Bug#1033147: accountsservice: autopkgtest fails when using a bookworm kernel

2024-08-07 Thread Paul Gevers
Hi Simon, On 07-08-2024 16:34, Simon McVittie wrote: So I think that theory is consistent with why sid's accountsservice now passes its autopkgtest when run in lxc on bookworm. I confirm that on ci.d.n the test in unstable now passes on a bookworm kernel on amd64, armel, armhf, i386 and ppc64

Bug#1072400: marked as done (avifile: FTBFS with ffmpeg 7.0: aviread/FFReadHandler.cpp:97:42: error: ‘AVCodecContext’ {aka ‘struct AVCodecContext’} has no member named ‘channels’)

2024-08-07 Thread Debian Bug Tracking System
Your message dated Thu, 08 Aug 2024 06:19:54 + with message-id and subject line Bug#1072400: fixed in avifile 1:0.7.48~20090503.ds-28 has caused the Debian Bug report #1072400, regarding avifile: FTBFS with ffmpeg 7.0: aviread/FFReadHandler.cpp:97:42: error: ‘AVCodecContext’ {aka ‘struct AVCo

Processed: severity of 1018424 is serious

2024-08-07 Thread Debian Bug Tracking System
Processing commands for cont...@bugs.debian.org: > severity 1018424 serious Bug #1018424 [src:nosexcover] nosexcover: build-depends on python3-nose or uses it for autopkgtest Severity set to 'serious' from 'important' > thanks Stopping processing here. Please contact me if you need assistance. -

Processed: severity of 1071922 is serious

2024-08-07 Thread Debian Bug Tracking System
Processing commands for cont...@bugs.debian.org: > severity 1071922 serious Bug #1071922 [src:python-proboscis] RM: python-proboscis Severity set to 'serious' from 'normal' > thanks Stopping processing here. Please contact me if you need assistance. -- 1071922: https://bugs.debian.org/cgi-bin/bu

Bug#1077405: Bug #1077405: pysodium-0.7.18.tar.gz.asc missing?

2024-08-07 Thread Joost van Baal-Ilić
Hi stef, I just found out https://pypi.org/project/pysodium/#files lacks a pysodium-0.7.18.tar.gz.asc . (It's not published on https://github.com/stef/pysodium/releases either.) (You did sign your pysodium releases in the past, didn't you?) Could you please pgp sign your release, and upload t

Processed: Bug#1077405 marked as pending in pysodium

2024-08-07 Thread Debian Bug Tracking System
Processing control commands: > tag -1 pending Bug #1077405 [src:pysodium] pysodium: FTBFS: setuptools.extern.packaging.version.InvalidVersion: Invalid version: '0.7.0_0' Added tag(s) pending. -- 1077405: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1077405 Debian Bug Tracking System Contac

Bug#1077405: marked as pending in pysodium

2024-08-07 Thread Joost van Baal
Control: tag -1 pending Hello, Bug #1077405 in pysodium 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/pysodium/-/commit/7050f37153f39ddec

Bug#1073898: marked as done (FTBFS with OCaml 5.2.0 (Uses String.capitalize))

2024-08-07 Thread Debian Bug Tracking System
Your message dated Thu, 08 Aug 2024 04:34:21 + with message-id and subject line Bug#1073898: fixed in ocaml-merlin 5.1-502+ds-1 has caused the Debian Bug report #1073898, regarding FTBFS with OCaml 5.2.0 (Uses String.capitalize) to be marked as done. This means that you claim that the problem

Bug#1074534: [Debian-med-packaging] Bug#1074534: dcm2niix: CVE-2024-27629

2024-08-07 Thread Salvatore Bonaccorso
Hi Étienne, On Wed, Aug 07, 2024 at 10:54:25PM +0200, Étienne Mollier wrote: > Control: found -1 1.0.20220720-1 > Control: notfound -1 1.0.20201102-1 > Control: tags -1 + bookworm > > Greetings, > > I tried to stress the CVE-2024-27629 affecting dcm2niix: > | An issue in dc2niix before v.1.0.202

Bug#1078190: chiark-utils:FTBFS:build failure(compile failed)

2024-08-07 Thread Yue Gui
Source: chiark-utils Version: 7.0.1 Severity: serious Tags: FTBFS, patch User: debian-ri...@lists.debian.org Usertags: riscv64 X-Debbugs-Cc: debian-ri...@lists.debian.org Dear chiark-utils Maintainer, The package chiark-utils build failed on arch riscv64, amd64,arm64 and most 64bit arch.The crucia

Bug#1058764: marked as done (opendmarc: installs deprecated /lib/opendmarc/opendmarc.service.generate)

2024-08-07 Thread Debian Bug Tracking System
Your message dated Thu, 08 Aug 2024 00:57:11 + with message-id and subject line Bug#1058764: fixed in opendmarc 1.4.2-5 has caused the Debian Bug report #1058764, regarding opendmarc: installs deprecated /lib/opendmarc/opendmarc.service.generate to be marked as done. This means that you clai

Bug#1058764: opendmarc: diff for NMU version 1.4.2-4.2

2024-08-07 Thread Scott Kitterman
On Tue, 6 Aug 2024 19:24:35 +0200 Chris Hofstaedtler wrote: > Control: tags 1058764 + patch > > Hi, > > > I’m very far away from this project. If you have a patch ready it is > > welcome. thank you. > > took a while, but please find a patch attached now. > > Chris Thanks. Uploaded. Scott K

Bug#1077434: unittest2: FTBFS: TypeError: expected string or bytes-like object, got 'late_version'

