Bug#1058114: marked as pending in python-nudatus

2024-02-21 Thread Nick Morrott
Control: tag -1 pending

Hello,

Bug #1058114 in python-nudatus reported by you has been fixed in the
Git repository and is awaiting an upload. You can see the commit
message below and you can check the diff of the fix at:

https://salsa.debian.org/python-team/packages/python-nudatus/-/commit/fc2e861573f78b09c75cba17b328205dd02f40a4


d/patches: Add patch explicitly-raise-tokenerror

Closes: #1058114


(this message was generated automatically)
-- 
Greetings

https://bugs.debian.org/1058114



Bug#1056488: marked as pending in python-nudatus

2024-02-21 Thread Nick Morrott
Control: tag -1 pending

Hello,

Bug #1056488 in python-nudatus reported by you has been fixed in the
Git repository and is awaiting an upload. You can see the commit
message below and you can check the diff of the fix at:

https://salsa.debian.org/python-team/packages/python-nudatus/-/commit/cfdd94f4ba22f12e431cb8d1b02eaea0b73a25cc


d/patches: Add patch assert-after-context-manager-exits

Closes: #1056488


(this message was generated automatically)
-- 
Greetings

https://bugs.debian.org/1056488



Bug#1062953: python3-pyocd: Module is unusable (missing runtime dependencies)

2024-02-03 Thread Nick Morrott (nickm)

Package: python3-pyocd
Version: 0.36.0-1
Severity: grave
Justification: renders package unusable

Dear Maintainer,

The upload of python3-pyocd 0.36.0-1 appears to be completely unusable:

$ python3
Python 3.11.7 (main, Dec  8 2023, 14:22:46) [GCC 13.2.0] on linux
Type "help", "copyright", "credits" or "license" for more information.
>>> import pyOCD
Traceback (most recent call last):
  File "", line 1, in 
  File "/usr/lib/python3/dist-packages/pyOCD/__init__.py", line 21, in 
from . import gdbserver
  File "/usr/lib/python3/dist-packages/pyOCD/gdbserver/__init__.py", line 17, 
in 

from .gdbserver import GDBServer
  File "/usr/lib/python3/dist-packages/pyOCD/gdbserver/gdbserver.py", line 42, 
in 

from ..rtos import RTOS
  File "/usr/lib/python3/dist-packages/pyOCD/rtos/__init__.py", line 29, in 


load_plugin_classes_of_type('pyocd.rtos', RTOS, ThreadProvider)
  File "/usr/lib/python3/dist-packages/pyOCD/core/plugin.py", line 97, in 
load_plugin_classes_of_type

plugin = entry_point.load()()
 ^^
  File "/usr/lib/python3/dist-packages/importlib_metadata/__init__.py", line 
203, in load

module = import_module(match.group('module'))
 
  File "/usr/lib/python3.11/importlib/__init__.py", line 126, in import_module
return _bootstrap._gcd_import(name[level:], package, level)
   
  File "/usr/lib/python3/dist-packages/pyocd/__init__.py", line 21, in 
from . import gdbserver
  File "/usr/lib/python3/dist-packages/pyocd/gdbserver/__init__.py", line 17, 
in 

from .gdbserver import GDBServer
  File "/usr/lib/python3/dist-packages/pyocd/gdbserver/gdbserver.py", line 50, 
in 

return _bootstrap._gcd_import(name[level:], package, level)
   
  File "/usr/lib/python3/dist-packages/pyocd/probe/jlink_probe.py", line 22, in 


import pylink
ModuleNotFoundError: No module named 'pylink'


The build log reports several missing dependencies:

I: dh_python3 pydist:302: Cannot find package that provides cmsis_pack_manager.
I: dh_python3 pydist:302: Cannot find package that provides libusb_package.
I: dh_python3 pydist:302: Cannot find package that provides pylink_square.


Although present in the distribution, no tests are configured to run at build 
time.



-- System Information:
Debian Release: trixie/sid
  APT prefers testing
  APT policy: (700, 'testing'), (600, 'unstable'), (400, 'experimental')
