Bug#1088838: marked as done (fuse2fs: ineffective Replaces due to /usr-move (DEP17 P1))

2024-12-03 Thread Debian Bug Tracking System
Your message dated Wed, 04 Dec 2024 05:34:15 + with message-id and subject line Bug#1088838: fixed in e2fsprogs 1.47.2~rc1-2 has caused the Debian Bug report #1088838, regarding fuse2fs: ineffective Replaces due to /usr-move (DEP17 P1) to be marked as done. This means that you claim that the

Processed: tagging 1088838

2024-12-03 Thread Debian Bug Tracking System
Processing commands for cont...@bugs.debian.org: > tags 1088838 + pending Bug #1088838 [fuse2fs] fuse2fs: ineffective Replaces due to /usr-move (DEP17 P1) Added tag(s) pending. > thanks Stopping processing here. Please contact me if you need assistance. -- 1088838: https://bugs.debian.org/cgi-bi

Bug#1088993: marked as done (ceph: CVE-2024-48916: Authentication bypass in CEPH RadosGW)

2024-12-03 Thread Debian Bug Tracking System
Your message dated Wed, 04 Dec 2024 03:55:09 + with message-id and subject line Bug#1088993: fixed in ceph 18.2.4+ds-11 has caused the Debian Bug report #1088993, regarding ceph: CVE-2024-48916: Authentication bypass in CEPH RadosGW to be marked as done. This means that you claim that the pro

Bug#1088993: marked as pending in ceph

2024-12-03 Thread Daniel Baumann
Control: tag -1 pending Hello, Bug #1088993 in ceph 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/ceph-team/ceph/-/commit/8293d591fee2081bb0916a4bc49b4ee3fa5b

Processed: Bug#1088993 marked as pending in ceph

2024-12-03 Thread Debian Bug Tracking System
Processing control commands: > tag -1 pending Bug #1088993 [src:ceph] ceph: CVE-2024-48916: Authentication bypass in CEPH RadosGW Ignoring request to alter tags of bug #1088993 to the same tags previously set -- 1088993: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1088993 Debian Bug Track

Processed: Bug#1088993 marked as pending in ceph

2024-12-03 Thread Debian Bug Tracking System
Processing control commands: > tag -1 pending Bug #1088993 [src:ceph] ceph: CVE-2024-48916: Authentication bypass in CEPH RadosGW Added tag(s) pending. -- 1088993: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1088993 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems

Bug#1088993: marked as pending in ceph

2024-12-03 Thread Daniel Baumann
Control: tag -1 pending Hello, Bug #1088993 in ceph 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/ceph-team/ceph/-/commit/4a2d88fdc747cce9df9acff483d38b071c08

Bug#1088970: marked as done (python-rioxarray: FTBFS with rasterio 1.4.3 (test failures))

2024-12-03 Thread Debian Bug Tracking System
Your message dated Wed, 04 Dec 2024 00:40:01 + with message-id and subject line Bug#1088970: fixed in python-rioxarray 0.18.1-2 has caused the Debian Bug report #1088970, regarding python-rioxarray: FTBFS with rasterio 1.4.3 (test failures) to be marked as done. This means that you claim that

Bug#1088988: pandas: FTBFS with xarray 2024.11.0 (test failures)