2024-08-07 Thread Alexandre Detiste
python-funcsigs is the only reverse dependency that will need a tiny & trivial patch. Don't waste time keeping this package alive. https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1078184

Processed: block 1053138 with 1072060 1078187

2024-08-07 Thread Debian Bug Tracking System
Processing commands for cont...@bugs.debian.org: > block 1053138 with 1072060 1078187 Bug #1053138 [src:unittest2] unittest2: RM unittest2 1053138 was blocked by: 1058975 1059888 1060632 1060641 1066129 1066063 1060637 1066133 1066135 1058969 1058984 1058980 1066132 1066130 1058959 1078185 107818

Processed: severity of 1058970 is serious

2024-08-07 Thread Debian Bug Tracking System
Processing commands for cont...@bugs.debian.org: > severity 1058970 serious Bug #1058970 [src:pgxnclient] pgxnclient: please remove extraneous stale dependency on python3-unittest2 Severity set to 'serious' from 'normal' > thanks Stopping processing here. Please contact me if you need assistance

Processed: block 1053138 with 1078184 1078185

2024-08-07 Thread Debian Bug Tracking System
Processing commands for cont...@bugs.debian.org: > block 1053138 with 1078184 1078185 Bug #1053138 [src:unittest2] unittest2: RM unittest2 1053138 was blocked by: 1066135 1060634 1066130 1060632 1059888 1058975 1058984 1058970 1060641 1066129 1058976 1060637 1058980 1066132 1058968 1058969 105897

Bug#1073608: Bug#1074014: Bug#1073608: Bug#1074014: Bug#1073622: Bug#1073608: mksh, pax: no move to /usr going to happen, because:

2024-08-07 Thread Sam Hartman
> "Helmut" == Helmut Grohne writes: Helmut> In bullseye and earlier, I guess it works. Helmut> If you start with bullseye or earlier, upgrade to bookworm Helmut> and then to trixie, it continues to work, because the dash Helmut> maintainer scripts preserve any diversion that

Processed: tagging 1064126

2024-08-07 Thread Debian Bug Tracking System
Processing commands for cont...@bugs.debian.org: > tags 1064126 + pending Bug #1064126 [libnss-libvirt,libvirt-daemon-system] libvirt: install NSS modules and systemd units into /usr Added tag(s) pending. > thanks Stopping processing here. Please contact me if you need assistance. -- 1064126: h

Processed: Re: [Debian-med-packaging] Bug#1074534: dcm2niix: CVE-2024-27629

2024-08-07 Thread Debian Bug Tracking System
Processing control commands: > found -1 1.0.20220720-1 Bug #1074534 {Done: Étienne Mollier } [src:dcm2niix] dcm2niix: CVE-2024-27629 Ignoring request to alter found versions of bug #1074534 to the same values previously set > notfound -1 1.0.20201102-1 Bug #1074534 {Done: Étienne Mollier } [src:

Bug#1074534: [Debian-med-packaging] Bug#1074534: dcm2niix: CVE-2024-27629

2024-08-07 Thread Étienne Mollier
Control: found -1 1.0.20220720-1 Control: notfound -1 1.0.20201102-1 Control: tags -1 + bookworm Greetings, I tried to stress the CVE-2024-27629 affecting dcm2niix: | An issue in dc2niix before v.1.0.20240202 allows a local attacker to | execute arbitrary code via the generated file name is not p

Bug#1074837: marked as done (bambootracker: ftbfs with GCC-14)

2024-08-07 Thread Debian Bug Tracking System
Your message dated Wed, 07 Aug 2024 20:41:52 + with message-id and subject line Bug#1074837: fixed in bambootracker 0.6.3-3 has caused the Debian Bug report #1074837, regarding bambootracker: ftbfs with GCC-14 to be marked as done. This means that you claim that the problem has been dealt wit

Bug#1074837: marked as pending in bambootracker

2024-08-07 Thread Dennis Braun
Control: tag -1 pending Hello, Bug #1074837 in bambootracker 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/multimedia-team/bambootracker/-/commit/1b54efa601a7

Processed: Bug#1074837 marked as pending in bambootracker

2024-08-07 Thread Debian Bug Tracking System
Processing control commands: > tag -1 pending Bug #1074837 [src:bambootracker] bambootracker: ftbfs with GCC-14 Added tag(s) pending. -- 1074837: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1074837 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems

Processed: severity of 1077838 is serious, severity of 1077840 is serious, severity of 1077842 is serious

2024-08-07 Thread Debian Bug Tracking System
Processing commands for cont...@bugs.debian.org: > severity 1077838 serious Bug #1077838 [openvpn-dco-dkms] openvpn-dco-dkms: module fails to build for Linux 6.10: error: expected declaration specifiers or '...' before string constant Severity set to 'serious' from 'important' > severity 1077840

Bug#1077416: marked as done (gtk4-layer-shell: FTBFS: dh_auto_test: error: cd obj-x86_64-linux-gnu && DEB_PYTHON_INSTALL_LAYOUT=deb LC_ALL=C.UTF-8 MESON_TESTTHREADS=8 meson test returned exit code 31)

2024-08-07 Thread Debian Bug Tracking System
Your message dated Wed, 07 Aug 2024 19:49:55 + with message-id and subject line Bug#1077416: fixed in gtk4-layer-shell 1.0.2-4 has caused the Debian Bug report #1077416, regarding gtk4-layer-shell: FTBFS: dh_auto_test: error: cd obj-x86_64-linux-gnu && DEB_PYTHON_INSTALL_LAYOUT=deb LC_ALL=C.U

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

