Bug#1059899:

2024-01-03 Thread Corin Langosch
I just disabled LLMNR by putting LLMNR=no in resolved.conf to see if it helps, but it still crashes as before. Jan 03 12:16:23 system1 systemd-resolved[863]: Got DNS stub UDP query packet for id 10122 Jan 03 12:16:23 system1 systemd-resolved[863]: Looking up RR for 54.49.125.74.in-addr.arpa

Bug#1059894: marked as done (dkms - fails autopkgtest with Linux 6.6)

2024-01-03 Thread Debian Bug Tracking System
Your message dated Wed, 3 Jan 2024 11:41:51 +0100 with message-id <800d2084-dd60-5747-6f39-b306e8003...@debian.org> and subject line Re: Bug#1059894: dkms - fails autopkgtest with Linux 6.6 has caused the Debian Bug report #1059894, regarding dkms - fails autopkgtest with Linux 6.6 to be marked as

Bug#1058250: marked as pending in urwid

2024-01-03 Thread Matthias Klose
Control: tag -1 pending Hello, Bug #1058250 in urwid 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:

Bug#1055564: marked as done (pyalsaaudio ftbfs with Python 3.12)

2024-01-03 Thread Debian Bug Tracking System
Your message dated Wed, 03 Jan 2024 09:53:59 + with message-id and subject line Bug#1055564: fixed in pyalsaaudio 0.10.0-0.1 has caused the Debian Bug report #1055564, regarding pyalsaaudio ftbfs with Python 3.12 to be marked as done. This means that you claim that the problem has been dealt

Processed: Bug#1058250 marked as pending in urwid

2024-01-03 Thread Debian Bug Tracking System
Processing control commands: > tag -1 pending Bug #1058250 [src:urwid] urwid: FTBFS: TypeError: list indices must be integers or slices, not Key Added tag(s) pending. -- 1058250: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1058250 Debian Bug Tracking System Contact ow...@bugs.debian.org

Bug#1058250: marked as done (urwid: FTBFS: TypeError: list indices must be integers or slices, not Key)

2024-01-03 Thread Debian Bug Tracking System
Your message dated Wed, 03 Jan 2024 10:25:17 + with message-id and subject line Bug#1058250: fixed in urwid 2.1.2-4.2 has caused the Debian Bug report #1058250, regarding urwid: FTBFS: TypeError: list indices must be integers or slices, not Key to be marked as done. This means that you

Processed: Bug#1058270 marked as pending in python-schema-salad

2024-01-03 Thread Debian Bug Tracking System
Processing control commands: > tag -1 pending Bug #1058270 [src:python-schema-salad] python-schema-salad: FTBFS: mypy-stubs/mistune/scanner.pyi:19:52: error: Missing type parameters for generic type "Match" [type-arg] Added tag(s) pending. -- 1058270:

Bug#1058270: marked as pending in python-schema-salad

2024-01-03 Thread Michael R. Crusoe
Control: tag -1 pending Hello, Bug #1058270 in python-schema-salad 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:

Bug#1059899: systemd-resolved: systemd-resolved takes up all memory on certain PTR queries and is then oom-killed

2024-01-03 Thread Corin Langosch
Package: systemd Version: 247.3-7+deb11u4 Severity: critical File: systemd-resolved Justification: breaks the whole system X-Debbugs-Cc: cor...@gmx.de Dear Maintainer, systemd-resolved takes up all memory on certain PTR queries within only a few milliseconds and is then oom-killed. This

Bug#1059894: dkms - fails autopkgtest with Linux 6.6

