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

2023-12-24 Thread Andreas Tille
Hi Agustin and Ulises, I noticed there were several NMUs not commited to the Git repository of this package. I'd volunteer to bring the repository in sync with latest uploads and move it to Debian Python Team before I try to tacke bug #1058083. Kind regards Andreas. -- http://fam-tille.de

Bug#1043131: marked as done (openafs-modules-dkms: module fails to build for Linux 6.5: error: static declaration of 'abort' follows non-static declaration)

2023-12-24 Thread Debian Bug Tracking System
Your message dated Mon, 25 Dec 2023 00:19:20 + with message-id and subject line Bug#1043131: fixed in openafs 1.8.10-2 has caused the Debian Bug report #1043131, regarding openafs-modules-dkms: module fails to build for Linux 6.5: error: static declaration of 'abort' follows non-static declar

Bug#1043131: Solution for kernel 6.5 with openafs 1.8.10-1 in debian

2023-12-24 Thread Benjamin Kaduk
Hi Gergely, On Wed, Dec 20, 2023 at 04:26:55PM +0100, Gergely Riskó wrote: > Hey all, > > Yes, OpenAFS is always a pain to work with both on the server and the > client side. :( > > This time I think the client installation is harder than usual, we > have to apply 5 patches. Yes, there's a lot

Bug#1056427: marked as done (monty's autopkg tests fail with Python 3.12)

2023-12-24 Thread Debian Bug Tracking System
Your message dated Sun, 24 Dec 2023 22:34:56 + with message-id and subject line Bug#1056427: fixed in monty 2023.11.3-2 has caused the Debian Bug report #1056427, regarding monty's autopkg tests fail with Python 3.12 to be marked as done. This means that you claim that the problem has been de

Bug#1058353: marked as done (libadios2-mpi-c-dev: ships headers already shipped in libadios2-common-c-dev)

2023-12-24 Thread Debian Bug Tracking System
Your message dated Sun, 24 Dec 2023 22:19:15 + with message-id and subject line Bug#1058353: fixed in adios2 2.9.2+dfsg1-6 has caused the Debian Bug report #1058353, regarding libadios2-mpi-c-dev: ships headers already shipped in libadios2-common-c-dev to be marked as done. This means that y

Bug#1058511: marked as done (ntpsec: FTBFS: mv: cannot stat 'debian/tmp/lib/systemd/system/ntpd.service': No such file or directory)

2023-12-24 Thread Debian Bug Tracking System
Your message dated Sun, 24 Dec 2023 16:06:50 -0600 with message-id <9fe632fb-fb05-4327-9a95-1f63cd836...@debian.org> and subject line Re: Bug#1058511: ntpsec: FTBFS: mv: cannot stat 'debian/tmp/lib/systemd/system/ntpd.service': No such file or directory has caused the Debian Bug report #1058511, r

Bug#1058511: ntpsec: FTBFS: mv: cannot stat 'debian/tmp/lib/systemd/system/ntpd.service': No such file or directory

2023-12-24 Thread Richard Laager
Control: fixed 1.2.2+dfsg1-3 This looks to be the same as #1052664. -- Richard OpenPGP_signature.asc Description: OpenPGP digital signature

Bug#1056467: python-djangosaml2's autopkg tests fail with Python 3.12

2023-12-24 Thread s3v
Dear Maintainer, This issue was fixed in the new upload of python3-xmlschema and autopkg tests pass now. Please see https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1058194 Kind Regards

Bug#1058194: python-djangosaml2: FTBFS: AttributeError: type object '_PurePosixPath' has no attribute '_from_parts'. Did you mean: '_load_parts'?

2023-12-24 Thread s3v
Dear Maintainer, >   File "/usr/lib/python3/dist-packages/xmlschema/__init__.py", line 20, in > > from .dataobjects import DataElement, DataElementConverter, >DataBindingConverter >   File "/usr/lib/python3/dist-packages/xmlschema/dataobjects.py", line 27, in > > from . import validator

Bug#1057570: marked as done (libgnt: FTBFS: error: invalid use of incomplete typedef ‘PANEL’ {aka ‘struct panel’})

2023-12-24 Thread Debian Bug Tracking System
Your message dated Sun, 24 Dec 2023 21:20:12 + with message-id and subject line Bug#1057570: fixed in libgnt 2.14.4-1 has caused the Debian Bug report #1057570, regarding libgnt: FTBFS: error: invalid use of incomplete typedef ‘PANEL’ {aka ‘struct panel’} to be marked as done. This means tha

Bug#1057570: libgnt: FTBFS: error: invalid use of incomplete typedef ‘PANEL’ {aka ‘struct panel’}

2023-12-24 Thread Richard Laager
On 2023-12-20 09:57, Sven Joachim wrote: I have not tested it myself, but these errors should be fixed in libgnt 2.14.4 which has been released upstream the other day. See https://keep.imfreedom.org/libgnt/libgnt/rev/2da723f790d6, which explicitly mentions this bug. Thanks for letting me know!

Bug#1058550: marked as done (autopkgtest: FTBFS: make[1]: *** [debian/rules:38: override_dh_auto_test] Error 1)

2023-12-24 Thread Debian Bug Tracking System
Your message dated Sun, 24 Dec 2023 20:50:53 + with message-id and subject line Bug#1058550: fixed in autopkgtest 5.31.2 has caused the Debian Bug report #1058550, regarding autopkgtest: FTBFS: make[1]: *** [debian/rules:38: override_dh_auto_test] Error 1 to be marked as done. This means tha

Processed: thunderbolt-tools: diff for NMU version 0.9.3-6.1

2023-12-24 Thread Debian Bug Tracking System
Processing control commands: > tags 1058828 + pending Bug #1058828 [src:thunderbolt-tools] thunderbolt-tools: installs tbtacl-write twice when udev.pc changes Added tag(s) pending. -- 1058828: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1058828 Debian Bug Tracking System Contact ow...@bug

Bug#1058828: thunderbolt-tools: diff for NMU version 0.9.3-6.1

2023-12-24 Thread Chris Hofstaedtler
Control: tags 1058828 + pending Dear maintainer, I've prepared an NMU for thunderbolt-tools (versioned as 0.9.3-6.1) and uploaded it to DELAYED/7. Please feel free to upload yourself in the meantime. Chris diff -Nru thunderbolt-tools-0.9.3/debian/changelog thunderbolt-tools-0.9.3/debian/changel

Processed: Bug#1058550 marked as pending in autopkgtest

2023-12-24 Thread Debian Bug Tracking System
Processing control commands: > tag -1 pending Bug #1058550 [src:autopkgtest] autopkgtest: FTBFS: make[1]: *** [debian/rules:38: override_dh_auto_test] Error 1 Added tag(s) pending. -- 1058550: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1058550 Debian Bug Tracking System Contact ow...@bug

Bug#1058550: marked as pending in autopkgtest

2023-12-24 Thread Simon McVittie
Control: tag -1 pending Hello, Bug #1058550 in autopkgtest 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/ci-team/autopkgtest/-/commit/4066518f5b21eae9ca62cb16

Bug#1057245: marked as done (gnome-settings-daemon: will FTBFS when udev.pc changes udevdir)

2023-12-24 Thread Debian Bug Tracking System
Your message dated Sun, 24 Dec 2023 16:19:26 + with message-id and subject line Bug#1057245: fixed in gnome-settings-daemon 45.0-2 has caused the Debian Bug report #1057245, regarding gnome-settings-daemon: will FTBFS when udev.pc changes udevdir to be marked as done. This means that you clai

Processed: Bug#1057245 marked as pending in gnome-settings-daemon

2023-12-24 Thread Debian Bug Tracking System
Processing control commands: > tag -1 pending Bug #1057245 [src:gnome-settings-daemon] gnome-settings-daemon: will FTBFS when udev.pc changes udevdir Added tag(s) pending. -- 1057245: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1057245 Debian Bug Tracking System Contact ow...@bugs.debian.

Bug#1057245: marked as pending in gnome-settings-daemon

2023-12-24 Thread Simon McVittie
Control: tag -1 pending Hello, Bug #1057245 in gnome-settings-daemon 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/gnome-team/gnome-settings-daemon/-/commit/2

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

2023-12-24 Thread Debian Bug Tracking System
Your message dated Sun, 24 Dec 2023 15:34:10 + with message-id and subject line Bug#1056224: fixed in advocate 1.0.0-5 has caused the Debian Bug report #1056224, regarding advocate: FTBFS: dh_auto_test: error: pybuild --test -i python{version} -p "3.12 3.11" returned exit code 13 to be marked

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

2023-12-24 Thread Debian Bug Tracking System
Your message dated Sun, 24 Dec 2023 15:34:10 + with message-id and subject line Bug#1058209: fixed in advocate 1.0.0-5 has caused the Debian Bug report #1058209, regarding advocate: FTBFS: dh_auto_test: error: pybuild --test -i python{version} -p "3.12 3.11" returned exit code 13 to be marked

Bug#1056224: marked as done (advocate's autopkg tests fail with Python 3.12)

2023-12-24 Thread Debian Bug Tracking System
Your message dated Sun, 24 Dec 2023 15:34:10 + with message-id and subject line Bug#1058209: fixed in advocate 1.0.0-5 has caused the Debian Bug report #1058209, regarding advocate's autopkg tests fail with Python 3.12 to be marked as done. This means that you claim that the problem has been

Bug#1056224: marked as done (advocate's autopkg tests fail with Python 3.12)

2023-12-24 Thread Debian Bug Tracking System
Your message dated Sun, 24 Dec 2023 15:34:10 + with message-id and subject line Bug#1056224: fixed in advocate 1.0.0-5 has caused the Debian Bug report #1056224, regarding advocate's autopkg tests fail with Python 3.12 to be marked as done. This means that you claim that the problem has been

Processed: Debian bug #1059396

2023-12-24 Thread Debian Bug Tracking System
Processing commands for cont...@bugs.debian.org: > forwarded 1059396 https://gitlab.gnome.org/GNOME/evolution/-/issues/2620 Bug #1059396 [evolution] PGP/GPG handling wrong Set Bug forwarded-to-address to 'https://gitlab.gnome.org/GNOME/evolution/-/issues/2620'. > -- Stopping processing here. Ple

Bug#1059396: PGP/GPG handling wrong

2023-12-24 Thread Jörg Frings-Fürst
Package: evolution Version: 3.50.2-1 Severity: critical I send all my e-mails with a PGP signature. If the recipient replies including my signature, the email is displayed as "partially signed with GPG" and the reply is hidden. This is incorrect, as it suggests that the reply is partially sig

Bug#1000044: ccze: depends on obsolete pcre3 library

2023-12-24 Thread Yavor Doganov
Axel Beckert wrote: > sorry for the late reply, but I only managed to continue on this now > as I'm on holidays now. No problem at all, we are all busy. And it's not late according to my standards. :) > I though got another crash on this line: > > Dec 24 06:43:16 c6 kernel: net_ratelimit: 1 ca