2024-08-07 Thread Debian Bug Tracking System
Your message dated Wed, 07 Aug 2024 19:26:20 + with message-id and subject line Bug#1064701: fixed in python-altair 5.0.1-2 has caused the Debian Bug report #1064701, regarding python-altair: FTBFS: dh_auto_test: error: pybuild --test --test-pytest -i python{version} -p "3.12 3.11" returned e

Bug#1077396: marked as done (units-cpp: FTBFS: main.cpp:1370:27: error: ‘setprecision’ is not a member of ‘std’)

2024-08-07 Thread Debian Bug Tracking System
Your message dated Wed, 07 Aug 2024 19:27:26 + with message-id and subject line Bug#1077396: fixed in units-cpp 2.3.3+ds-4 has caused the Debian Bug report #1077396, regarding units-cpp: FTBFS: main.cpp:1370:27: error: ‘setprecision’ is not a member of ‘std’ to be marked as done. This means

Bug#1077405: bump to 0.7.18 hopefully that fixes this issue

2024-08-07 Thread stef
howdy, (pysodium upstream here) i just checked it, the culprit is, that back in the days i published 0.7.0 as 0.7.0-0 on pypi. none of the newer version have that -0 postfix, so any later version should be ok. of course the best would be the latest, 0.7.18.

Bug#1077405: bump to 0.7.18 hopefully that fixes this issue

2024-08-07 Thread stef
howdy, (pysodium upstream here) i'm a bit confused, 0.7.0 is packaged according to the build log, and it is called 0.7.0_0 - i have no idea where the _0 postfix comes from. nota bene pysodium is already are at 0.7.18 and according to https://pypi.debian.net/pysodium/ there is awareness of a newe

Processed: tagging 1052826

2024-08-07 Thread Debian Bug Tracking System
Processing commands for cont...@bugs.debian.org: > tags 1052826 + wontfix Bug #1052826 [src:entrypoints] entrypoints: FTBFS: dh_auto_test: error: pybuild --test --test-pytest -i python{version} -p 3.11 returned exit code 13 Added tag(s) wontfix. > thanks Stopping processing here. Please contact

Processed: Bug#1073780 marked as pending in runit

2024-08-07 Thread Debian Bug Tracking System
Processing control commands: > tag -1 pending Bug #1073780 [runit,runit-init] src:runit: move aliased files from / to /usr (DEP17) Ignoring request to alter tags of bug #1073780 to the same tags previously set -- 1073780: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1073780 Debian Bug Trac

Processed: Bug#1075484 marked as pending in runit

2024-08-07 Thread Debian Bug Tracking System
Processing control commands: > tag -1 pending Bug #1075484 [src:runit] runit: ftbfs with GCC-14 Ignoring request to alter tags of bug #1075484 to the same tags previously set -- 1075484: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1075484 Debian Bug Tracking System Contact ow...@bugs.debia

Bug#1075484: marked as pending in runit

2024-08-07 Thread Lorenzo Puliti
Control: tag -1 pending Hello, Bug #1075484 in runit 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/debian/runit/-/commit/3e3ceeebb948d41332a8930594010f44ebd19

Bug#1073780: marked as pending in runit

2024-08-07 Thread Lorenzo Puliti
Control: tag -1 pending Hello, Bug #1073780 in runit 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/debian/runit/-/commit/a5d45f277169cf3e624c8a857b993992ac4c5

Bug#1077326: marked as done (libgcrypt20 FTBFS on armhf with gcc 14)

2024-08-07 Thread Debian Bug Tracking System
Your message dated Wed, 07 Aug 2024 17:25:22 + with message-id and subject line Bug#1077326: fixed in libgcrypt20 1.11.0-6 has caused the Debian Bug report #1077326, regarding libgcrypt20 FTBFS on armhf with gcc 14 to be marked as done. This means that you claim that the problem has been deal

Bug#1075075: marked as done (hylafax: ftbfs with GCC-14)

2024-08-07 Thread Debian Bug Tracking System
Your message dated Wed, 07 Aug 2024 17:24:47 + with message-id and subject line Bug#1075075: fixed in hylafax 3:6.0.7-10 has caused the Debian Bug report #1075075, regarding hylafax: ftbfs with GCC-14 to be marked as done. This means that you claim that the problem has been dealt with. If thi

Bug#1075397: marked as done (prime-phylo: ftbfs with GCC-14)

2024-08-07 Thread Debian Bug Tracking System
Your message dated Wed, 07 Aug 2024 16:53:45 + with message-id and subject line Bug#1075397: fixed in prime-phylo 1.0.11-12 has caused the Debian Bug report #1075397, regarding prime-phylo: ftbfs with GCC-14 to be marked as done. This means that you claim that the problem has been dealt with.

Bug#1077399: marked as done (graphviz: FTBFS: ns.c:709:37: error: passing argument 4 of 'qsort' from incompatible pointer type [-Wincompatible-pointer-types])

2024-08-07 Thread Debian Bug Tracking System
Your message dated Wed, 07 Aug 2024 16:49:31 + with message-id and subject line Bug#1077399: fixed in graphviz 2.42.4-2 has caused the Debian Bug report #1077399, regarding graphviz: FTBFS: ns.c:709:37: error: passing argument 4 of 'qsort' from incompatible pointer type [-Wincompatible-pointe

Bug#1074658: marked as done (kissplice: FTBFS: dh_auto_test: error: cd obj-x86_64-linux-gnu && make -j8 test ARGS\+=--verbose ARGS\+=-j8 returned exit code 2)