Architecture: amd64 (x86_64)

Kernel: Linux 6.5.0-5-amd64 (SMP w/24 CPU threads; PREEMPT)
Kernel taint flags: TAINT_PROPRIETARY_MODULE, TAINT_OOT_MODULE, 
TAINT_UNSIGNED_MODULE

Locale: LANG=en_GB.UTF-8, LC_CTYPE=en_GB.UTF-8 (charmap=UTF-8), 
LANGUAGE=en_GB:en
Shell: /bin/sh linked to /usr/bin/dash
Init: systemd (via /run/systemd/system)
LSM: AppArmor: enabled

Versions of packages python3-pyocd depends on:
ii  python3  3.11.6-1
ii  python3-capstone 4.0.2-5+b1
ii  python3-colorama 0.4.6-4
ii  python3-importlib-metadata   4.12.0-1
ii  python3-importlib-resources  6.0.1-1
ii  python3-intelhex 2.3.0-2
ii  python3-intervaltree 3.0.2-1.1
ii  python3-lark 1.1.9-1
ii  python3-natsort  8.0.2-2
ii  python3-pkg-resources68.1.2-2
ii  python3-prettytable  3.6.0-1
ii  python3-pyelftools   0.30-1
ii  python3-six  1.16.0-4
ii  python3-typing-extensions4.7.1-2
ii  python3-usb  1.2.1-2
ii  python3-yaml 6.0.1-1+b1

python3-pyocd recommends no packages.

python3-pyocd suggests no packages.

-- no debconf information



Bug#999977: qxw: depends on obsolete pcre3 library

2023-09-04 Thread Nick Morrott
On Mon, 4 Sept 2023 at 07:32, Stephen Kitt  wrote:
>
> It took me longer to get round to this than I hoped, but here is a patch for
> qxw. I’ve already forwarded it upstream.

Dear Stephen and Bastian,

Thank you both for the pcre2 patch and the upload of qxw.

I got back from vacation yesterday and receiving the commit and upload
notifications this morning was a very unexpected gift!

Many thanks,
Nick



Bug#999977: qxw: depends on obsolete pcre3 library

2023-07-30 Thread Nick Morrott
On 2023/07/22 at 08:43, Stephen Kitt wrote:
>aOn Sat, 22 Jul 2023 16:14:06 +0200, Bastian Germann  wrote:
> > I suggest to remove the package. I do not think upstream will deal with 
> > this.
> 
> qxw’s usage of pcre seems simple enough, I’ll try to come up with a patch.
> 
> Regards,
> 
> Stephen

Bastian/Stephen,

In my last contact with upstream I discussed the use of the obsolete pcre3
library. The development team told me that a new GTK3/Qt GUI is under
development which will resolve the pcre3 issue in addition to the
proposed UI improvements.

In the meantime, I will look to spend some time understanding the
pcre3->pcre2 migration and patching qxw in the short term, if Stephen does
not have time to do so.

I'd like to keep qxw in the archive, given the time spent getting it
reintroduced in time for bookworm following the RFP.

Thanks,
Nick



Bug#1026600: firmware-microbit-micropython: diff for NMU version 1.0.1-3.1

2023-02-07 Thread Nick Morrott
On Tue, 7 Feb 2023 at 09:01, Adrian Bunk  wrote:
>
> On Tue, Feb 07, 2023 at 01:23:28AM +, Nick Morrott wrote:
> >...
> > I'm happy for the NMU to stay in DELAYED/1 and will have a look at
> > getting the new upstream packaged over the next days.
>
> that sounds good, but please wait until my NMU is in testing before
> making further uploads - if the package misses the deadline on the 12th
> it will not be in bookworm.

Absolutely.

Thank you again,
Nick



Bug#1026600: firmware-microbit-micropython: diff for NMU version 1.0.1-3.1

2023-02-06 Thread Nick Morrott
On Mon, 6 Feb 2023 at 23:33, Adrian Bunk  wrote:
>
> Control: tags 1026600 + patch
> Control: tags 1026600 + pending
>
> Dear maintainer,
>
> I've prepared an NMU for firmware-microbit-micropython (versioned as 
> 1.0.1-3.1)
> and uploaded it to DELAYED/1. Please feel free to tell me if I should cancel 
> it.