Bug#1057240: alsa-utils: diff for NMU version 1.2.10-1.1

2023-12-24 Thread Chris Hofstaedtler
Control: tags 1057240 + patch Control: tags 1057240 + pending Dear maintainer, I've prepared an NMU for alsa-utils (versioned as 1.2.10-1.1) and uploaded it to DELAYED/7. The NMU/patch also fixes the install path for systemd units and moves the d-i script. Chris diff -Nru alsa-utils-1.2.10/deb

Processed: alsa-utils: diff for NMU version 1.2.10-1.1

2023-12-24 Thread Debian Bug Tracking System
Processing control commands: > tags 1057240 + patch Bug #1057240 [src:alsa-utils] alsa-utils: will FTBFS when udev.pc changes udevdir Ignoring request to alter tags of bug #1057240 to the same tags previously set > tags 1057240 + pending Bug #1057240 [src:alsa-utils] alsa-utils: will FTBFS when u

Bug#1057231: udev.pc was changed

2023-12-24 Thread Chris Hofstaedtler
severity 1057231 serious severity 1057240 serious severity 1057245 serious severity 1058828 serious thanks udev.pc was changed today. Your package will now either FTBFS or introduce a policy violation on a rebuild. Chris

Processed: udev.pc was changed

2023-12-24 Thread Debian Bug Tracking System
Processing commands for cont...@bugs.debian.org: > severity 1057231 serious Bug #1057231 [btrfs-progs] btrfs-progs: will FTBFS when udev.pc changes udevdir Severity set to 'serious' from 'important' > severity 1057240 serious Bug #1057240 [src:alsa-utils] alsa-utils: will FTBFS when udev.pc change