2024-01-03 Thread Bastian Blank
Package: dkms Version: 3.0.12-1 Severity: serious The dkms autopkgtest fails with Linux 6.6. The only output is: | 143s autopkgtest [15:40:46]: test run_test.sh: [--- | 143s Using kernel 6.6.9-amd64/x86_64 | 143s Preparing a clean test environment | 146s Test framework file

Bug#1059785: marked as done (benchmark breaks ABI without SONAME bump)

2024-01-03 Thread Debian Bug Tracking System
Your message dated Wed, 03 Jan 2024 10:09:33 + with message-id and subject line Bug#1059785: fixed in benchmark 1.8.3-2 has caused the Debian Bug report #1059785, regarding benchmark breaks ABI without SONAME bump to be marked as done. This means that you claim that the problem has been

Bug#1055717: marked as pending in python-multidict

2024-01-03 Thread Matthias Klose
Control: tag -1 pending Hello, Bug #1055717 in python-multidict 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:

Processed: Bug#1055717 marked as pending in python-multidict

2024-01-03 Thread Debian Bug Tracking System
Processing control commands: > tag -1 pending Bug #1055717 [src:python-multidict] python-multidict ftbfs with Python 3.12 Added tag(s) pending. -- 1055717: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1055717 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems

Processed: Re: systemd-resolved: systemd-resolved takes up all memory on certain PTR queries and is then oom-killed

2024-01-03 Thread Debian Bug Tracking System
Processing control commands: > severity -1 normal Bug #1059899 [systemd] systemd-resolved: systemd-resolved takes up all memory on certain PTR queries and is then oom-killed Severity set to 'normal' from 'critical' > tags -1 moreinfo Bug #1059899 [systemd] systemd-resolved: systemd-resolved

Bug#1059899: systemd-resolved: systemd-resolved takes up all memory on certain PTR queries and is then oom-killed

2024-01-03 Thread Luca Boccassi
Control: severity -1 normal Control: tags -1 moreinfo On Wed, 03 Jan 2024 12:02:40 +0100 Corin Langosch wrote: > Package: systemd > Version: 247.3-7+deb11u4 > Severity: critical > File: systemd-resolved > Justification: breaks the whole system Your logs show that it restarts just fine after the

Processed: affects 1059671

2024-01-03 Thread Debian Bug Tracking System
Processing commands for cont...@bugs.debian.org: > affects 1059671 + src:ropgadget Bug #1059671 [python3-capstone] python3-capstone: Python 3.12 has no module named 'distutils' Added indication that 1059671 affects src:ropgadget > thanks Stopping processing here. Please contact me if you need

Bug#1030545: marked as done (qemu-(img|system-s390x) hang on s390x bullseye kernel)

2024-01-03 Thread Debian Bug Tracking System
Your message dated Wed, 3 Jan 2024 19:00:38 +0300 with message-id and subject line Re: qemu-(img|system-s390x) hang on s390x bullseye kernel has caused the Debian Bug report #1030545, regarding qemu-(img|system-s390x) hang on s390x bullseye kernel to be marked as done. This means that you claim

Bug#1059921: intake: autopkgtest failure with Python 3.12

2024-01-03 Thread Graham Inggs
Source: intake Version: 0.6.6-2 Severity: serious User: debian-pyt...@lists.debian.org Usertags: python3.12 Hi Maintainer intake's autopkgtests fail with Python 3.12 [1]. I've copied what I hope is the relevant part of the log below. Regards Graham [1]

Bug#1058417: pytest-mock: FTBFS: dh_auto_test: error: pybuild --test --test-pytest -i python{version} -p "3.12 3.11" returned exit code 13

2024-01-03 Thread Graham Inggs
Control: tags -1 + fixed-upstream patch This was fixed in the following upstream commit: https://github.com/pytest-dev/pytest-mock/commit/3d48ff90257daf6b3c50100bd5dd36faf34e70dc

Bug#1059671: ropgadget: autopkgtest failure with Python 3.12

2024-01-03 Thread Timo Röhling
Control: reassign -1 python3-capstone Control: retitle -1 python3-capstone: Python 3.12 has no module named 'distutils' On Fri, 29 Dec 2023 23:25:28 +0200 Graham Inggs wrote: 36s from capstone import * 36s File "/usr/lib/python3/dist-packages/capstone/__init__.py", line 266, in 36s

Processed: Re: ropgadget: autopkgtest failure with Python 3.12

2024-01-03 Thread Debian Bug Tracking System
Processing control commands: > reassign -1 python3-capstone Bug #1059671 [src:ropgadget] ropgadget: autopkgtest failure with Python 3.12 Bug reassigned from package 'src:ropgadget' to 'python3-capstone'. No longer marked as found in versions ropgadget/7.4+dfsg-1. Ignoring request to alter fixed

Bug#1055696: marked as done (python3-rdkit: unusable with Python 3.12)

2024-01-03 Thread Debian Bug Tracking System
Your message dated Wed, 3 Jan 2024 13:35:13 +0200 with message-id and subject line Re: Bug#1055696: 1055696: more info has caused the Debian Bug report #1055696, regarding python3-rdkit: unusable with Python 3.12 to be marked as done. This means that you claim that the problem has been dealt

Bug#1059913: setuptools-scm fails it's autopkg tests

2024-01-03 Thread Matthias Klose
Package: src:setuptools-scm Version: 8.0.4-1 Severity: serious Tags: sid trixie User: debian-pyt...@lists.debian.org Usertags: python3.12 $ apt show python3-setuptools-scm|grep Depends Depends: python3-distutils, python3-pkg-resources, python3-packaging, python3-tomli | python3-supported-min

Bug#1059922: nut-server: upsd fails to start since version 2.8.1

2024-01-03 Thread Jörg-Volker Peetz
Package: nut-server Version: 2.8.1-1 Severity: grave Dear Laurent Bigonville, with version 2.8.0-7 an EATON UPS connected to a debian computer via USB was working in standalone mode as expected. The only change in the config files was in /etc/nut/ups.conf where I added the following lines:

Bug#1055717: marked as done (python-multidict ftbfs with Python 3.12)

2024-01-03 Thread Debian Bug Tracking System
Your message dated Wed, 03 Jan 2024 11:35:16 + with message-id and subject line Bug#1055717: fixed in python-multidict 6.0.4-1.1 has caused the Debian Bug report #1055717, regarding python-multidict ftbfs with Python 3.12 to be marked as done. This means that you claim that the problem has

Bug#1056594: [Pkg-privacy-maintainers] Bug#1056594: mat2: test failure

2024-01-03 Thread Georg Faerber
Hi Paul, On 24-01-01 10:24:46, Paul Gevers wrote: > On 01-01-2024 09:50, Paul Gevers wrote: > > I'm going to NMU with this patch shortly. @gregor, any reason why > > you didn't the upload to DELAYED after you built it already? > > I have uploaded the attached changes. Thanks for the upload,

Processed: pytest-mock: FTBFS: dh_auto_test: error: pybuild --test --test-pytest -i python{version} -p "3.12 3.11" returned exit code 13

2024-01-03 Thread Debian Bug Tracking System
Processing control commands: > tags -1 + fixed-upstream patch Bug #1058417 [src:pytest-mock] pytest-mock: FTBFS: dh_auto_test: error: pybuild --test --test-pytest -i python{version} -p "3.12 3.11" returned exit code 13 Added tag(s) patch and fixed-upstream. -- 1058417:

Bug#1059894: dkms - fails autopkgtest with Linux 6.6

2024-01-03 Thread Bastian Blank
On Wed, Jan 03, 2024 at 11:41:51AM +0100, Andreas Beckmann wrote: > On 03/01/2024 09.49, Bastian Blank wrote: > > The dkms autopkgtest fails with Linux 6.6. The only output is: > > | 173s modinfo: ERROR: Module > > /var/lib/dkms/dkms_test/1.0/6.6.9-amd64/x86_64/module/dkms_test.ko not > >

Bug#1059923: marked as done (spread-sheet-widget_0.10-1_s390x-buildd.changes REJECTED)

2024-01-03 Thread Debian Bug Tracking System
Your message dated Wed, 03 Jan 2024 18:51:24 + with message-id and subject line Bug#1059923: fixed in spread-sheet-widget 0.10-2 has caused the Debian Bug report #1059923, regarding spread-sheet-widget_0.10-1_s390x-buildd.changes REJECTED to be marked as done. This means that you claim that

Processed: Re: Bug#1059885: makes dkms package postinst fail with "post-installation script subprocess returned error exit status 127"

2024-01-03 Thread Debian Bug Tracking System
Processing control commands: > severity -1 serious Bug #1059885 [dkms] makes dkms package postinst fail with "post-installation script subprocess returned error exit status 127" Severity set to 'serious' from 'normal' -- 1059885: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1059885 Debian

Bug#1059885: marked as done (makes dkms package postinst fail with "post-installation script subprocess returned error exit status 127")

2024-01-03 Thread Debian Bug Tracking System
Your message dated Wed, 03 Jan 2024 19:34:04 + with message-id and subject line Bug#1059885: fixed in dkms 3.0.12-4 has caused the Debian Bug report #1059885, regarding makes dkms package postinst fail with "post-installation script subprocess returned error exit status 127" to be marked as

Bug#1056828: Severity / marking of "uses cython3-legacy" bugs

2024-01-03 Thread Rebecca N. Palmer
pandas and statsmodels are currently using cython3-legacy. I left their cython 3.0 bugs open when I made this change, as I do want to actually switch them to cython 3.x at some point. These bugs have now been raised to RC. Is this an intentional attempt to remove cython3-legacy (which seems

Processed: reopening 1059923

2024-01-03 Thread Debian Bug Tracking System
Processing commands for cont...@bugs.debian.org: > reopen 1059923 Bug #1059923 {Done: Friedrich Beckmann } [src:spread-sheet-widget] spread-sheet-widget_0.10-1_s390x-buildd.changes REJECTED 'reopen' may be inappropriate when a bug has been closed with a version; all fixed versions will be

Bug#1059923: marked as done (spread-sheet-widget_0.10-1_s390x-buildd.changes REJECTED)

2024-01-03 Thread Debian Bug Tracking System
Your message dated Wed, 03 Jan 2024 22:06:09 + with message-id and subject line Bug#1059923: fixed in spread-sheet-widget 0.10-3 has caused the Debian Bug report #1059923, regarding spread-sheet-widget_0.10-1_s390x-buildd.changes REJECTED to be marked as done. This means that you claim that

Bug#1059913: marked as done (setuptools-scm fails it's autopkg tests)

2024-01-03 Thread Debian Bug Tracking System
Your message dated Wed, 03 Jan 2024 22:05:57 + with message-id and subject line Bug#1059913: fixed in setuptools-scm 8.0.4-2 has caused the Debian Bug report #1059913, regarding setuptools-scm fails it's autopkg tests to be marked as done. This means that you claim that the problem has been

Bug#1056393: marked as done (radare2-cutter: Cannot debug binary: File '' does not have executable permissions.)

2024-01-03 Thread Debian Bug Tracking System
Your message dated Wed, 03 Jan 2024 17:37:02 + with message-id and subject line Bug#1059836: Removed package(s) from unstable has caused the Debian Bug report #1056393, regarding radare2-cutter: Cannot debug binary: File '' does not have executable permissions. to be marked as done. This

Bug#1058404: marked as done (python-graphviz: FTBFS: dh_auto_test: error: pybuild --test --test-pytest -i python{version} -p "3.12 3.11" returned exit code 13)

2024-01-03 Thread Debian Bug Tracking System
Your message dated Wed, 03 Jan 2024 21:07:09 + with message-id and subject line Bug#1058404: fixed in python-graphviz 0.20.1+20240103-1 has caused the Debian Bug report #1058404, regarding python-graphviz: FTBFS: dh_auto_test: error: pybuild --test --test-pytest -i python{version} -p "

Bug#1000005: marked as done (passwordmaker-cli: depends on obsolete pcre3 library)

2024-01-03 Thread Debian Bug Tracking System
Your message dated Wed, 03 Jan 2024 21:06:54 + with message-id and subject line Bug#105: fixed in passwordmaker-cli 1.5+dfsg-6 has caused the Debian Bug report #105, regarding passwordmaker-cli: depends on obsolete pcre3 library to be marked as done. This means that you claim that

Bug#1056473: marked as done (python-graphviz's autopkg test failures with Python 3.12)

2024-01-03 Thread Debian Bug Tracking System
Your message dated Wed, 03 Jan 2024 21:07:09 + with message-id and subject line Bug#1056473: fixed in python-graphviz 0.20.1+20240103-1 has caused the Debian Bug report #1056473, regarding python-graphviz's autopkg test failures with Python 3.12 to be marked as done. This means that you

Bug#1059885: makes dkms package postinst fail with "post-installation script subprocess returned error exit status 127"

2024-01-03 Thread Andreas Beckmann
On 03/01/2024 20.13, Johannes Schauer Marin Rodrigues wrote: now that I know that BUILT_MODULE_NAME[0] and DEST_MODULE_LOCATION[0] break it, I found other packages via codesearch.d.n that use that syntax and I was wondering whether they break as well. I did the same test after seeing your bug

Bug#1056594: [Pkg-privacy-maintainers] Bug#1056594: mat2: test failure

2024-01-03 Thread Paul Gevers
Hi, On 03-01-2024 14:02, Georg Faerber wrote: Thanks for the upload, although I would have appreciated communication about this upfront. Of course. As a Release Manager, I would have appreciated a more timely handeling of an RC issue that blocks other packages. I followed DevRef guidance:

Bug#1058318: flask-login: FTBFS: dh_auto_test: error: pybuild --test --test-pytest -i python{version} -p "3.12 3.11" returned exit code 13

2024-01-03 Thread Julian Gilbey
On Fri, Dec 22, 2023 at 12:04:48AM +0100, Gregor Riepl wrote: > Hi Carsten, > [...] > > My point was that if, for whatever reason, werkzeug 3.0.1 is not yet fit for > release, it should be enough to upgrade to 2.3.5 to address these unit test > failures. > [...] > > That doesn't make any sense

Bug#1056891: Severity / marking of "uses cython3-legacy" bugs

2024-01-03 Thread stefanor
Hi Rebecca (2024.01.03_21:27:49_+) > pandas and statsmodels are currently using cython3-legacy. I left their > cython 3.0 bugs open when I made this change, as I do want to actually > switch them to cython 3.x at some point. > > These bugs have now been raised to RC. Is this an intentional

Bug#1059923: spread-sheet-widget_0.10-1_s390x-buildd.changes REJECTED

2024-01-03 Thread Aurelien Jarno
Source: spread-sheet-widget Version: 0.10-1 Severity: serious On 2024-01-03 17:21, Debian FTP Masters wrote: > > > libspread-sheet-widget-dev_0.10-1_s390x.deb: has 1 file(s) with a timestamp > too far in the past: > usr/share/doc/libspread-sheet-widget-dev/changelog.gz (Thu Jan 1 00:00:00

Bug#1059913: marked as pending in setuptools-scm

2024-01-03 Thread Stefano Rivera
Control: tag -1 pending Hello, Bug #1059913 in setuptools-scm 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:

Processed: Bug#1059913 marked as pending in setuptools-scm

2024-01-03 Thread Debian Bug Tracking System
Processing control commands: > tag -1 pending Bug #1059913 [src:setuptools-scm] setuptools-scm fails it's autopkg tests Added tag(s) pending. -- 1059913: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1059913 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems

Bug#1008205: marked as done (RM: gamin -- RoQA; dead upstream)

2024-01-03 Thread Debian Bug Tracking System
Your message dated Wed, 03 Jan 2024 17:41:39 + with message-id and subject line Bug#1057655: Removed package(s) from unstable has caused the Debian Bug report #1008205, regarding RM: gamin -- RoQA; dead upstream to be marked as done. This means that you claim that the problem has been dealt

Bug#1042184: marked as done (chaussette: FTBFS: AssertionError: Lists differ: ['waitress', 'wsgiref'] != ['eventlet', 'waitress', 'wsgiref'])

2024-01-03 Thread Debian Bug Tracking System
Your message dated Wed, 03 Jan 2024 17:40:10 + with message-id and subject line Bug#1059887: Removed package(s) from unstable has caused the Debian Bug report #1042184, regarding chaussette: FTBFS: AssertionError: Lists differ: ['waitress', 'wsgiref'] != ['eventlet', 'waitress', 'wsgiref']

Bug#1054973: marked as done (libcgi-application-plugin-authentication-perl: FTBFS: dh_auto_test: error: make -j8 test TEST_VERBOSE=1 returned exit code 2)

2024-01-03 Thread Debian Bug Tracking System
Your message dated Thu, 04 Jan 2024 00:04:07 + with message-id and subject line Bug#1054973: fixed in libcgi-application-plugin-authentication-perl 0.23+~cs0.5-2.1 has caused the Debian Bug report #1054973, regarding libcgi-application-plugin-authentication-perl: FTBFS: dh_auto_test: error:

Bug#1054973: marked as done (libcgi-application-plugin-authentication-perl: FTBFS: dh_auto_test: error: make -j8 test TEST_VERBOSE=1 returned exit code 2)

2024-01-03 Thread Debian Bug Tracking System
Your message dated Thu, 04 Jan 2024 00:19:50 + with message-id and subject line Bug#1054973: fixed in libcgi-application-plugin-authentication-perl 0.23+~cs0.5-3 has caused the Debian Bug report #1054973, regarding libcgi-application-plugin-authentication-perl: FTBFS: dh_auto_test: error:

Bug#999989: poco 1.2 uses PCRE2, Mumble 1.5 depends on poco

2024-01-03 Thread Chris Knadle
All recent versions of Mumble now require Poco to build and will not build without it. Unless the Poco library can be updated the only way to save Mumble will be to introduce an epoch in the package version to upload the now well outdated mumble 1.3.4 again which upstream cannot support

Bug#1059923: marked as done (spread-sheet-widget_0.10-1_s390x-buildd.changes REJECTED)

2024-01-03 Thread Friedrich Beckmann
I disabled that the upstream changelog file is distributed in the debian package. The spread-sheet-widget provides two binary packages libspread-sheet-widget and libspread-sheet-widget-dev and both usually have the same changelog.gz which is derived from ChangeLog in the source directory. I

Bug#1056471: python-fabio: debdiff with patch from upstream recommendation

2024-01-03 Thread Yogeswaran Umasankar
Source: python-fabio Version: 2023.6.0-3 Followup-For: Bug #1056471 X-Debbugs-Cc: kd8...@gmail.com Hi, I went ahead and created a patch following the upstream author's advice. I've attached the debdiff for you to check out. Cheers! -- System Information: Debian Release: trixie/sid APT prefers

Bug#1054943: marked as done (haskell-yesod-bin: FTBFS: unsatisfiable build-dependency: libghc-fsnotify-dev (< 0.4) but 0.4.1.0-1+b1 is to be installed)

2024-01-03 Thread Debian Bug Tracking System
Your message dated Thu, 04 Jan 2024 05:19:07 + with message-id and subject line Bug#1054943: fixed in haskell-yesod-bin 1.6.2.2-2 has caused the Debian Bug report #1054943, regarding haskell-yesod-bin: FTBFS: unsatisfiable build-dependency: libghc-fsnotify-dev (< 0.4) but 0.4.1.0-1+b1 is to

Bug#999989: poco 1.2 uses PCRE2, Mumble 1.5 depends on poco

2024-01-03 Thread Jochen Sprickerhof
Hi Chris, * Chris Knadle [2024-01-02 03:06]: Can the poco library be updated? Can I help in some way? poco is basically orphaned, as I dropped myself from Uploaders in git and did not hear from the other maintainers for some time. The best way to help is to step up as a maintainer and

Bug#1058318: flask-login: FTBFS: dh_auto_test: error: pybuild --test --test-pytest -i python{version} -p "3.12 3.11" returned exit code 13

2024-01-03 Thread Carsten Schoenert
Hello Gregor, Am 22.12.23 um 00:04 schrieb Gregor Riepl: My point was that if, for whatever reason, werkzeug 3.0.1 is not yet fit for release, it should be enough to upgrade to 2.3.5 to address these unit test failures. I did come to the conclusion that Werkzeug 2.3.x has some bigger changes

Bug#1058318: flask-login: FTBFS: dh_auto_test: error: pybuild --test --test-pytest -i python{version} -p "3.12 3.11" returned exit code 13

2024-01-03 Thread Carsten Schoenert
Hello Julian, Am 03.01.24 um 22:22 schrieb Julian Gilbey: Just to throw in: these werkzeug failures are also causing a similar FTBFS in debugpy; I've temporarily addressed it by skipping these unit tests, but that's not a great solution. I just took a quick look at upgrading the

Bug#1058083: Before I try to tackle this bug - can we move the package to DPT

2024-01-03 Thread Andreas Tille
Ping? If I do not hear from you in the next couple of days I'll move the package to DPT at beginning of next week. Kind regards Andreas. Am Mon, Dec 25, 2023 at 08:34:58AM +0100 schrieb Andreas Tille: > Hi Agustin and Ulises, > > I noticed there were several NMUs not commited to the Git