2024-12-03 Thread Rebecca N. Palmer
Not *obviously* known upstream. Some type mismatches (like this one), some shape mismatches that suggest different handling of duplicates in indexes. (There's also two other apparently unrelated issues that can make pandas FTBFS: test_spss_metadata, and parso not supporting python 3.13.) I

Bug#1074981: gdl: FTBFS with gcc-14

2024-12-03 Thread Jeremy Bícha
On Tue, Dec 3, 2024 at 3:12 PM Rebecca N. Palmer wrote: > Control: forwarded -1 https://gitlab.gnome.org/GNOME/gdl/-/issues/9 > (actually Gentoo reporting the same bug, but they don't have a fix either) > > Upstream are considering archiving this project, which suggests but does > not prove that r

Bug#1086345: marked as done (desmume:FTBFS:build failure (error: ‘AT_HWCAP’ undeclared ))

2024-12-03 Thread Debian Bug Tracking System
Your message dated Tue, 03 Dec 2024 22:19:10 + with message-id and subject line Bug#1086345: fixed in desmume 0.9.13-2 has caused the Debian Bug report #1086345, regarding desmume:FTBFS:build failure (error: ‘AT_HWCAP’ undeclared ) to be marked as done. This means that you claim that the prob

Bug#1074854: brasero: FTBFS with gcc-14

2024-12-03 Thread Jeremy Bícha
On Tue, Dec 3, 2024 at 4:48 PM Rebecca N. Palmer wrote: > This applies the above upstream patch to Debian brasero; it builds, but > that's all the testing it's had. > > https://salsa.debian.org/rnpalmer-guest/brasero > > (Not a real merge request because the above repository was created with > 'gi

Bug#1084517: marked as done (pushpin: FTBFS: failed to select a version for the requirement `base64 = "^0.21"`)

2024-12-03 Thread Debian Bug Tracking System
Your message dated Tue, 03 Dec 2024 22:07:42 + with message-id and subject line Bug#1084517: fixed in pushpin 1.39.1-3 has caused the Debian Bug report #1084517, regarding pushpin: FTBFS: failed to select a version for the requirement `base64 = "^0.21"` to be marked as done. This means that

Bug#1074854: brasero: FTBFS with gcc-14

2024-12-03 Thread Rebecca N. Palmer
This applies the above upstream patch to Debian brasero; it builds, but that's all the testing it's had. https://salsa.debian.org/rnpalmer-guest/brasero (Not a real merge request because the above repository was created with 'git push' and hence isn't officially a fork.)

Bug#1088995: matrix-synapse: CVE-2024-52805 CVE-2024-52815 CVE-2024-53863 CVE-2024-53867

2024-12-03 Thread Salvatore Bonaccorso
Source: matrix-synapse Version: 1.116.0-4 Severity: grave Tags: security upstream Justification: user security hole X-Debbugs-Cc: car...@debian.org, Debian Security Team Hi, The following vulnerabilities were published for matrix-synapse. CVE-2024-52805[0]: | Synapse is an open-source Matrix ho

Bug#1088714: marked as done (apache-curator: FTBFS: shutdown(boolean) in org.apache.curator.test.TestingZooKeeperMain.TestZooKeeperServer cannot override shutdown(boolean) in org.apache.zookeeper.serv

2024-12-03 Thread Debian Bug Tracking System
Your message dated Tue, 03 Dec 2024 21:19:16 + with message-id and subject line Bug#1088714: fixed in apache-curator 5.7.1+ds-1 has caused the Debian Bug report #1088714, regarding apache-curator: FTBFS: shutdown(boolean) in org.apache.curator.test.TestingZooKeeperMain.TestZooKeeperServer can

Bug#1088993: ceph: CVE-2024-48916: Authentication bypass in CEPH RadosGW

2024-12-03 Thread Salvatore Bonaccorso
Source: ceph Version: 18.2.4+ds-10 Severity: grave Tags: security upstream Justification: user security hole Forwarded: https://tracker.ceph.com/issues/68836 X-Debbugs-Cc: car...@debian.org, Debian Security Team Hi, The following vulnerability was published for ceph. CVE-2024-48916[0]: Authenti

Bug#1082692: marked as done (pegsolitaire: FTBFS: /usr/bin/ld: src/render.o: undefined reference to symbol 'fmin@@GLIBC_2.2.5')

2024-12-03 Thread Debian Bug Tracking System
Your message dated Tue, 03 Dec 2024 21:09:18 + with message-id and subject line Bug#1087803: fixed in pegsolitaire 0.3-4 has caused the Debian Bug report #1087803, regarding pegsolitaire: FTBFS: /usr/bin/ld: src/render.o: undefined reference to symbol 'fmin@@GLIBC_2.2.5' to be marked as done.

Bug#1087803: marked as done (pegsolitaire: FTBFS: /usr/bin/ld: src/render.o: undefined reference to symbol 'fmin@@GLIBC_2.2.5')

2024-12-03 Thread Debian Bug Tracking System
Your message dated Tue, 03 Dec 2024 21:09:18 + with message-id and subject line Bug#1087803: fixed in pegsolitaire 0.3-4 has caused the Debian Bug report #1087803, regarding pegsolitaire: FTBFS: /usr/bin/ld: src/render.o: undefined reference to symbol 'fmin@@GLIBC_2.2.5' to be marked as done.

Processed: merging 1082692 1087803

2024-12-03 Thread Debian Bug Tracking System
Processing commands for cont...@bugs.debian.org: > merge 1082692 1087803 Bug #1082692 [src:pegsolitaire] pegsolitaire: FTBFS: /usr/bin/ld: src/render.o: undefined reference to symbol 'fmin@@GLIBC_2.2.5' Bug #1087803 [src:pegsolitaire] pegsolitaire: FTBFS: /usr/bin/ld: src/render.o: undefined ref

Processed: severity of 1087803 is serious

2024-12-03 Thread Debian Bug Tracking System
Processing commands for cont...@bugs.debian.org: > severity 1087803 serious Bug #1087803 [src:pegsolitaire] pegsolitaire: FTBFS: /usr/bin/ld: src/render.o: undefined reference to symbol 'fmin@@GLIBC_2.2.5' Severity set to 'serious' from 'normal' > thanks Stopping processing here. Please contact

Processed (with 1 error): merging 1082692 1087803

2024-12-03 Thread Debian Bug Tracking System
Processing commands for cont...@bugs.debian.org: > merge 1082692 1087803 Bug #1082692 [src:pegsolitaire] pegsolitaire: FTBFS: /usr/bin/ld: src/render.o: undefined reference to symbol 'fmin@@GLIBC_2.2.5' Unable to merge bugs because: severity of #1087803 is 'normal' not 'serious' Failed to merge 1

Bug#1086462: RM: gcc-riscv64-unknown-elf [mips64el] -- ROM; mips64el gcc crashes while building this package

2024-12-03 Thread Johannes Schauer Marin Rodrigues
Hi Keith, Quoting Keith Packard (2024-12-03 21:30:43) > It looks like adding -mxgot to the mips64el build flags (as suggested by > Nicolas Schodet) has resolve the build issue on that arch, letting me reset > this package to Architecture: Any. That means there's no need to remove this > package fr

Bug#1086462: RM: gcc-riscv64-unknown-elf [mips64el] -- ROM; mips64el gcc crashes while building this package

2024-12-03 Thread Keith Packard
Package: gcc-riscv64-unknown-elf Version: 14.2.0-8+16 It looks like adding -mxgot to the mips64el build flags (as suggested by Nicolas Schodet) has resolve the build issue on that arch, letting me reset this package to Architecture: Any. That means there's no need to remove this package from the

Processed: Re: Bug#1085289: perl breaks backuppc autopkgtest: no ping response from localhost

2024-12-03 Thread Debian Bug Tracking System
Processing control commands: > tags -1 + patch Bug #1085289 [src:backuppc] Please set net.ipv4.ping_group_range sysctl in autopkgtests Added tag(s) patch. -- 1085289: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1085289 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems

Bug#1085289: perl breaks backuppc autopkgtest: no ping response from localhost

2024-12-03 Thread Noah Meyerhans
Control: tags -1 + patch The attached patch resolves the issue in (at least) the lxc autopkgtest environment. noah >From da1b5c83e3d730c3f2aa63297bc9e994c0a9b237 Mon Sep 17 00:00:00 2001 From: Noah Meyerhans Date: Tue, 3 Dec 2024 15:18:21 -0500 Subject: [PATCH] autopkgtest: set ping_group_range

Bug#1074863: caribou: FTBFS with gcc-14

2024-12-03 Thread Rebecca N. Palmer
Upstream is archived, and do not appear to be aware of this bug. The actual errors appear to be these 3: caribou-gtk-module.c: In function 'caribou_gtk_module_callback': caribou-gtk-module.c:599:24: error: assignment to 'CaribouKeyboard *' {aka 'struct _CaribouKeyboard *'} from incompatible poi

Processed: gdl: FTBFS with gcc-14

2024-12-03 Thread Debian Bug Tracking System
Processing control commands: > forwarded -1 https://gitlab.gnome.org/GNOME/gdl/-/issues/9 Bug #1074981 [src:gdl] gdl: ftbfs with GCC-14 Set Bug forwarded-to-address to 'https://gitlab.gnome.org/GNOME/gdl/-/issues/9'. -- 1074981: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1074981 Debian Bu

Bug#1074981: gdl: FTBFS with gcc-14

2024-12-03 Thread Rebecca N. Palmer
Control: forwarded -1 https://gitlab.gnome.org/GNOME/gdl/-/issues/9 (actually Gentoo reporting the same bug, but they don't have a fix either) Upstream are considering archiving this project, which suggests but does not prove that removing it from Debian might be reasonable if we can't fix this

Processed: brasero: FTBFS with gcc-14

2024-12-03 Thread Debian Bug Tracking System
Processing control commands: > tags -1 fixed-upstream patch Bug #1074854 [src:brasero] brasero: ftbfs with GCC-14 Added tag(s) fixed-upstream and patch. -- 1074854: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1074854 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems

Bug#1074854: brasero: FTBFS with gcc-14

2024-12-03 Thread Rebecca N. Palmer
Control: tags -1 fixed-upstream patch Upstream fix: https://gitlab.gnome.org/GNOME/brasero/-/merge_requests/30/diffs What looks like the actual error is further back than the above log shows: brasero-metadata.c:668:45: error: passing argument 1 of 'gst_install_plugins_async' from incompatible

Bug#1081027:

2024-12-03 Thread Andreas Hasenack
Sergio[1] got access to the actual container that failed to run this test, and we tried to troubleshoot it a bit. We were pressed for time, and didn't get very far. What we did/tried: - reproduced the problem at will, in every single test run, interactively - verified that the ldap setup was sound

Bug#1075025: marked as done (gnome-font-viewer: ftbfs with GCC-14)

2024-12-03 Thread Debian Bug Tracking System
Your message dated Tue, 3 Dec 2024 19:50:39 + with message-id and subject line Re: Bug#1075025: appears to be fixed Re: gnome-font-viewer FTBFS with gcc-14 has caused the Debian Bug report #1075025, regarding gnome-font-viewer: ftbfs with GCC-14 to be marked as done. This means that you clai

Bug#1088936: marked as done (libpam-tmpdir: moved pam module to aliased path (DEP17))

2024-12-03 Thread Debian Bug Tracking System
Your message dated Tue, 03 Dec 2024 19:19:32 + with message-id and subject line Bug#1088936: fixed in pam-tmpdir 0.11 has caused the Debian Bug report #1088936, regarding libpam-tmpdir: moved pam module to aliased path (DEP17) to be marked as done. This means that you claim that the problem h

Bug#1075025: appears to be fixed Re: gnome-font-viewer FTBFS with gcc-14

2024-12-03 Thread Rebecca N. Palmer
This appears to have been fixed (presumably by upstream): gcc-14 is now the default and this package builds successfully. I suggest closing this bug. https://tests.reproducible-builds.org/debian/rb-pkg/unstable/amd64/gnome-font-viewer.html

Processed: retitle 1088904 to simplesamlphp: CVE-2024-52596 CVE-2024-52806

2024-12-03 Thread Debian Bug Tracking System
Processing commands for cont...@bugs.debian.org: > retitle 1088904 simplesamlphp: CVE-2024-52596 CVE-2024-52806 Bug #1088904 [src:simplesamlphp] simplesamlphp: CVE-2024-52596 Changed Bug title to 'simplesamlphp: CVE-2024-52596 CVE-2024-52806' from 'simplesamlphp: CVE-2024-52596'. > thanks Stoppin

Bug#1088937: marked as done (pam-tmpdir FTBFS on all but amd64: source includes prebuild object files)

2024-12-03 Thread Debian Bug Tracking System
Your message dated Tue, 03 Dec 2024 19:19:32 + with message-id and subject line Bug#1088937: fixed in pam-tmpdir 0.11 has caused the Debian Bug report #1088937, regarding pam-tmpdir FTBFS on all but amd64: source includes prebuild object files to be marked as done. This means that you claim

Processed: closing 1021809

2024-12-03 Thread Debian Bug Tracking System
Processing commands for cont...@bugs.debian.org: > close 1021809 3:1.0.0~rc3-10 Bug #1021809 [php-xmlrpc] php-xmlrpc - uninstallable due to breaks in php-common Marked as fixed in versions php-xmlrpc/3:1.0.0~rc3-10. Bug #1021809 [php-xmlrpc] php-xmlrpc - uninstallable due to breaks in php-common M

Processed: python-escript: FTBFS: dh_install: error: missing files, aborting

2024-12-03 Thread Debian Bug Tracking System
Processing control commands: > severity -1 important Bug #1088894 [src:python-escript] python-escript: FTBFS: dh_install: error: missing files, aborting Severity set to 'important' from 'serious' -- 1088894: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1088894 Debian Bug Tracking System Co

Processed: forcibly merging 1065606 1068733, severity of 1068733 is serious

2024-12-03 Thread Debian Bug Tracking System
Processing commands for cont...@bugs.debian.org: > forcemerge 1065606 1068733 Bug #1065606 [lvm2] lvm2: lvresize --resizefs fails due to missing /usr/libexec/lvresize_fs_helper Bug #1068733 [lvm2] lvm2: resize lv error "/usr/libexec/lvresize_fs_helper: execvp failed" Set Bug forwarded-to-address

Bug#1088866: marked as done (sundials: autopkgtest failures)

2024-12-03 Thread Debian Bug Tracking System
Your message dated Tue, 03 Dec 2024 18:23:12 + with message-id and subject line Bug#1088866: fixed in sundials 7.1.1+dfsg1-6 has caused the Debian Bug report #1088866, regarding sundials: autopkgtest failures to be marked as done. This means that you claim that the problem has been dealt with

Bug#1088971: sbuild's autopkg tests fail

2024-12-03 Thread Johannes Schauer Marin Rodrigues
Hi, Quoting Matthias Klose (2024-12-03 18:33:14) > > This is because cross-building in unstable from amd64 (build) to arm64 > > (host) is broken right now. The autopkgtest will pass once that is fixed > > in the relevant packages. > > > > Feel free to reassign this bug to the actual culprit,

Processed: Re: Bug#1085289: Close this bug ?

2024-12-03 Thread Debian Bug Tracking System
Processing control commands: > severity -1 serious Bug #1085289 [src:backuppc] Please set net.ipv4.ping_group_range sysctl in autopkgtests Severity set to 'serious' from 'important' -- 1085289: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1085289 Debian Bug Tracking System Contact ow...@bu

Bug#1086011: marked as done (fence-agents: Please set net.ipv4.ping_group_range sysctl in autopkgtests)

2024-12-03 Thread Debian Bug Tracking System
Your message dated Tue, 03 Dec 2024 18:00:15 + with message-id and subject line Bug#1086011: fixed in fence-agents 4.16.0-1 has caused the Debian Bug report #1086011, regarding fence-agents: Please set net.ipv4.ping_group_range sysctl in autopkgtests to be marked as done. This means that you

Bug#1075386: marked as done (php-zmq: ftbfs with GCC-14)

2024-12-03 Thread Debian Bug Tracking System
Your message dated Tue, 03 Dec 2024 18:00:20 + with message-id and subject line Bug#1075386: fixed in php-zmq 1.1.3-29 has caused the Debian Bug report #1075386, regarding php-zmq: ftbfs with GCC-14 to be marked as done. This means that you claim that the problem has been dealt with. If this

Bug#1088971: sbuild's autopkg tests fail

2024-12-03 Thread Matthias Klose
On 03.12.24 17:30, Johannes Schauer Marin Rodrigues wrote: > Hi, > > Quoting Matthias Klose (2024-12-03 17:00:05) >> sbuild's autopkg tests fail: > > yes, this is this: > > https://lists.debian.org/debian-release/2024/10/msg00346.html > > This is because cross-building in unstable from amd64 (buil

Bug#1088974: chromium: 131.0.6778.85-1~deb12u1 in bookworm-security fails to start on arm64: stack smashing detected

2024-12-03 Thread Andres Salomon
Currently waiting on #1088699 to fix this. On 12/3/24 12:06, Emanuele Rocca wrote: Package: chromium Version: 131.0.6778.85-1~deb12u1 Severity: serious User: debian-...@lists.debian.org Usertags: arm64 On arm64 systems, the version of chromium currently in bookworm-security (131.0.6778.85-1~deb

Bug#1088974: chromium: 131.0.6778.85-1~deb12u1 in bookworm-security fails to start on arm64: stack smashing detected

2024-12-03 Thread Emanuele Rocca
Package: chromium Version: 131.0.6778.85-1~deb12u1 Severity: serious User: debian-...@lists.debian.org Usertags: arm64 On arm64 systems, the version of chromium currently in bookworm-security (131.0.6778.85-1~deb12u1) fails to start with several "stack smashing detected" errors. The bookworm versi

Bug#1088971: sbuild's autopkg tests fail

2024-12-03 Thread Johannes Schauer Marin Rodrigues
Hi, Quoting Matthias Klose (2024-12-03 17:00:05) > sbuild's autopkg tests fail: yes, this is this: https://lists.debian.org/debian-release/2024/10/msg00346.html This is because cross-building in unstable from amd64 (build) to arm64 (host) is broken right now. The autopkgtest will pass once that

Bug#1088972: flowblade: Consider dropping gmic from Depends

2024-12-03 Thread Jeremy Bícha
Source: flowblade Version: 2.16.3-2 Severity: serious X-Debbugs-CC: t...@debian.org flowblade is currently not in Debian Testing because it has Depends: gmic. gmic is not in Testing because of 2 RC issues. flowblade can run without gmic being installed so please consider demoting gmic to Suggests

Bug#1088894: python-escript: FTBFS: dh_install: error: missing files, aborting

2024-12-03 Thread Graham Inggs
Control: severity -1 important This issue is not seen on the builds [1]. nor on reproducible builds [2]. As this bug currently blocks the openmpi transition, I am downgrading the severity. Please feel free to raise the severity again after openmpi has migrated, if the problem persists. [1] http

Bug#1075195: marked as done (liboggplay: ftbfs with GCC-14)

2024-12-03 Thread Debian Bug Tracking System
Your message dated Tue, 03 Dec 2024 16:05:37 + with message-id and subject line Bug#1075195: fixed in liboggplay 0.2.1~git20091227-5.1 has caused the Debian Bug report #1075195, regarding liboggplay: ftbfs with GCC-14 to be marked as done. This means that you claim that the problem has been d

Bug#1088971: sbuild's autopkg tests fail

2024-12-03 Thread Matthias Klose
Package: src:sbuild Version: 0.87.1 Severity: serious Tags: sid trixie sbuild's autopkg tests fail: [...] 284s Install main build dependencies (apt-based resolver) 284s 284s 284s Installing build dependencies 285s Reading package lists... 285s

Bug#1087645: marked as done (FTBFS with Python 3.13: error: implicit declaration of function ‘_PyList_Extend’)

2024-12-03 Thread Debian Bug Tracking System
Your message dated Tue, 03 Dec 2024 15:53:55 + with message-id and subject line Bug#1087645: fixed in python-pyspike 0.8.0+dfsg-3 has caused the Debian Bug report #1087645, regarding FTBFS with Python 3.13: error: implicit declaration of function ‘_PyList_Extend’ to be marked as done. This m

Bug#1088970: python-rioxarray: FTBFS with rasterio 1.4.3 (test failures)

2024-12-03 Thread Bas Couwenberg
Source: python-rioxarray Version: 0.18.1-1 Severity: serious Tags: ftbfs upstream patch Justification: makes the package in question unusable or mostly so Dear Maintainer, Your package FTBFS with rasterio 1.4.3: === FAILURES ===

Bug#1074166: marked as done (erlang-dialyzer has an undeclared file conflict on /usr/bin/typer)

2024-12-03 Thread Debian Bug Tracking System
Your message dated Tue, 03 Dec 2024 14:52:44 + with message-id and subject line Bug#1074166: fixed in erlang 1:27.1.2+dfsg-1 has caused the Debian Bug report #1074166, regarding erlang-dialyzer has an undeclared file conflict on /usr/bin/typer to be marked as done. This means that you claim t

Bug#1074700: marked as done (dfwinreg: FTBFS: make: *** [debian/rules:10: build] Error 2)

2024-12-03 Thread Debian Bug Tracking System
Your message dated Tue, 03 Dec 2024 14:50:34 + with message-id and subject line Bug#1074700: fixed in dfwinreg 20240316-1 has caused the Debian Bug report #1074700, regarding dfwinreg: FTBFS: make: *** [debian/rules:10: build] Error 2 to be marked as done. This means that you claim that the p

Bug#1087616: confirm linux-image-6.11.7-amd64 boot failure

2024-12-03 Thread Chris Nospam
ian_br...@mail.ru wrote at Mon, 2 Dec 2024 22:56:25 -0800 > However, having now installed systemd v257~rc3-1, the problem seems to > have gone away, without altering the boot parameters. This is the case > at least with kernel linux-image-6.11.10-amd64. I cannot confirm that. The hang in with syst

Bug#1088881: marked as done (blackbox-terminal: No support for -e flag)

2024-12-03 Thread Debian Bug Tracking System
Your message dated Tue, 03 Dec 2024 14:50:22 + with message-id and subject line Bug#101: fixed in blackbox-terminal 0.14.0-5 has caused the Debian Bug report #101, regarding blackbox-terminal: No support for -e flag to be marked as done. This means that you claim that the problem has

Processed: Re: gmic: FTBFS: File 'CImg.h' has been already included (should have been done first in file 'gmic.h')

2024-12-03 Thread Debian Bug Tracking System
Processing commands for cont...@bugs.debian.org: > tags 1088066 +ftbfs Bug #1088066 [src:gmic] gmic: FTBFS: File 'CImg.h' has been already included (should have been done first in file 'gmic.h') Added tag(s) ftbfs. > End of message, stopping processing here. Please contact me if you need assista

Processed: found 1085192 in 0.17.4-1, tagging 1085192, tagging 1088919

2024-12-03 Thread Debian Bug Tracking System
Processing commands for cont...@bugs.debian.org: > found 1085192 0.17.4-1 Bug #1085192 [wlroots] wlroots 0.18 transition There is no source info for the package 'wlroots' at version '0.17.4-1' with architecture '' Unable to make a source version for version '0.17.4-1' Marked as found in versions

Bug#1088919: libmpich-dev no longer provides mpi-c.pc

2024-12-03 Thread Andreas Beckmann
On 12/2/24 23:07, Adrian Bunk wrote: Package mpi-c was not found in the pkg-config search path. This was changed in: https://salsa.debian.org/science-team/mpich/-/commit/2f0d0190d12923c482df5ba7eacd8da721f8d0a3 mpich had stopped providing variants of mpi-c.pc etc. so I removed the dangling

Bug#1088958: libcomedi0t64: empty, aliased directory /lib/udev/rules.d

2024-12-03 Thread Helmut Grohne
Package: libcomedi0t64 Version: 0.11.0+5-1.2 Severity: serious Justification: installing into aliased locations is release-critical Tags: patch User: helm...@debian.org Usertags: dep17m2 Hi, Michael uploaded my earlier patch #1058848 submission as NMU 0.11.0+5-1.2. Unfortunately, the patch given

Processed: python3-domain2idna has an undeclared file conflict on /usr/bin/domain2idna

2024-12-03 Thread Debian Bug Tracking System
Processing control commands: > affects -1 + domain2idna Bug #1088955 [python3-domain2idna] python3-domain2idna has an undeclared file conflict on /usr/bin/domain2idna Added indication that 1088955 affects domain2idna -- 1088955: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1088955 Debian B

Processed: promtool has an undeclared file conflict on /usr/bin/promtool

2024-12-03 Thread Debian Bug Tracking System
Processing control commands: > affects -1 + prometheus Bug #1088956 [promtool] promtool has an undeclared file conflict on /usr/bin/promtool Added indication that 1088956 affects prometheus -- 1088956: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1088956 Debian Bug Tracking System Contact

Bug#1088955: python3-domain2idna has an undeclared file conflict on /usr/bin/domain2idna

2024-12-03 Thread Helmut Grohne
Package: python3-domain2idna Version: 1.12.2-1 Severity: serious User: debian...@lists.debian.org Usertags: fileconflict Control: affects -1 + domain2idna python3-domain2idna has an undeclared file conflict. This may result in an unpack error from dpkg. The file /usr/bin/domain2idna is contained

Bug#1088956: promtool has an undeclared file conflict on /usr/bin/promtool

2024-12-03 Thread Helmut Grohne
Package: promtool Version: 2.45.6+ds-8 Severity: serious User: debian...@lists.debian.org Usertags: fileconflict Control: affects -1 + prometheus promtool has an undeclared file conflict. This may result in an unpack error from dpkg. The file /usr/bin/promtool is contained in the packages * prom

Bug#1088724: python-maturin: FTBFS: error: failed to select a version for the requirement `pep440_rs = "^0.6.0"`

2024-12-03 Thread Colin Watson
On Fri, Nov 29, 2024 at 11:11:10PM +0100, Santiago Vila wrote: > cargo generate-lockfile --offline > error: failed to select a version for the requirement `pep440_rs = "^0.6.0"` > candidate versions found which didn't match: 0.7.2 I beat my head against this for a while as there are several simila

Processed: severity of 1088871 is wishlist

2024-12-03 Thread Debian Bug Tracking System
Processing commands for cont...@bugs.debian.org: > severity 1088871 wishlist Bug #1088871 [dracut] fixed lintian error and add support for system with ostree Severity set to 'wishlist' from 'critical' > thanks Stopping processing here. Please contact me if you need assistance. -- 1088871: https:

Bug#1088759: marked as done (openstack-trove: autopkgtest failure with Python 3.13)

2024-12-03 Thread Debian Bug Tracking System
Your message dated Tue, 03 Dec 2024 11:20:25 + with message-id and subject line Bug#1088759: fixed in openstack-trove 1:22.0.0-2 has caused the Debian Bug report #1088759, regarding openstack-trove: autopkgtest failure with Python 3.13 to be marked as done. This means that you claim that the

Bug#1088246: marked as done (djangorestframework: autopkgtest failure with Python 3.13)

2024-12-03 Thread Debian Bug Tracking System
Your message dated Tue, 03 Dec 2024 11:19:20 + with message-id and subject line Bug#1088246: fixed in djangorestframework 3.15.2-2 has caused the Debian Bug report #1088246, regarding djangorestframework: autopkgtest failure with Python 3.13 to be marked as done. This means that you claim tha

Bug#1088246: marked as pending in djangorestframework

2024-12-03 Thread Colin Watson
Control: tag -1 pending Hello, Bug #1088246 in djangorestframework 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/djangorestframework/-/co

Processed: Bug#1088246 marked as pending in djangorestframework

2024-12-03 Thread Debian Bug Tracking System
Processing control commands: > tag -1 pending Bug #1088246 [src:djangorestframework] djangorestframework: autopkgtest failure with Python 3.13 Added tag(s) pending. -- 1088246: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1088246 Debian Bug Tracking System Contact ow...@bugs.debian.org wit

Bug#1087059: calamares has an undeclared file conflict

2024-12-03 Thread Jonathan Carter
On 2024/12/03 11:54, Helmut Grohne wrote: Please do not repurpose this bug for the necessary clamares-extensions upload, because doing so confuses dumat and will make it file a duplicate. If you want to track the issue in calamares-extensions separately, that's fine. Just make a new bug. You may

Processed: Re: Bug#1087059: calamares has an undeclared file conflict

2024-12-03 Thread Debian Bug Tracking System
Processing control commands: > reassign -1 calamares 3.3.11-1 Bug #1087059 [calamares-extensions] calamares has an undeclared file conflict Bug reassigned from package 'calamares-extensions' to 'calamares'. No longer marked as found in versions calamares-extensions/3.3.1-1. Ignoring request to alt

Bug#1087059: calamares has an undeclared file conflict

2024-12-03 Thread Helmut Grohne
Control: reassign -1 calamares 3.3.11-1 Hi Jonathan and Aaron, On Wed, Nov 20, 2024 at 10:48:47PM -0600, Aaron Rainbolt wrote: > This is because of a module that moved from calamares-extensions to > calamares. calamares-extensions 3.3.11 solves the issue, however a > tarball of it hasn't been pub

Bug#1088936: libpam-tmpdir: moved pam module to aliased path (DEP17)

2024-12-03 Thread Helmut Grohne
Package: libpam-tmpdir Version: 0.10 Severity: serious Justification: moving files from /usr to / is now forbidden User: helm...@debian.org Usertags: dep17m2 Hi Tollef, your most recet pam-tmpdir upload fails to consider the 0.09+nmu1 upload done by Chris Hofstaedler. That upload moved the pam mo

Bug#1088937: pam-tmpdir FTBFS on all but amd64: source includes prebuild object files

2024-12-03 Thread Helmut Grohne
Source: pam-tmpdir Version: 0.10 Severity: serious Tags: ftbfs pam-tmpdir fails to build from source on all but any-amd64, because its source package includes prebuilt ELF objects that happen to be reused during build. The linkers for other architectures are not happy with those objects. Cleaning

Bug#1088881: mutt: /usr/lib/mutt/mailto-mutt should not assume -e

2024-12-03 Thread Matthias Geiger
On Mon, 02 Dec 2024 15:33:49 +0100 Matthias Geiger wrote: Control: reassign -1 blackbox-terminal Control: retitle -1 blackbox-terminal: No support for -e flag Control: severity -1 serious Control: tags -1 upstream Control: forwarded -1 https://gitlab.gnome.org/raggesilver/blackbox/-/issues/388

Processed: closing 1077388

2024-12-03 Thread Debian Bug Tracking System
Processing commands for cont...@bugs.debian.org: > close 1077388 2.2.4-1 Bug #1077388 [src:php-yaml] php-yaml: FTBFS: parse.c:534:39: error: passing argument 1 of 'zval_ptr_dtor' from incompatible pointer type [-Wincompatible-pointer-types] Marked as fixed in versions php-yaml/2.2.4-1. Bug #1077

Bug#1086387: marked as done (todoman: FTBFS: AssertionError: assert 'second' in '[ ] 2 2017-03-04 first @default')

2024-12-03 Thread Debian Bug Tracking System
Your message dated Tue, 03 Dec 2024 08:43:26 + with message-id and subject line Bug#1086387: fixed in todoman 4.5.0-1 has caused the Debian Bug report #1086387, regarding todoman: FTBFS: AssertionError: assert 'second' in '[ ] 2 2017-03-04 first @default' to be marked as done. This means tha

Bug#1088827: marked as done (FTBFS with Python 3.13: ModuleNotFoundError: No module named 'audioop')

2024-12-03 Thread Debian Bug Tracking System
Your message dated Tue, 03 Dec 2024 09:05:14 + with message-id and subject line Bug#1088827: fixed in python-voip-utils 0.2.1-1 has caused the Debian Bug report #1088827, regarding FTBFS with Python 3.13: ModuleNotFoundError: No module named 'audioop' to be marked as done. This means that you

Processed: severity

2024-12-03 Thread Debian Bug Tracking System
Processing commands for cont...@bugs.debian.org: > severity 1084676 serious Bug #1084676 [src:pyro4] pyro4: removal of Python standard libraries in Python 3.13 Severity set to 'serious' from 'important' > End of message, stopping processing here. Please contact me if you need assistance. -- 108

Processed: Bug#1086387 marked as pending in todoman

2024-12-03 Thread Debian Bug Tracking System
Processing control commands: > tag -1 pending Bug #1086387 [src:todoman] todoman: FTBFS: AssertionError: assert 'second' in '[ ] 2 2017-03-04 first @default' Added tag(s) pending. -- 1086387: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1086387 Debian Bug Tracking System Contact ow...@bugs

Bug#1086387: marked as pending in todoman

2024-12-03 Thread Félix Sipma
Control: tag -1 pending Hello, Bug #1086387 in todoman 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/todoman/-/commit/dbf2320e7cc5be5ecba