2024-08-07 Thread Debian Bug Tracking System
Your message dated Wed, 07 Aug 2024 16:49:44 + with message-id and subject line Bug#1074658: fixed in kissplice 2.6.7-1 has caused the Debian Bug report #1074658, regarding kissplice: FTBFS: dh_auto_test: error: cd obj-x86_64-linux-gnu && make -j8 test ARGS\+=--verbose ARGS\+=-j8 returned exi

Bug#1073482: marked as done (kissplice: FTBFS: make[3]: *** [doc/CMakeFiles/doc.dir/build.make:78: doc/user_guide.pdf] Error 1)

2024-08-07 Thread Debian Bug Tracking System
Your message dated Wed, 07 Aug 2024 16:49:44 + with message-id and subject line Bug#1073482: fixed in kissplice 2.6.7-1 has caused the Debian Bug report #1073482, regarding kissplice: FTBFS: make[3]: *** [doc/CMakeFiles/doc.dir/build.make:78: doc/user_guide.pdf] Error 1 to be marked as done.

Bug#1078098: marked as done (libcrypt-gcrypt-perl: Can't link/include C library 'gcrypt', aborting)

2024-08-07 Thread Debian Bug Tracking System
Your message dated Wed, 07 Aug 2024 15:34:19 + with message-id and subject line Bug#1078098: fixed in libcrypt-gcrypt-perl 1.26-7 has caused the Debian Bug report #1078098, regarding libcrypt-gcrypt-perl: Can't link/include C library 'gcrypt', aborting to be marked as done. This means that yo

Bug#1078087: marked as done (bowtie2: test dependency on non-free libmath-random-perl)

2024-08-07 Thread Debian Bug Tracking System
Your message dated Wed, 07 Aug 2024 15:30:45 + with message-id and subject line Bug#1078087: fixed in bowtie2 2.5.4-1 has caused the Debian Bug report #1078087, regarding bowtie2: test dependency on non-free libmath-random-perl to be marked as done. This means that you claim that the problem

Bug#1078168: initramfs-tools: failing autopkgtest prevents testing migration