Bug#1000044: marked as done (ccze: depends on obsolete pcre3 library)

2023-12-24 Thread Debian Bug Tracking System
Your message dated Sun, 24 Dec 2023 12:34:04 + with message-id and subject line Bug#144: fixed in ccze 0.2.1-8 has caused the Debian Bug report #144, regarding ccze: depends on obsolete pcre3 library to be marked as done. This means that you claim that the problem has been dealt with.

Bug#1058767: netplug: unmaintained

2023-12-24 Thread Pali Rohár
On Wednesday 20 December 2023 22:32:38 Chris Hofstaedtler wrote: > Hi, > > * Pali Rohár [231216 11:35]: > > On Friday 15 December 2023 21:56:01 Chris Hofstaedtler wrote: > > Hello, I talked with the author of the netplug (Bryan O'Sullivan) and I > > got permission to continue working on this proj

Bug#1058767: closing 1058767

2023-12-24 Thread Pali Rohár
close 1058767 thanks

Processed: closing 1058767

2023-12-24 Thread Debian Bug Tracking System
Processing commands for cont...@bugs.debian.org: > close 1058767 Bug #1058767 [src:netplug] netplug: unmaintained Marked Bug as done > thanks Stopping processing here. Please contact me if you need assistance. -- 1058767: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1058767 Debian Bug Track

Bug#1059266: error: cannot verify inline signature

2023-12-24 Thread Aurelien Jarno
Hi On 2023-12-22 23:30, Guillem Jover wrote: > I'll prepare an upload right away and force the code to use gpg for > now (as it was used before the recent upload, instead of trying gpgv, > sqop, pgpainless-cli, or sq), until I've devised a better migration > plan, or implemented enough configurati

Bug#1000044: ccze: depends on obsolete pcre3 library

2023-12-24 Thread Axel Beckert
Control: tag -1 + pending Hi Yavor, sorry for the late reply, but I only managed to continue on this now as I'm on holidays now. Yavor Doganov wrote: > Here it is -- no memory leaks and I could not obtain crash or abort > with the logs I've tested. Note that while my original patch > introduced

Processed: Re: Bug#1000044: ccze: depends on obsolete pcre3 library

2023-12-24 Thread Debian Bug Tracking System
Processing control commands: > tag -1 + pending Bug #144 [src:ccze] ccze: depends on obsolete pcre3 library Added tag(s) pending. -- 144: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=144 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems

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

2023-12-24 Thread Debian Bug Tracking System
Your message dated Sun, 24 Dec 2023 11:34:05 + with message-id and subject line Bug#1058393: fixed in autoflake 2.2.1-2 has caused the Debian Bug report #1058393, regarding autoflake: FTBFS: dh_auto_test: error: pybuild --test -i python{version} -p "3.12 3.11" returned exit code 13 to be mark

Bug#1056229: marked as done (autoflake's autopkg tests fail with Python 3.12)

2023-12-24 Thread Debian Bug Tracking System
Your message dated Sun, 24 Dec 2023 11:34:05 + with message-id and subject line Bug#1056229: fixed in autoflake 2.2.1-2 has caused the Debian Bug report #1056229, regarding autoflake's autopkg tests fail with Python 3.12 to be marked as done. This means that you claim that the problem has bee

Bug#1052740: marked as done (graphite2: FTBFS: graph_legend.dot:1: error: Problems running dot: exit code=1, command='dot', arguments='"/<>/build/doc/doxygen/html/graph_legend.dot" -Tpng

2023-12-24 Thread Debian Bug Tracking System
Your message dated Sun, 24 Dec 2023 11:04:46 + with message-id and subject line Bug#1052740: fixed in graphite2 1.3.14-2 has caused the Debian Bug report #1052740, regarding graphite2: FTBFS: graph_legend.dot:1: error: Problems running dot: exit code=1, command='dot', arguments='"/<>/build/d

Processed: Re:Bug#1058876 libopenmpi-dev: paths missing /usr/include...(for fortran mpi.mod)

2023-12-24 Thread Debian Bug Tracking System
Processing commands for cont...@bugs.debian.org: > reopen 1058876 Bug #1058876 {Done: Alastair McKinstry } [libopenmpi-dev] libopenmpi-dev: paths missing /usr/include...(for fortran mpi.mod) 'reopen' may be inappropriate when a bug has been closed with a version; all fixed versions will be cleare

Bug#1058876: libopenmpi-dev: paths missing /usr/include...(for fortran mpi.mod)

2023-12-24 Thread Drew Parsons
reopen 1058876 block 1058944 by 1058876 thanks Alas, the fix in openmpi 4.1.6-3 for the include path to the openmpi fortran modules has hardcoded x86_64-linux-gnu This is preventing builds and tests on other architectures, e.g. rebuilding sundials for the petsc transition. I think openmpi's

Bug#1052740: marked as pending in graphite2

2023-12-24 Thread Rene Engelhard
Control: tag -1 pending Hello, Bug #1052740 in graphite2 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/libreoffice-team/graphite2/-/commit/966553657a7a75e527c

Processed: Bug#1052740 marked as pending in graphite2

2023-12-24 Thread Debian Bug Tracking System
Processing control commands: > tag -1 pending Bug #1052740 [src:graphite2] graphite2: FTBFS: graph_legend.dot:1: error: Problems running dot: exit code=1, command='dot', arguments='"/<>/build/doc/doxygen/html/graph_legend.dot" -Tpng -o "/<>/build/doc/doxygen/html/graph_legend.png"' Added tag(s)

Bug#1059389: r-cran-ggeffects: autopkgtest regression

2023-12-24 Thread Graham Inggs
Source: r-cran-ggeffects Version: 1.3.2+dfsg-1 Severity: serious User: debian...@lists.debian.org Usertags: regression Hi Maintainer Since the upload of r-cran-emmeans 1.9.0+dfsg-1, the autopkgtest of r-cran-ggeffects is failing [1]. I've copied what I hope is the relevant part of the log below.

Bug#1052740: graphite2: FTBFS: graph_legend.dot:1: error: Problems running dot: exit code=1, command='dot', arguments='"/<>/build/doc/doxygen/html/graph_legend.dot" -Tpng -o "/<

2023-12-24 Thread Rene Engelhard
Hi, Am 23.12.23 um 11:43 schrieb Rene Engelhard: Hi, Am 23.12.23 um 02:40 schrieb Bastian Germann: graph_legend.dot should have quotes around the font name references. Ah, thanks. Unfortunately this is a generated file... And yes, I also noticed that the FreeSans.ttf is at fault. Indeed I a