Dear Adrian,

Thank you so much for preparing a patch and NMU to fix this issue. I
hadn't yet realised the fix would be quite so straightforward.

I'm happy for the NMU to stay in DELAYED/1 and will have a look at
getting the new upstream packaged over the next days.

Thanks,
Nick



Bug#933923: src:valinor: Incompatible with safe load changes in new pyyaml

2019-11-10 Thread Nick Morrott
Control: retitle -1 valinor: FTBFS and autopkgtest failure due to new version 
of pyyaml
thanks



Bug#933923: src:valinor: Incompatible with safe load changes in new pyyaml

2019-11-10 Thread Nick Morrott
Control: retitle -1 valinor: FTBFS and autopkgtest failure due to new
version of pyyaml
thanks



Bug#933923: src:valinor: Incompatible with safe load changes in new pyyaml

2019-11-10 Thread Nick Morrott
retitle -1 valinor: FTBFS and autopkgtest failure due to new version of pyyaml
thanks



Bug#910342: playerctl: diff for NMU version 0.6.1-1.1

2018-10-11 Thread Nick Morrott
On Wed, 10 Oct 2018 10:01:20 +0100 Simon McVittie  wrote:
> Control: tags 910342 + patch
> Control: tags 910342 + pending
>
> I've prepared an NMU for playerctl (versioned as 0.6.1-1.1) and
> uploaded it to DELAYED/2. Please feel free to tell me if I
> should cancel it or delay it longer.
>
> Individual git commits and a consolidated nmudiff are
> attached, but I imagine you'd probably prefer to merge
> https://salsa.debian.org/nickm-guest/playerctl/merge_requests/1 instead.

Simon,

Many thanks for preparing an NMU, which I'll let upload from DELAYED/2.

I've merged your PR on salsa.

Thanks,
Nick


Bug#898086: libequinox-osgi-java: Does not install symlinks into /usr/lib/eclipse/plugins

2018-05-06 Thread Nick Morrott
Source: libequinox-osgi-java
Version: 3.9.1-1
Severity: grave
Justification: renders package unusable
Control: affects eclipse

Dear Maintainer,

The separation of the libequinox-osgi-java binary package from the eclipse
source appears to break fresh installations of eclipse.

On a fresh installation of eclipse on buster/sid (using a supported JDK
version), it is apparent that eclipse is unable to locate
/usr/lib/eclipse/plugins/org.eclipse.osgi_3.8.1.dist.jar (configured in
/usr/lib/eclipse/configuration/org.eclipse.equinox.simpleconfigurator/bundles.info).

On stretch (3.8.1-10), the relevant symlinks between
/usr/lib/eclipse/plugins and
/usr/share/java are present.

On buster/sid, no symlink is created to /usr/lib/eclipse/plugins,
which causes eclipse to immediately crash.

Manually installing the following symlink resolves the issue:

cd /usr/lib/eclipse/plugins
ln -s ../../../share/java/org.eclipse.osgi-3.9.1.jar
org.eclipse.osgi_3.8.1.dist.jar



-- System Information:
Debian Release: buster/sid
  APT prefers testing
  APT policy: (600, 'testing'), (200, 'unstable')
Architecture: amd64 (x86_64)

Kernel: Linux 4.15.0-3-amd64 (SMP w/8 CPU cores)
Locale: LANG=en_GB.UTF-8, LC_CTYPE=en_GB.UTF-8 (charmap=UTF-8),
LANGUAGE=en_GB:en (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Init: systemd (via /run/systemd/system)
LSM: AppArmor: enabled



Bug#792193: FTBFS: t/test_filters.t fails with TAP syntax errors

2015-08-17 Thread Nick Morrott
Please close. This bug report is against an old version of XMLTV (0.5.63-2).

My NMU of 0.5.66-0.1 was accepted into unstable a few weeks ago and
this bug report is stopping it from migrating into testing.

Thanks,
Nick