2024-08-07 Thread Chris Hofstaedtler
Source: initramfs-tools Version: 0.143.1 Severity: serious Filing with sev: serious as testing migration is blocked by the failing autopkgtest. It currently fails on: armhf and ppc64el. On ppc64el, the relevant output seems to be: autopkgtest [03:08:30]: test qemu-separate-usr: [---

Processed: Bug#1078098 marked as pending in libcrypt-gcrypt-perl

2024-08-07 Thread Debian Bug Tracking System
Processing control commands: > tag -1 pending Bug #1078098 [src:libcrypt-gcrypt-perl] libcrypt-gcrypt-perl: Can't link/include C library 'gcrypt', aborting Added tag(s) pending. -- 1078098: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1078098 Debian Bug Tracking System Contact ow...@bugs.d

Bug#1078098: marked as pending in libcrypt-gcrypt-perl

2024-08-07 Thread gregor herrmann
Control: tag -1 pending Hello, Bug #1078098 in libcrypt-gcrypt-perl 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/perl-team/modules/packages/libcrypt-gcrypt-p

Bug#1075397: marked as pending in prime-phylo

2024-08-07 Thread Étienne Mollier
Control: tag -1 pending Hello, Bug #1075397 in prime-phylo 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/med-team/prime-phylo/-/commit/ac2e6e0ed190391b9c06b1e

Processed: Bug#1075397 marked as pending in prime-phylo

2024-08-07 Thread Debian Bug Tracking System
Processing control commands: > tag -1 pending Bug #1075397 [src:prime-phylo] prime-phylo: ftbfs with GCC-14 Added tag(s) pending. -- 1075397: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1075397 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems

Processed: bug 1078098 is forwarded to https://github.com/alranel/Crypt-GCrypt/pull/4

2024-08-07 Thread Debian Bug Tracking System
Processing commands for cont...@bugs.debian.org: > forwarded 1078098 https://github.com/alranel/Crypt-GCrypt/pull/4 Bug #1078098 [src:libcrypt-gcrypt-perl] libcrypt-gcrypt-perl: Can't link/include C library 'gcrypt', aborting Set Bug forwarded-to-address to 'https://github.com/alranel/Crypt-GCry

Bug#1077854: Fixed upstream (libcurl4t64: SIGPIPE leaks in some cases)

2024-08-07 Thread Carlos Henrique Lima Melara
Hi, On Mon, Aug 05, 2024 at 07:49:14PM GMT, Raphaël Halimi wrote: > Le 05/08/2024 à 19:40, Carlos Henrique Lima Melara a écrit : > > On Mon, Aug 05, 2024 at 02:55:49PM GMT, Raphaël Halimi wrote: > > > Upstream has released a fix: > > > > > > https://github.com/curl/curl/commit/3eec5afbd0b6377eca8

Bug#1078098: libcrypt-gcrypt-perl: Can't link/include C library 'gcrypt', aborting

2024-08-07 Thread gregor herrmann
On Wed, 07 Aug 2024 00:30:47 +0300, Niko Tyni wrote: > Rebuilding this package on current sid produces an empty package. Ouch. Once again … > So this is a GCC 14 related regression and is fixed by including > the gcrypt.h header with the version check. Patch attached. Great! > As for not fai

Processed: tagging 1075314, tagging 1073665, tagging 1073644, tagging 1073610, tagging 1075329 ...

2024-08-07 Thread Debian Bug Tracking System
Processing commands for cont...@bugs.debian.org: > tags 1075314 - sid trixie Bug #1075314 {Done: Christoph Martin } [src:nfs-ganesha] nfs-ganesha: ftbfs with GCC-14 Removed tag(s) trixie and sid. > tags 1073665 - sid trixie Bug #1073665 [libreswan] libreswan: move aliased files from / to /usr (DE

Bug#1033147: accountsservice: autopkgtest fails when using a bookworm kernel

2024-08-07 Thread Simon McVittie
On Mon, 05 Aug 2024 at 00:43:06 +0100, Simon McVittie wrote: > A sid lxc container in a bookworm VM (built with a-b-lxc from bookworm) > doesn't currently start up at all for me I reported that separately, as #1078165. After resolving that by using autopkgtest(-virt-lxc) from bookworm-backports,

Processed: Re: Bug#1078161: nvidia-settings-tesla: depends on to-be-removed package nvidia-tesla-alternative

2024-08-07 Thread Debian Bug Tracking System
Processing control commands: > retitle -1 nvidia-settings-tesla: should not be released with trixie Bug #1078161 [nvidia-settings-tesla] nvidia-settings-tesla: depends on to-be-removed package nvidia-tesla-alternative Changed Bug title to 'nvidia-settings-tesla: should not be released with trixi

Bug#1078161: nvidia-settings-tesla: depends on to-be-removed package nvidia-tesla-alternative

2024-08-07 Thread Andreas Beckmann
Control: retitle -1 nvidia-settings-tesla: should not be released with trixie On 07/08/2024 15.49, Helmut Grohne wrote: I'm not sure what the desired solution should be, but something needs to be done here and this bug documents the need for action. not needed without the corresponding driver

Processed: Re-assigning to mercurial, should be fixed there

2024-08-07 Thread Debian Bug Tracking System
Processing control commands: > reassign -1 src:mercurial Bug #1076449 [python3.12] mercurial: does not start anymore with python 3.12.4-3, hgdemandimport problem Bug #1076493 [python3.12] python3.12: latest update breaks mercurial. Bug reassigned from package 'python3.12' to 'src:mercurial'. Bug

Bug#1076449: Re-assigning to mercurial, should be fixed there

2024-08-07 Thread Matthias Klose
Control: reassign -1 src:mercurial Control: severity -1 important Python 3.12.5 released with that patch, so I assume upstream will not fix that. The Debian bug contains a proposal for a less invasive fix in mercurial, therefore re-assigning and keeping the bug open

Bug#1078162: nut-server: riello_usb, Failed to open device

2024-08-07 Thread Daniele Nuzzo
Package: nut-server Version: 2.8.0-7 Severity: critical Justification: communication with ups fail Dear maintainer, Here goes the description of a critical bug in the driver for the Riello UPS SPW 5000 A3 (riello_usb), perhaps affecting other Riello UPS models. Environment --- Compute

Bug#1078161: nvidia-settings-tesla: depends on to-be-removed package nvidia-tesla-alternative

2024-08-07 Thread Helmut Grohne
Package: nvidia-settings-tesla Version: 525.147.05-1 Severity: serious Tags: trixie Justification: unsatisfiable dependency in trixie soon Hi, we earlier agreed that nvidia-graphics-drivers-tesla should not be included with trixie. Unfortunately, nvidia-settings-tesla has a dependency on nvidia-t

Bug#1078159: r-cran-bayestestr: autopkgtest regression in testing

2024-08-07 Thread Graham Inggs
Source: r-cran-bayestestr Version: 0.13.2-1 Severity: serious User: debian...@lists.debian.org Usertags: regression Hi Maintainer Sometime around 2024-07-04, r-cran-bayestestr's autopkgtest regressed in testing [1]. I've copied what I hope is the relevant part of the log in unstable [2] (which s

Bug#1060229: fuse,fuse3,ntfs-3g: migrate dpkg-statoverride for UsrMerge?

2024-08-07 Thread Helmut Grohne
Control: tags -1 + patch On Sun, Jan 07, 2024 at 10:52:52PM +0100, Chris Hofstaedtler wrote: > fuse, fuse3, and ntfs-3g use dpkg-statoverride on aliased paths in > /bin: /bin/fusermount, /bin/fusermount3. > > They do so in their postinst scripts, only checking if a > statoverride exists. If not,

Processed: Re: Bug#1060229: fuse,fuse3,ntfs-3g: migrate dpkg-statoverride for UsrMerge?

2024-08-07 Thread Debian Bug Tracking System
Processing control commands: > tags -1 + patch Bug #1060229 [ntfs-3g] fuse,fuse3,ntfs-3g: migrate dpkg-statoverride for UsrMerge? Added tag(s) patch. -- 1060229: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1060229 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems

Processed: Re: Bug#1060229: fuse,fuse3,ntfs-3g: migrate dpkg-statoverride for UsrMerge?

2024-08-07 Thread Debian Bug Tracking System
Processing control commands: > tags -1 + patch Bug #1060229 [ntfs-3g] fuse,fuse3,ntfs-3g: migrate dpkg-statoverride for UsrMerge? Ignoring request to alter tags of bug #1060229 to the same tags previously set -- 1060229: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1060229 Debian Bug Track

Bug#1078158: gcc-doc-defaults: switch to GCC 14

2024-08-07 Thread Andreas Beckmann
Source: gcc-doc-defaults Version: 5:27 Severity: serious Tags: ftbfs Justification: fails to build from source (but built successfully in the past) gcc-doc-defaults started to FTBFS when the default compiler has been switched to GCC 14. Please update the doc package to GCC 14, too. Andreas

Bug#1078156: bart-cuda: FTBFS in sid: ./test_convcorr segfaults

2024-08-07 Thread Andreas Beckmann
Package: bart-cuda Version: 0.8.00-2 Severity: serious Tags: ftbfs sid trixie Justification: fails to build from source Hi, bart-cuda recently started to FTBFS in sid. This could be related to GCC 14 being the defult compiler now. Or to the version skew between src:bart and src:bart-cuda. ...

Bug#1077153: marked as done (ampliconnoise FTBFS with gcc 14)

2024-08-07 Thread Debian Bug Tracking System
Your message dated Wed, 07 Aug 2024 12:49:17 + with message-id and subject line Bug#1077153: fixed in ampliconnoise 1.29-12 has caused the Debian Bug report #1077153, regarding ampliconnoise FTBFS with gcc 14 to be marked as done. This means that you claim that the problem has been dealt with

Processed: found 1076683 in 1.70.0+dfsg1-7~deb11u1, severity of 1077839 is serious ...

2024-08-07 Thread Debian Bug Tracking System
Processing commands for cont...@bugs.debian.org: > found 1076683 1.70.0+dfsg1-7~deb11u1 Bug #1076683 [rust-web-doc] rust-web-doc: missing Conflicts: rust-mozilla-doc Marked as found in versions rustc-web/1.70.0+dfsg1-7~deb11u1. > severity 1077839 serious Bug #1077839 [rtpengine-kernel-dkms] rtpeng

Bug#1073608: Bug#1074014: Bug#1073622: Bug#1073608: mksh, pax: no move to /usr going to happen, because:

2024-08-07 Thread Helmut Grohne
Hi Thorsten, On Wed, Aug 07, 2024 at 09:59:09AM +, Thorsten Glaser wrote: > >that the way people tend to use mksh is by adding a local diversion for > > Unfortunately not. > > The way we have to do it since squeeze, when dash unilaterally broke > cross-package coordination, is: > > dpkg-rec

Processed: Re: Bug#1067817: libfuse2: move library to /usr (DEP17 P1)

2024-08-07 Thread Debian Bug Tracking System
Processing control commands: > tags -1 + patch Bug #1067817 [libfuse2t64] libfuse2: move library to /usr (DEP17 P1) Added tag(s) patch. -- 1067817: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1067817 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems

Processed: Re: Bug#1060229: fuse,fuse3,ntfs-3g: migrate dpkg-statoverride for UsrMerge?

2024-08-07 Thread Debian Bug Tracking System
Processing control commands: > clone -1 -2 Bug #1060229 [fuse,ntfs-3g] fuse,fuse3,ntfs-3g: migrate dpkg-statoverride for UsrMerge? Bug 1060229 cloned as bug 1078151 > reassign -1 ntfs-3g Bug #1060229 [fuse,ntfs-3g] fuse,fuse3,ntfs-3g: migrate dpkg-statoverride for UsrMerge? Bug reassigned from p

Bug#1067817: libfuse2: move library to /usr (DEP17 P1)

2024-08-07 Thread Helmut Grohne
Control: tags -1 + patch On Tue, Aug 06, 2024 at 07:19:10PM +0200, Chris Hofstaedtler wrote: > Control: tags -1 - patch > > On Wed, Mar 27, 2024 at 08:33:46AM +0100, Helmut Grohne wrote: > > fuse2 is involved in the /usr-move (DEP17) in multiple ways. In this bug > > report, I am staying away fro

Bug#1060229: fuse,fuse3,ntfs-3g: migrate dpkg-statoverride for UsrMerge?

2024-08-07 Thread Helmut Grohne
Control: clone -1 -2 Control: reassign -1 ntfs-3g Control: reassign -2 fuse Control: tags -2 + patch Hi, On Sun, Jan 07, 2024 at 10:52:52PM +0100, Chris Hofstaedtler wrote: > Package: fuse,fuse3,ntfs-3g > X-Debbugs-CC: Laszlo Boszormenyi (GCS) , Helmut Grohne > > > Hello Laszlo! > > fuse, fus

Bug#1078149: irpas: FTBFS on 32-bit architectures with 64-bit time_t

2024-08-07 Thread Andreas Beckmann
Source: irpas Version: 0.10-9 Severity: serious Tags: ftbfs sid trixie Justification: fails to build from source (but built successfully in the past) irpas FTBFS on armhf after the 64-bit time_t switch: icmp_redirect.c:462:27: error: passing argument 1 of 'ctime' from incompatible pointer type [

Bug#1074841: bglibs: diff for NMU version 2.04+dfsg-6.1

2024-08-07 Thread Peter Pentchev
Control: tags 1074841 + patch Control: tags 1074841 + pending Dear maintainer, I've prepared an NMU for bglibs (versioned as 2.04+dfsg-6.1) and uploaded it to DELAYED/7. Please feel free to tell me if I should delay it longer. Regards. -- -- Peter Pentchev r...@ringlet.net r...@debian.org

Processed: bglibs: diff for NMU version 2.04+dfsg-6.1

2024-08-07 Thread Debian Bug Tracking System
Processing control commands: > tags 1074841 + patch Bug #1074841 [src:bglibs] bglibs: ftbfs with GCC-14 Added tag(s) patch. > tags 1074841 + pending Bug #1074841 [src:bglibs] bglibs: ftbfs with GCC-14 Added tag(s) pending. -- 1074841: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1074841 Deb

Processed: OCaml 5.2.0 uploaded to unstable

2024-08-07 Thread Debian Bug Tracking System
Processing commands for cont...@bugs.debian.org: > severity 1073913 serious Bug #1073913 [src:xen] FTBFS with OCaml 5.2.0 (Problem in C stubs) Severity set to 'serious' from 'important' > severity 1074548 serious Bug #1074548 [src:supermin] FTBFS with OCaml 5.2.0 (Uses Pervasives) Severity set to

Bug#1078147: libkdepim-dev: missing Breaks+Replaces: libkf5libkdepim-dev (<< 4:24)

2024-08-07 Thread Andreas Beckmann
Package: libkdepim-dev Version: 4:24.05.2-1 Severity: serious User: debian...@lists.debian.org Usertags: piuparts fileconflict Hi, during a test with piuparts I noticed your package fails to upgrade from 'sid' to 'experimental'. It installed fine in 'sid', then the upgrade to 'experimental' fails

Processed: severity of 1053138 is serious

2024-08-07 Thread Debian Bug Tracking System
Processing commands for cont...@bugs.debian.org: > severity 1053138 serious Bug #1053138 [src:unittest2] unittest2: RM unittest2 Severity set to 'serious' from 'normal' > thanks Stopping processing here. Please contact me if you need assistance. -- 1053138: https://bugs.debian.org/cgi-bin/bugrep

Bug#1078145: trn4: FTBFS with GCC 14: error: return type defaults to 'int'

2024-08-07 Thread Andreas Beckmann
Source: trn4 Version: 4.0-test77-17 Severity: serious Tags: ftbfs Justification: fails to build from source (but built successfully in the past) Hi, trn4 started to FTBFS when GCC 14 was made the default compiler: Checking your choice of C compiler and flags for coherency... I've tried to compil

Processed: found 1077841 in nvidia-graphics-drivers/545.23.06-1, reassign 1078124 to src:nvidia-graphics-drivers ...

2024-08-07 Thread Debian Bug Tracking System
Processing commands for cont...@bugs.debian.org: > found 1077841 nvidia-graphics-drivers/545.23.06-1 Bug #1077841 [src:nvidia-graphics-drivers] build error for kernel 6.10.2 Bug #1078014 [src:nvidia-graphics-drivers] nvidia-kernel-dkms: Does not build with 6.10.3-amd64 Bug #1078018 [src:nvidia-gr

Processed: severity of 1071840 is serious

2024-08-07 Thread Debian Bug Tracking System
Processing commands for cont...@bugs.debian.org: > severity 1071840 serious Bug #1071840 [src:user-session-migration] user-session-migration: please move away from deprecated python3-nose Severity set to 'serious' from 'normal' > thanks Stopping processing here. Please contact me if you need ass

Processed: tagging 1077434

2024-08-07 Thread Debian Bug Tracking System
Processing commands for cont...@bugs.debian.org: > tags 1077434 + wontfix Bug #1077434 [src:unittest2] unittest2: FTBFS: TypeError: expected string or bytes-like object, got 'late_version' Added tag(s) wontfix. > thanks Stopping processing here. Please contact me if you need assistance. -- 1077

Bug#1077153: marked as pending in ampliconnoise

2024-08-07 Thread Étienne Mollier
Control: tag -1 pending Hello, Bug #1077153 in ampliconnoise 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/med-team/ampliconnoise/-/commit/f1fae7f6d271ac9b768

Processed: Bug#1077153 marked as pending in ampliconnoise

2024-08-07 Thread Debian Bug Tracking System
Processing control commands: > tag -1 pending Bug #1077153 [src:ampliconnoise] ampliconnoise FTBFS with gcc 14 Added tag(s) pending. -- 1077153: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1077153 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems

Processed: tags 1078111

2024-08-07 Thread Debian Bug Tracking System
Processing commands for cont...@bugs.debian.org: > tags 1078111 upstream Bug #1078111 [azure-cli] azure-cli - does telemetry upload without asking the user Added tag(s) upstream. > severity 1078111 wishlist Bug #1078111 [azure-cli] azure-cli - does telemetry upload without asking the user Severi

Processed: Re: Bug#1078115: azure-cli - fails to get access token: User 'X' does not exist in MSAL token cache

2024-08-07 Thread Debian Bug Tracking System
Processing control commands: > severity -1 minor Bug #1078115 [azure-cli] azure-cli - fails to get access token: User 'X' does not exist in MSAL token cache Severity set to 'minor' from 'serious' > reassign -1 microsoft-authentication-extensions-for-python Bug #1078115 [azure-cli] azure-cli - fai

Bug#1078115: azure-cli - fails to get access token: User 'X' does not exist in MSAL token cache

2024-08-07 Thread Luca Boccassi
Control: severity -1 minor Control: reassign -1 microsoft-authentication-extensions-for-python On Wed, 7 Aug 2024 10:18:59 +0200 Bastian Blank wrote: > Control: severity -1 serious > > On Wed, Aug 07, 2024 at 09:59:06AM +0200, Bastian Blank wrote: > > With a brand new config and after using "az

Bug#1078141: cufflinks: FTBFS with GCC 14: locfit/c_plot.c:470:14: error: passing argument 1 of 'setvarname' from incompatible pointer type

2024-08-07 Thread Andreas Beckmann
Source: cufflinks Version: 2.2.1+dfsg.1-9 Severity: serious Tags: ftbfs sid trixie Justification: fails to build from source (but built successfully in the past) Hi, cufflinks started to FTBFS when GCC 14 was made the default compiler: gcc -DHAVE_CONFIG_H -I. -I.. -I../src -Wdate-time -D_FORTI

Bug#1078140: plasma-desktoptheme: missing Breaks+Replaces: plasma-framework (<< 6)

2024-08-07 Thread Andreas Beckmann
Package: plasma-desktoptheme Version: 6.1.3-3 Severity: serious User: debian...@lists.debian.org Usertags: piuparts fileconflict Hi, during a test with piuparts I noticed your package fails to upgrade from 'sid' to 'experimental'. It installed fine in 'sid', then the upgrade to 'experimental' fai

Processed: tree-puzzle: ftbfs with failure to link sprng symbols

2024-08-07 Thread Debian Bug Tracking System
Processing control commands: > tag -1 confirmed Bug #1075584 [src:tree-puzzle] tree-puzzle: ftbfs with GCC-14 Added tag(s) confirmed. -- 1075584: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1075584 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems

Bug#1075584: tree-puzzle: ftbfs with failure to link sprng symbols

2024-08-07 Thread Étienne Mollier
Control: tag -1 confirmed Since the bug submission, it seems another issue cropped up. From what I can parse of the new build output, something off went of with the sprng symbols. Relevant part of the build: Use Debian packaged libsprng2. gcc -g -O2 -Werror=implicit-function-dec

Bug#1078137: blimps: FTBFS with GCC 14: error: implicit declaration of function 'gets'

2024-08-07 Thread Andreas Beckmann
Source: blimps Version: 3.9+ds-2 Severity: serious Tags: ftbfs Justification: fails to build from source gcc -Wall -O2 -c blksort.c blksort.c: In function 'main': blksort.c:242:13: error: implicit declaration of function 'gets'; did you mean 'fgets'? [-Wimplicit-function-declaration] 242 |

Bug#1073466: marked as done (389-ds-base: FTBFS: make[2]: *** [Makefile:13095: /<>/rs/rnsslapd/release/librnsslapd.a] Error 101)

2024-08-07 Thread Debian Bug Tracking System
Your message dated Wed, 07 Aug 2024 10:49:26 + with message-id and subject line Bug#1073466: fixed in 389-ds-base 3.1.1+dfsg1-1 has caused the Debian Bug report #1073466, regarding 389-ds-base: FTBFS: make[2]: *** [Makefile:13095: /<>/rs/rnsslapd/release/librnsslapd.a] Error 101 to be marked

Bug#1078136: arb: FTBFS with GCC 14: clustalv.c:130:1: error: return type defaults to 'int'

2024-08-07 Thread Andreas Beckmann
Source: arb Version: 6.0.6-7 Severity: serious Tags: ftbfs Justification: fails to build from source (but built successfully in the past) Hi, arb started to FTBFS when GCC 14 was made the default compiler: [17:16.880788997] Make CLUSTAL make[7]: E

Bug#1075617: marked as done (velvet: ftbfs with GCC-14)

2024-08-07 Thread Debian Bug Tracking System
Your message dated Wed, 07 Aug 2024 10:38:56 + with message-id and subject line Bug#1075617: fixed in velvet 1.2.10+dfsg1-9 has caused the Debian Bug report #1075617, regarding velvet: ftbfs with GCC-14 to be marked as done. This means that you claim that the problem has been dealt with. If t

Processed: lz4: new lz4Config.cmake file causes FTBFS due to bogus xxhash dependency

2024-08-07 Thread Debian Bug Tracking System
Processing control commands: > affects -1 yuzu Bug #1078134 [src:lz4] lz4: new lz4Config.cmake file causes FTBFS due to bogus xxhash dependency Added indication that 1078134 affects yuzu > block 1077401 by -1 Bug #1077401 [src:yuzu] yuzu: FTBFS: collect2: error: ld returned 1 exit status 1077401

Bug#1078133: libyang3: missing Breaks+Replaces: libyang2 (<< 3), libyang2t64 (<< 3)

2024-08-07 Thread Andreas Beckmann
Package: libyang3 Version: 3.1.0+dfsg-4 Severity: serious User: debian...@lists.debian.org Usertags: piuparts fileconflict Hi, during a test with piuparts I noticed your package fails to upgrade from 'bookworm'. It installed fine in 'bookworm', then the upgrade to 'trixie' fails because it tries

Bug#1069384: marked as done (zmat: FTBFS on arm64: cc: error: unrecognized command-line option ‘-msse2’)

2024-08-07 Thread Debian Bug Tracking System
Your message dated Wed, 07 Aug 2024 10:19:53 + with message-id and subject line Bug#1068683: fixed in zmat 0.9.9+ds.1-3 has caused the Debian Bug report #1068683, regarding zmat: FTBFS on arm64: cc: error: unrecognized command-line option ‘-msse2’ to be marked as done. This means that you cl

Bug#1068683: marked as done (zmat: FTBFS: ar: blosc2/blosc/*.o: No such file or directory)

2024-08-07 Thread Debian Bug Tracking System
Your message dated Wed, 07 Aug 2024 10:19:53 + with message-id and subject line Bug#1068683: fixed in zmat 0.9.9+ds.1-3 has caused the Debian Bug report #1068683, regarding zmat: FTBFS: ar: blosc2/blosc/*.o: No such file or directory to be marked as done. This means that you claim that the pr

Bug#1073608: Bug#1074014: Bug#1073622: Bug#1073608: mksh, pax: no move to /usr going to happen, because:

2024-08-07 Thread Thorsten Glaser
(Another data point is that there’s versions of mksh with version numbers larger than what’s in sid around in my own repo, for those wanting to follow CVS snapshots more closely, backported to all versions up to sarge, so bookworm users can very well have mksh packages with a version number that is

Bug#1073608: Bug#1074014: Bug#1073622: Bug#1073608: mksh, pax: no move to /usr going to happen, because:

2024-08-07 Thread Thorsten Glaser
Helmut Grohne dixit: >that the way people tend to use mksh is by adding a local diversion for Unfortunately not. The way we have to do it since squeeze, when dash unilaterally broke cross-package coordination, is: dpkg-reconfigure dash ⇒ remove its owning of /bin/sh (so it reverts to bash) ln

  1   2   >