Bug#1103226: marked as done (chromium: FTBFS: gen/third_party/blink/renderer/platform/color_data.cc:138:7: error: fallthrough annotation does not directly precede switch label)

2025-04-15 Thread Debian Bug Tracking System
Your message dated Wed, 16 Apr 2025 06:36:23 + with message-id and subject line Bug#1103226: fixed in chromium 135.0.7049.95-1 has caused the Debian Bug report #1103226, regarding chromium: FTBFS: gen/third_party/blink/renderer/platform/color_data.cc:138:7: error: fallthrough annotation does

Bug#1102693: src:frr: fails to migrate to testing for too long: FTBFS on s390x

2025-04-15 Thread Pranav P
Hi, Looks like https://github.com/FRRouting/frr/pull/18662/commits/da8fce3830baa2fd4d70050a3f7677d6e8bd5ad4 by Mark is fixing the issue. But it's still waiting to be merged. Thanks, Pranav

Bug#1103217: [PATCH] Fix for FTBFS with r-base-dev=4.5.0-1

2025-04-15 Thread liwenjun
Package: src:r-bioc-affxparser Version: 1.78.0-2 Severity: serious Tags: ftbfs trixie sid Dear maintainer: Hi, I'm summitting a patch for fixing this FTBFS problem while building with r-base-dev=4.5.0-1 on Debian sid,trixie. My patch Fix-FTBFS.patch replace Calloc() and Free() with R_Calloc()

Bug#1102322: android-udev-rules ineffectively Replaces android-sdk-platform-tools-common due to the /usr-move transition (DEP17 P1)

2025-04-15 Thread Mina
On Mon, 14 Apr 2025 22:55:49 -0700 Roger Shimizu wrote: > control: fixed -1 20250314+ds-4 > > is this the same as #1102321? > looks very similar. > -Roger > > i think you ment 0~20250314+ds-4 i could be wrong that's why i didn't fix it

Processed: reassign 1103210 to python-levenshtein, affects 1103210, closing 1103210

2025-04-15 Thread Debian Bug Tracking System
Processing commands for cont...@bugs.debian.org: > reassign 1103210 python-levenshtein 0.27.1-1 Bug #1103210 [src:textdistance] textdistance: FTBFS: RuntimeError: cannot import Levenshtein.distance Bug reassigned from package 'src:textdistance' to 'python-levenshtein'. No longer marked as found i

Bug#1103210: reassign 1103210 to python-levenshtein, affects 1103210, closing 1103210

2025-04-15 Thread Julian Gilbey
reassign 1103210 python-levenshtein 0.27.1-1 affects 1103210 textdistance close 1103210 0.27.1-2 thanks -- python-levenshtein 0.27.1-1 did not include the Levenshtein module; this is fixed in 0.27.1-2.

Bug#1102390: passenger: missing licenses

2025-04-15 Thread Matheus Polkorny
From: Matheus Polkorny To: 1102...@bugs.debian.org Subject: Re: passenger: missing licenses user debian-rele...@lists.debian.org usertags 1102390 + patch + bsp-2025-04-brazil thanks Hi, I have updated the d/copyright file according to the latest upstream version available on Debian. More deta

Bug#1102379: marked as done (hyperkitty: FTBFS: FAIL: test_header (hyperkitty.tests.test_templatetags.TestDecorate.test_header))

2025-04-15 Thread Debian Bug Tracking System
Your message dated Wed, 16 Apr 2025 04:19:30 + with message-id and subject line Bug#1102379: fixed in hyperkitty 1.3.12-3 has caused the Debian Bug report #1102379, regarding hyperkitty: FTBFS: FAIL: test_header (hyperkitty.tests.test_templatetags.TestDecorate.test_header) to be marked as don

Bug#1078617: marked as done (golang-github-fsouza-go-dockerclient: will FTBFS during trixie support period)

2025-04-15 Thread Debian Bug Tracking System
Your message dated Wed, 16 Apr 2025 03:58:11 + with message-id and subject line Bug#1078617: fixed in golang-github-fsouza-go-dockerclient 1.12.1-1 has caused the Debian Bug report #1078617, regarding golang-github-fsouza-go-dockerclient: will FTBFS during trixie support period to be marked

Bug#1103250: yasm: FTBFS on amd64, arm64, armel, armhf, i386, ppc64el, ppc64, powerpc, riscv64

2025-04-15 Thread Jing Luo
On 2025-04-16 05:50, Peter Green wrote: On 15/04/2025 16:07, Jing Luo wrote: X-Debbugs-Cc: debian-am...@lists.debian.org, debian-...@lists.debian.org, debian-powe...@lists.debian.org, debian-ri...@lists.debian.org I understand CC'ing the porters when you have an issue that is specific to the

Bug#1103282: hwloc-contrib: FTBFS hwloc_type_sscanf: hwloc_type_sscanf.c:40: _check: Assertion `depth == (int) obj->depth' failed.

2025-04-15 Thread Andreas Beckmann
Source: hwloc-contrib Version: 2.12.0-1 Severity: serious Tags: ftbfs Justification: fails to build from source Hi, while rebuilding all packages build-depending on nvidia-cuda-toolkit, hwloc-contrib did FTBFS with a failing test: FAIL: hwloc_type_sscanf ===

Bug#1103146: marked as done (jsonpickle: FTBFS in testing/i386: dh_auto_test: error: pybuild --test --test-pytest -i python{version} -p 3.13 returned exit code 13)

2025-04-15 Thread Debian Bug Tracking System
Your message dated Wed, 16 Apr 2025 01:49:05 + with message-id and subject line Bug#1103146: fixed in jsonpickle 4.0.2+dfsg-2 has caused the Debian Bug report #1103146, regarding jsonpickle: FTBFS in testing/i386: dh_auto_test: error: pybuild --test --test-pytest -i python{version} -p 3.13 re

Bug#1103146: marked as pending in jsonpickle

2025-04-15 Thread Colin Watson
Control: tag -1 pending Hello, Bug #1103146 in jsonpickle 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/jsonpickle/-/commit/6587920555c2b

Processed: Bug#1103146 marked as pending in jsonpickle

2025-04-15 Thread Debian Bug Tracking System
Processing control commands: > tag -1 pending Bug #1103146 [src:jsonpickle] jsonpickle: FTBFS in testing/i386: dh_auto_test: error: pybuild --test --test-pytest -i python{version} -p 3.13 returned exit code 13 Added tag(s) pending. -- 1103146: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=

Processed: bug 1103146 is forwarded to https://github.com/jsonpickle/jsonpickle/pull/560

2025-04-15 Thread Debian Bug Tracking System
Processing commands for cont...@bugs.debian.org: > forwarded 1103146 https://github.com/jsonpickle/jsonpickle/pull/560 Bug #1103146 [src:jsonpickle] jsonpickle: FTBFS in testing/i386: dh_auto_test: error: pybuild --test --test-pytest -i python{version} -p 3.13 returned exit code 13 Set Bug forwa

Bug#1101500: marked as done (upx-ucl: CVE-2025-2849)

2025-04-15 Thread Debian Bug Tracking System
Your message dated Wed, 16 Apr 2025 01:04:26 + with message-id and subject line Bug#1101500: fixed in upx-ucl 4.2.4-1.1 has caused the Debian Bug report #1101500, regarding upx-ucl: CVE-2025-2849 to be marked as done. This means that you claim that the problem has been dealt with. If this is

Bug#1099130: Are the Firefox Terms of Use suitable for Debian?

2025-04-15 Thread Joey Hess
Jeremy Bícha wrote: > https://www.mozilla.org/en-US/privacy/firefox/ which does include the > new Terms of Use. I don't see a link on that page to the new ToU. (It does link to some ToU's of chatbots.) > It is also linked to in Help > About Firefox. Indeed it is! While this is a ways from "mak

Bug#1101591: marked as done (r-cran-waveslim: FTBFS: build-dependency not installable: r-cran-multitaper)

2025-04-15 Thread Debian Bug Tracking System
Your message dated Wed, 16 Apr 2025 09:55:08 +0900 with message-id and subject line r-cran-multitaper is now in Debian. has caused the Debian Bug report #1101591, regarding r-cran-waveslim: FTBFS: build-dependency not installable: r-cran-multitaper to be marked as done. This means that you claim

Processed: tagging 1102516

2025-04-15 Thread Debian Bug Tracking System
Processing commands for cont...@bugs.debian.org: > tags 1102516 + ftbfs Bug #1102516 [src:yubikey-manager] yubikey-manager_5.6.1-1_all-buildd.changes REJECTED Added tag(s) ftbfs. > thanks Stopping processing here. Please contact me if you need assistance. -- 1102516: https://bugs.debian.org/cgi

Bug#1099130: Are the Firefox Terms of Use suitable for Debian?

2025-04-15 Thread Jeremy Bícha
On Tue, Apr 15, 2025 at 6:59 PM Mike Hommey wrote: > Actually, we don't, because ESR 128 doesn't have the code that shows the > Terms of Use. I thought that at first. Opening Firefox ESR 128.9.0esr-2 in Debian Testing opens two tabs, one is about:welcome and can be ignored here. The other, becaus

Processed: Re: Bug#1099130: Are the Firefox Terms of Use suitable for Debian?

2025-04-15 Thread Debian Bug Tracking System
Processing control commands: > reassign -1 firefox Bug #1099130 [firefox-esr] Are the Firefox Terms of Use suitable for Debian? Bug reassigned from package 'firefox-esr' to 'firefox'. No longer marked as found in versions firefox-esr/128.7.0esr-1. Ignoring request to alter fixed versions of bug #1

Bug#1099130: Are the Firefox Terms of Use suitable for Debian?

2025-04-15 Thread Mike Hommey
Control: reassign -1 firefox On Tue, Apr 15, 2025 at 05:37:24PM -0400, Jeremy Bícha wrote: > Control: retitle -1 Are the Firefox Terms of Use suitable for Debian? > > > As described in Mozilla’s communication, due to changes in laws in > > various places where Mozilla operates (particularly Calif

Processed: Re: Bug#1103152: Starts 2nd getty on hvc0, making console login (almost) impossible

2025-04-15 Thread Debian Bug Tracking System
Processing control commands: > tags -1 moreinfo Bug #1103152 [getty-run] Starts 2nd getty on hvc0, making console login (almost) impossible Ignoring request to alter tags of bug #1103152 to the same tags previously set -- 1103152: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1103152 Debian

Bug#1103152: Starts 2nd getty on hvc0, making console login (almost) impossible

2025-04-15 Thread Lorenzo
Control: tags -1 moreinfo Hi Andras, Hi Andrew, On Mon, 14 Apr 2025 16:28:36 +0200 Andras Korn wrote: > Package: getty-run > Version: 2.2.0-2 > Severity: critical > Justification: makes console logins all but impossible, thus arguably > breaking the entire system > > Hi, > > I have a VPS that

Processed: Re: Bug#1103152: Starts 2nd getty on hvc0, making console login (almost) impossible

2025-04-15 Thread Debian Bug Tracking System
Processing control commands: > tags -1 moreinfo Bug #1103152 [getty-run] Starts 2nd getty on hvc0, making console login (almost) impossible Added tag(s) moreinfo. -- 1103152: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1103152 Debian Bug Tracking System Contact ow...@bugs.debian.org with

Bug#1103044: marked as done (mat2: unsatisfiable dependency on python2)

2025-04-15 Thread Debian Bug Tracking System
Your message dated Tue, 15 Apr 2025 22:11:05 + with message-id and subject line Bug#1103044: fixed in mat2 0.13.5-1.2 has caused the Debian Bug report #1103044, regarding mat2: unsatisfiable dependency on python2 to be marked as done. This means that you claim that the problem has been dealt

Processed: fixed 1103256 in 0.20.0-5

2025-04-15 Thread Debian Bug Tracking System
Processing commands for cont...@bugs.debian.org: > fixed 1103256 0.20.0-5 Bug #1103256 {Done: Jérémy Lal } [golang-github-smallstep-certificates] golang-github-smallstep-crypto: FTBFS during tests when built with nebula >= 1.9.3 There is no source info for the package 'golang-github-smallstep-ce

Processed: reassign 1103256 to golang-github-smallstep-certificates

2025-04-15 Thread Debian Bug Tracking System
Processing commands for cont...@bugs.debian.org: > reassign 1103256 golang-github-smallstep-certificates Bug #1103256 {Done: Jérémy Lal } [src:golang-github-smallstep-crypto] golang-github-smallstep-crypto: FTBFS during tests when built with nebula >= 1.9.3 Bug reassigned from package 'src:golan

Processed: Re: Bug#1099130: Are the Firefox Terms of Use suitable for Debian?

2025-04-15 Thread Debian Bug Tracking System
Processing control commands: > retitle -1 Are the Firefox Terms of Use suitable for Debian? Bug #1099130 [firefox-esr] firefox-esr: Please package a fork that respects users privacy Changed Bug title to 'Are the Firefox Terms of Use suitable for Debian?' from 'firefox-esr: Please package a fork

Bug#1099130: Are the Firefox Terms of Use suitable for Debian?

2025-04-15 Thread Jeremy Bícha
Control: retitle -1 Are the Firefox Terms of Use suitable for Debian? > As described in Mozilla’s communication, due to changes in laws in > various places where Mozilla operates (particularly California and the > EU), having a clear Terms of Use in the product became a necessity (all > other majo

Bug#1103208: marked as done (supysonic: FTBFS: dh_install: error: missing files, aborting)

2025-04-15 Thread Debian Bug Tracking System
Your message dated Tue, 15 Apr 2025 21:07:12 + with message-id and subject line Bug#1103208: fixed in supysonic 0.7.9+ds-2 has caused the Debian Bug report #1103208, regarding supysonic: FTBFS: dh_install: error: missing files, aborting to be marked as done. This means that you claim that the

Bug#1103011: marked as done (skanpage: FTBFS in testing/arm64: make: *** [debian/rules:6: binary] Error 2)

2025-04-15 Thread Debian Bug Tracking System
Your message dated Tue, 15 Apr 2025 21:06:24 + with message-id and subject line Bug#1100320: fixed in qt6-webengine 6.8.2+dfsg-4 has caused the Debian Bug report #1100320, regarding skanpage: FTBFS in testing/arm64: make: *** [debian/rules:6: binary] Error 2 to be marked as done. This means

Bug#1100320: marked as done (qt6-pdf-dev: missing Qt6Pdf files (which are in qt6-webengine-dev instead) break cmake-based builds w/o qt6-webengine-dev)

2025-04-15 Thread Debian Bug Tracking System
Your message dated Tue, 15 Apr 2025 21:06:24 + with message-id and subject line Bug#1100320: fixed in qt6-webengine 6.8.2+dfsg-4 has caused the Debian Bug report #1100320, regarding qt6-pdf-dev: missing Qt6Pdf files (which are in qt6-webengine-dev instead) break cmake-based builds w/o qt6-web

Processed: Re: Bug#1101258: uvloop: FTBFS: AssertionError: None != 'mytask!'

2025-04-15 Thread Debian Bug Tracking System
Processing control commands: > tags 1101258 patch Bug #1101258 [src:uvloop] uvloop: FTBFS: AssertionError: None != 'mytask!' Added tag(s) patch. -- 1101258: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1101258 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems

Bug#1103250: yasm: FTBFS on amd64, arm64, armel, armhf, i386, ppc64el, ppc64, powerpc, riscv64

2025-04-15 Thread Peter Green
On 15/04/2025 16:07, Jing Luo wrote: X-Debbugs-Cc: debian-am...@lists.debian.org, debian-...@lists.debian.org, debian-powe...@lists.debian.org, debian-ri...@lists.debian.org I understand CC'ing the porters when you have an issue that is specific to the port, but if it's failing on every damn

Bug#1101258: uvloop: FTBFS: AssertionError: None != 'mytask!'

2025-04-15 Thread textshell
Control: tags 1101258 patch This is actually caused by a test that makes assumsations about the builtin python asyncio event loops that no longer hold. python upstream commit https://github.com/python/cpython/commit/38a99568763604ccec5d5027f0658100ad76876f semi-silently moved the responsibity fo

Bug#1102970: marked as done (guile-git: FTBFS in testing: dh_auto_test: error: cd debian/build/guile-3.0 && make -j1 check "TESTSUITEFLAGS=-j1 --verbose" VERBOSE=1 returned exit code 2)

2025-04-15 Thread Debian Bug Tracking System
Your message dated Tue, 15 Apr 2025 20:42:33 + with message-id and subject line Bug#1102970: fixed in guile-git 0.9.0-2 has caused the Debian Bug report #1102970, regarding guile-git: FTBFS in testing: dh_auto_test: error: cd debian/build/guile-3.0 && make -j1 check "TESTSUITEFLAGS=-j1 --verb

Processed: Re: rust-sudo-rs: Autopkgtests fail on 32-bit architectures

2025-04-15 Thread Debian Bug Tracking System
Processing commands for cont...@bugs.debian.org: > forwarded 1103275 > https://github.com/trifectatechfoundation/sudo-rs/issues/1074 Bug #1103275 [src:rust-sudo-rs] rust-sudo-rs: Autopkgtests fail on 32-bit architectures Set Bug forwarded-to-address to 'https://github.com/trifectatechfoundation

Bug#1103275: rust-sudo-rs: Autopkgtests fail on 32-bit architectures

2025-04-15 Thread Jeremy Bícha
Source: rust-sudo-rs Version: 0.2.5-3 Severity: serious Tags: upstream The autopkgtests for rust-sudo-rs are failing on 32-bit architectures. This is preventing the latest update from migrating to Testing. I'm filing an upstream bug for this. Autopkgtest log excerpt == error[

Processed: Bug#1103208 marked as pending in supysonic

2025-04-15 Thread Debian Bug Tracking System
Processing control commands: > tag -1 pending Bug #1103208 [src:supysonic] supysonic: FTBFS: dh_install: error: missing files, aborting Added tag(s) pending. -- 1103208: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1103208 Debian Bug Tracking System Contact ow...@bugs.debian.org with probl

Bug#1103208: marked as pending in supysonic

2025-04-15 Thread Colin Watson
Control: tag -1 pending Hello, Bug #1103208 in supysonic 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/supysonic/-/commit/75d143b9dc5f3fe

Bug#1103211: Upstream fix for ykman incomplete - tests failing.

2025-04-15 Thread Ludovic Rousseau
Le 15/04/2025 à 20:24, Patrick Winnertz a écrit : Hey, There is a partial fix upstream available however they lock the version to <2.2.2 which won't help us within debian right now. So - sadly no fix available upstream yet. For yubikey-manager ignore the change for pyproject.toml that locks p

Bug#980148: mesa-vulkan-drivers: file content conflict in Multi-Arch:same package

2025-04-15 Thread Helmut Grohne
On Tue, Apr 15, 2025 at 10:41:22AM +0200, Michel Dänzer wrote: > Given that different variants of libvulkan_*.so are located in separate > search paths, is there any scenario other than a system misconfiguration > which would result in an attempt to load the wrong one? I fear the answer to this

Bug#980148: mesa-vulkan-drivers: file content conflict in Multi-Arch:same package

2025-04-15 Thread Helmut Grohne
Hi Simon, On Tue, Apr 15, 2025 at 01:47:54PM +0100, Simon McVittie wrote: > I think a regression for amd64/i386 co-installation would have a > considerably larger practical negative impact on Debian users than > ABI conflicts between less-commonly-used architecture pairs like > armel/armhf, and a

Bug#1103194: marked as done (pcs: FTBFS: rm: cannot remove '/<>/debian/tmp/usr/lib/python3/dist-packages/*.dist-info/COPYING': No such file or directory)

2025-04-15 Thread Debian Bug Tracking System
Your message dated Tue, 15 Apr 2025 19:49:43 + with message-id and subject line Bug#1103194: fixed in pcs 0.12.0-2 has caused the Debian Bug report #1103194, regarding pcs: FTBFS: rm: cannot remove '/<>/debian/tmp/usr/lib/python3/dist-packages/*.dist-info/COPYING': No such file or directory

Bug#1102440: xrt FTBFS in trixie: compilation failure due to lack of -Wno-error=mismatched-new-delete

2025-04-15 Thread Carlos Henrique Lima Melara
Hi, On Sun, 13 Apr 2025 23:10:19 -0300 Matheus Polkorny wrote: > The attached debdiff fixes a policy violation in xrt where a > compiler flag was conditionally applied only in unstable. I've just uploaded it to the DELAYED/2 queue. If you prefer I postpone or cancel the nmu, let me know. Also,

Processed: severity of 1067709 is important

2025-04-15 Thread Debian Bug Tracking System
Processing commands for cont...@bugs.debian.org: > severity 1067709 important Bug #1067709 [src:dante] FTBFS in armel/armhf: some symbols disappeared Severity set to 'important' from 'serious' > thanks Stopping processing here. Please contact me if you need assistance. -- 1067709: https://bugs.d

Processed: mpich

2025-04-15 Thread Debian Bug Tracking System
Processing commands for cont...@bugs.debian.org: > forwarded 1102612 https://github.com/pmodels/mpich/issues/7064 Bug #1102612 [mpich] mpich 4.3 not initialising multiple processes Set Bug forwarded-to-address to 'https://github.com/pmodels/mpich/issues/7064'. > End of message, stopping processing

Processed: bug 1102889 is forwarded to https://lore.kernel.org/regressions/z_6sh7byddqdk...@eldamar.lan/T/#u

2025-04-15 Thread Debian Bug Tracking System
Processing commands for cont...@bugs.debian.org: > forwarded 1102889 > https://lore.kernel.org/regressions/z_6sh7byddqdk...@eldamar.lan/T/#u Bug #1102889 [src:linux] linux-image-6.1.0-33-amd64: KVM GPU passthrough broken Bug #1102914 [src:linux] VMs don't start up when being passed through a PCI

Processed: your mail

2025-04-15 Thread Debian Bug Tracking System
Processing commands for cont...@bugs.debian.org: > tags 1103039 - pending Bug #1103039 [src:yubikey-manager] ModuleNotFoundError: No module named 'smartcard.pcsc.PCSCContext' since 2.2.1-2 to 2.2.2-1 upgrade Bug #1103211 [src:yubikey-manager] yubikey-manager: FTBFS: E ModuleNotFoundError: No m

Bug#1102889: [regression 6.1.y] Regression from 476c1dfefab8 ("mm: Don't pin ZERO_PAGE in pin_user_pages()") with pci-passthrough for both KVM VMs and booting in xen DomU

2025-04-15 Thread Salvatore Bonaccorso
Hi [Apologies if this has been reported already but I have not found an already filled corresponding report] After updating from the 6.1.129 based version to 6.1.133, various users have reported that their VMs do not boot anymore up (both KVM and under Xen) if pci-passthrough is involved. The rep

Processed: your mail

2025-04-15 Thread Debian Bug Tracking System
Processing commands for cont...@bugs.debian.org: > reassign 1103039 src:yubikey-manager Bug #1103039 [yubikey-manager] ModuleNotFoundError: No module named 'smartcard.pcsc.PCSCContext' since 2.2.1-2 to 2.2.2-1 upgrade Bug reassigned from package 'yubikey-manager' to 'src:yubikey-manager'. Ignorin

Processed: Pending

2025-04-15 Thread Debian Bug Tracking System
Processing commands for cont...@bugs.debian.org: > tags 1103039 + pending Bug #1103039 [src:yubikey-manager] ModuleNotFoundError: No module named 'smartcard.pcsc.PCSCContext' since 2.2.1-2 to 2.2.2-1 upgrade Bug #1103211 [src:yubikey-manager] yubikey-manager: FTBFS: E ModuleNotFoundError: No m

Processed: Re: [Debian-med-packaging] Bug#1103129: libbioparser-dev: FTBFS in testing/i386: make[1]: *** [debian/rules:11: override_dh_auto_configure] Error 2

2025-04-15 Thread Debian Bug Tracking System
Processing control commands: > tags -1 confirmed Bug #1103129 [src:libbioparser-dev] libbioparser-dev: FTBFS in testing/i386: make[1]: *** [debian/rules:11: override_dh_auto_configure] Error 2 Added tag(s) confirmed. -- 1103129: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1103129 Debian B

Bug#1103129: [Debian-med-packaging] Bug#1103129: libbioparser-dev: FTBFS in testing/i386: make[1]: *** [debian/rules:11: override_dh_auto_configure] Error 2

2025-04-15 Thread Étienne Mollier
Control: tags -1 confirmed Greetings, Making the find_package(biosoup) more verbose, I see the following warning when trying to build libbioparser-dev on i386: CMake Warning at CMakeLists.txt:25 (find_package): Could not find a configuration file for package "biosoup" that is

Bug#1102275: marked as done (feature trace is unusable)

2025-04-15 Thread Debian Bug Tracking System
Your message dated Tue, 15 Apr 2025 19:35:27 +0100 with message-id and subject line re: feature trace is unusable has caused the Debian Bug report #1102275, regarding feature trace is unusable to be marked as done. This means that you claim that the problem has been dealt with. If this is not the

Bug#1103186: commonmark-bkrs: FTBFS: help2man: can't get `--help' info from debian/adhoc/wrappers/python3/cmark-bkrs

2025-04-15 Thread Jerome BENOIT
Hello Santiago, thanks for the report. I could reproduce the issue on my box. I will try to fix this during the next week-end. Cheers, Jerome -- Jerome BENOIT | calculus+at-rezozer^dot*net https://qa.debian.org/developer.php?login=calcu...@rezozer.net AE28 AE15 710D FF1D 87E5 A762 3F92 19A6 7F36

Bug#1103211: Upstream fix for ykman incomplete - tests failing.

2025-04-15 Thread Patrick Winnertz
forcemerge 1103211 1103039 thanks Hey, There is a partial fix upstream available however they lock the version to <2.2.2 which won't help us within debian right now. So - sadly no fix available upstream yet. With the patch currently in salsa the build still fails like this: I: pybuild base:3

Processed (with 1 error): Upstream fix for ykman incomplete - tests failing.

2025-04-15 Thread Debian Bug Tracking System
Processing commands for cont...@bugs.debian.org: > forcemerge 1103211 1103039 Bug #1103211 [src:yubikey-manager] yubikey-manager: FTBFS: E ModuleNotFoundError: No module named 'smartcard.pcsc.PCSCContext' Unable to merge bugs because: package of #1103039 is 'yubikey-manager' not 'src:yubikey-ma

Processed: Bug#1103187 marked as pending in dssi

2025-04-15 Thread Debian Bug Tracking System
Processing control commands: > tag -1 pending Bug #1103187 [src:dssi] dssi: FTBFS: /usr/include/alsa/seq_event.h:30:2: error: #warning "use #include , should not be used directly" [-Werror=cpp] Added tag(s) pending. -- 1103187: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1103187 Debian

Bug#1103187: marked as pending in dssi

2025-04-15 Thread Andreas Henriksson
Control: tag -1 pending Hello, Bug #1103187 in dssi 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/dssi/-/commit/498e0fbff74eb804d0932af34f1ecf

Bug#1102516: Repacked source

2025-04-15 Thread Patrick Winnertz
tags 1102516 + pending thanks I've repacked the source with find -type f -exec touch {} \; in order to give every file a valid timestamp. The wrong timestamps are according to the upstream bug report a "feature". A new upload is however depending on a solution for the ModuleNotFoundError du

Processed: Repacked source

2025-04-15 Thread Debian Bug Tracking System
Processing commands for cont...@bugs.debian.org: > tags 1102516 + pending Bug #1102516 [src:yubikey-manager] yubikey-manager_5.6.1-1_all-buildd.changes REJECTED Added tag(s) pending. > thanks Stopping processing here. Please contact me if you need assistance. -- 1102516: https://bugs.debian.org

Bug#1102068: marked as done (libfabric: FTBFS on 32-bit arches: ofi_cma.h: error: passing argument 2 of 'ofi_consume_iov' from incompatible pointer type)

2025-04-15 Thread Debian Bug Tracking System
Your message dated Tue, 15 Apr 2025 18:22:39 + with message-id and subject line Bug#1102068: fixed in mpich 4.3.0-6 has caused the Debian Bug report #1102068, regarding libfabric: FTBFS on 32-bit arches: ofi_cma.h: error: passing argument 2 of 'ofi_consume_iov' from incompatible pointer type

Bug#1103229: marked as done (ltt-control:FTBFS:build failed(error: 'health_state' undeclared))

2025-04-15 Thread Debian Bug Tracking System
Your message dated Tue, 15 Apr 2025 18:19:46 + with message-id and subject line Bug#1103229: fixed in ltt-control 2.13.15-2 has caused the Debian Bug report #1103229, regarding ltt-control:FTBFS:build failed(error: 'health_state' undeclared) to be marked as done. This means that you claim tha

Bug#1103256: marked as done (golang-github-smallstep-crypto: FTBFS during tests when built with nebula >= 1.9.3)

2025-04-15 Thread Debian Bug Tracking System
Your message dated Tue, 15 Apr 2025 18:19:29 + with message-id and subject line Bug#1103256: fixed in golang-github-smallstep-certificates 0.20.0-5 has caused the Debian Bug report #1103256, regarding golang-github-smallstep-crypto: FTBFS during tests when built with nebula >= 1.9.3 to be ma

Bug#1100828: marked as done (debian-archive-keyring: trixie archive signing keys)

2025-04-15 Thread Debian Bug Tracking System
Your message dated Tue, 15 Apr 2025 18:17:25 + with message-id and subject line Bug#1100828: fixed in debian-archive-keyring 2023.3+deb12u2 has caused the Debian Bug report #1100828, regarding debian-archive-keyring: trixie archive signing keys to be marked as done. This means that you claim

Bug#1100829: marked as done (debian-archive-keyring: trixie SRM key)

2025-04-15 Thread Debian Bug Tracking System
Your message dated Tue, 15 Apr 2025 18:17:25 + with message-id and subject line Bug#1100829: fixed in debian-archive-keyring 2023.3+deb12u2 has caused the Debian Bug report #1100829, regarding debian-archive-keyring: trixie SRM key to be marked as done. This means that you claim that the prob

Bug#1099223: marked as done (debian-archive-keyring: FTBFS: gpg: Can't check signature: No public key)

2025-04-15 Thread Debian Bug Tracking System
Your message dated Tue, 15 Apr 2025 18:17:25 + with message-id and subject line Bug#1099223: fixed in debian-archive-keyring 2023.3+deb12u2 has caused the Debian Bug report #1099223, regarding debian-archive-keyring: FTBFS: gpg: Can't check signature: No public key to be marked as done. This

Bug#1103255: /usr/bin/rails: No $EDITOR to open file in. Assign one like this: EDITOR="mate --wait" bin/rails credentials:edit

2025-04-15 Thread Antonio Terceiro
Control: severity -1 normal On Tue, Apr 15, 2025 at 07:33:09PM +0200, наб wrote: > Package: ruby-railties > Version: 2:6.1.7.10+dfsg-1~deb12u1 > Severity: serious > Justification: Policy 11.4 > File: /usr/bin/rails > > Dear Maintainer, > > I just got > $ rails credentials:edit > No $EDITOR t

Processed: Re: Bug#1103255: /usr/bin/rails: No $EDITOR to open file in. Assign one like this: EDITOR="mate --wait" bin/rails credentials:edit

2025-04-15 Thread Debian Bug Tracking System
Processing control commands: > severity -1 normal Bug #1103255 [ruby-railties] /usr/bin/rails: No $EDITOR to open file in. Assign one like this: EDITOR="mate --wait" bin/rails credentials:edit Severity set to 'normal' from 'serious' -- 1103255: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=

Bug#1103252: rust-pprof - soundness issue RUSTSEC-2024-0408

2025-04-15 Thread Alexander Kjäll
pprof was at some point needed for the gix stack, if they have moved away from using it then I agree that it's not needed in trixie. Will this bug be enought to block it, or do we need to do anything more? Den tis 15 apr. 2025 kl 17:57 skrev Peter Green : > > Package: rust-pprof > Version: 0.13.0

Bug#1103256: golang-github-smallstep-crypto: FTBFS during tests when built with nebula >= 1.9.3

2025-04-15 Thread Jérémy Lal
Source: golang-github-smallstep-crypto Version: 0.57.0-1 Severity: serious Tags: ftbfs This is https://ci.debian.net/packages/g/golang-github-smallstep-certificates/testing/amd64/59900165/ 143s # github.com/smallstep/certificates/authority/provisioner [github.com/smallstep/certificates/authorit

Bug#1103239: marked as done (all-knowing-dns: service doesn't start at all (Net::DNS incompatibility))

2025-04-15 Thread Debian Bug Tracking System
Your message dated Tue, 15 Apr 2025 15:18:56 + with message-id and subject line Bug#1103239: fixed in all-knowing-dns 1.7-7 has caused the Debian Bug report #1103239, regarding all-knowing-dns: service doesn't start at all (Net::DNS incompatibility) to be marked as done. This means that you

Bug#1101712: marked as done (ruby-mail-room: FTBFS: Failure/Error: @server.start)

2025-04-15 Thread Debian Bug Tracking System
Your message dated Tue, 15 Apr 2025 17:44:39 + with message-id and subject line Bug#1102689: Removed package(s) from unstable has caused the Debian Bug report #1101712, regarding ruby-mail-room: FTBFS: Failure/Error: @server.start to be marked as done. This means that you claim that the probl

Bug#1082382: marked as done (ruby-devise-two-factor: CVE-2024-8796)

2025-04-15 Thread Debian Bug Tracking System
Your message dated Tue, 15 Apr 2025 17:43:18 + with message-id and subject line Bug#1102667: Removed package(s) from unstable has caused the Debian Bug report #1082382, regarding ruby-devise-two-factor: CVE-2024-8796 to be marked as done. This means that you claim that the problem has been de

Bug#1100967: marked as done (golang-step-crypto-dev and golang-github-smallstep-crypto-dev have undeclared file conflicts)

2025-04-15 Thread Debian Bug Tracking System
Your message dated Tue, 15 Apr 2025 17:41:53 + with message-id and subject line Bug#1102636: Removed package(s) from unstable has caused the Debian Bug report #1100967, regarding golang-step-crypto-dev and golang-github-smallstep-crypto-dev have undeclared file conflicts to be marked as done.

Bug#1095881: marked as done (ruby-devise: autopkgtest failure with rails 7: /usr/share/rubygems-integration/all/gems/railties-7.2.2.1/lib/rails/generators/app_base.rb:750:in ``': No such file or direc

2025-04-15 Thread Debian Bug Tracking System
Your message dated Tue, 15 Apr 2025 17:44:13 + with message-id and subject line Bug#1102688: Removed package(s) from unstable has caused the Debian Bug report #1095881, regarding ruby-devise: autopkgtest failure with rails 7: /usr/share/rubygems-integration/all/gems/railties-7.2.2.1/lib/rails

Bug#1084360: marked as done (ruby-devise-two-factor: FTBFS: failing tests)

2025-04-15 Thread Debian Bug Tracking System
Your message dated Tue, 15 Apr 2025 17:43:18 + with message-id and subject line Bug#1102667: Removed package(s) from unstable has caused the Debian Bug report #1084360, regarding ruby-devise-two-factor: FTBFS: failing tests to be marked as done. This means that you claim that the problem has

Bug#1103061: node-prop-types: FTBFS in testing/i386: make: *** [debian/rules:5: binary] Error 25

2025-04-15 Thread Lucas Nussbaum
Source: node-prop-types Version: 15.8.1+~15.7.9+~cs1.1.1-1 Severity: serious Justification: FTBFS Tags: trixie sid ftbfs User: lu...@debian.org Usertags: ftbfs-20250414 ftbfs-trixie Hi, During a rebuild of all packages in testing (trixie), your package failed to build on i386. Relevant part (ho

Bug#1103224: libssh: FTBFS: /<>/build-openssl/tests/tests_config.h:3:41: error: missing binary operator before token ".0p2"

2025-04-15 Thread Santiago Vila
Package: src:libssh Version: 0.11.1-1 Severity: serious Tags: ftbfs trixie sid Dear maintainer: During a rebuild of all packages in unstable, your package failed to build: [...] [ 47%] Building C object examples/CMa

Bug#1103189: gpgme1.0: FTBFS: FAIL! : CryptoConfigTest::testDefault() Compared values are not the same

2025-04-15 Thread Andreas Metzler
On 2025-04-15 Santiago Vila wrote: > Package: src:gpgme1.0 > Version: 1.24.2-1 > Severity: serious > Tags: ftbfs trixie sid > Dear maintainer: > During a rebuild of all packages in unstable, your package failed to build: >

Processed: Re: Bug#1102967: python-booleanoperations: FTBFS in testing: KeyError: 'setuptools_scm'

2025-04-15 Thread Debian Bug Tracking System
Processing control commands: > tags -1 +help Bug #1102967 [src:python-booleanoperations] python-booleanoperations: FTBFS in testing: BooleanTests Added tag(s) help. -- 1102967: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1102967 Debian Bug Tracking System Contact ow...@bugs.debian.org wit

Bug#1103063: r-cran-themis: FTBFS in testing/i386: make: *** [debian/rules:4: binary] Error 25

2025-04-15 Thread Lucas Nussbaum
Source: r-cran-themis Version: 1.0.3-1 Severity: serious Justification: FTBFS Tags: trixie sid ftbfs User: lu...@debian.org Usertags: ftbfs-20250414 ftbfs-trixie Hi, During a rebuild of all packages in testing (trixie), your package failed to build on i386. Relevant part (hopefully): > debian/

Bug#1089267: marked as done (memkind: FTBFS with make 4.4.1)

2025-04-15 Thread Debian Bug Tracking System
Your message dated Tue, 15 Apr 2025 17:40:11 + with message-id and subject line Bug#1102530: Removed package(s) from unstable has caused the Debian Bug report #1089267, regarding memkind: FTBFS with make 4.4.1 to be marked as done. This means that you claim that the problem has been dealt wit

Bug#1078314: marked as done (qtorganizer-eds: FTBFS: The following tests FAILED: 5 - recurrence-test (Failed))

2025-04-15 Thread Debian Bug Tracking System
Your message dated Tue, 15 Apr 2025 17:39:16 + with message-id and subject line Bug#1102510: Removed package(s) from unstable has caused the Debian Bug report #1078314, regarding qtorganizer-eds: FTBFS: The following tests FAILED: 5 - recurrence-test (Failed) to be marked as done. This means

Bug#1091960: marked as done (xfce4-sntray-plugin: FTBFS: mv: cannot stat '/<>/debian/tmp/usr/lib/xfce4': No such file or directory)

2025-04-15 Thread Debian Bug Tracking System
Your message dated Tue, 15 Apr 2025 17:36:48 + with message-id and subject line Bug#1102506: Removed package(s) from unstable has caused the Debian Bug report #1091960, regarding xfce4-sntray-plugin: FTBFS: mv: cannot stat '/<>/debian/tmp/usr/lib/xfce4': No such file or directory to be marked

Bug#1086771: marked as done (vala-sntray-plugin: Wrong placement of the library file prevents detection of the plugin by vala-panel)

2025-04-15 Thread Debian Bug Tracking System
Your message dated Tue, 15 Apr 2025 17:36:48 + with message-id and subject line Bug#1102506: Removed package(s) from unstable has caused the Debian Bug report #1086771, regarding vala-sntray-plugin: Wrong placement of the library file prevents detection of the plugin by vala-panel to be marke

Bug#1053625: marked as done (rust-extprim: Remove from Debian?)

2025-04-15 Thread Debian Bug Tracking System
Your message dated Tue, 15 Apr 2025 17:36:16 + with message-id and subject line Bug#1101718: Removed package(s) from unstable has caused the Debian Bug report #1053625, regarding rust-extprim: Remove from Debian? to be marked as done. This means that you claim that the problem has been dealt

Bug#1089185: marked as done (liboqs: CVE-2024-54137)

2025-04-15 Thread Debian Bug Tracking System
Your message dated Tue, 15 Apr 2025 17:34:54 + with message-id and subject line Bug#1100144: Removed package(s) from unstable has caused the Debian Bug report #1089185, regarding liboqs: CVE-2024-54137 to be marked as done. This means that you claim that the problem has been dealt with. If th

Bug#1073250: marked as done (liboqs: CVE-2024-36405)

2025-04-15 Thread Debian Bug Tracking System
Your message dated Tue, 15 Apr 2025 17:34:54 + with message-id and subject line Bug#1100144: Removed package(s) from unstable has caused the Debian Bug report #1073250, regarding liboqs: CVE-2024-36405 to be marked as done. This means that you claim that the problem has been dealt with. If th

Bug#1064714: marked as done (codraft: FTBFS: ImportError: cannot import name 'update_dataset' from 'guidata.dataset' (/usr/lib/python3/dist-packages/guidata/dataset/__init__.py))

2025-04-15 Thread Debian Bug Tracking System
Your message dated Tue, 15 Apr 2025 17:33:29 + with message-id and subject line Bug#1099982: Removed package(s) from unstable has caused the Debian Bug report #1064714, regarding codraft: FTBFS: ImportError: cannot import name 'update_dataset' from 'guidata.dataset' (/usr/lib/python3/dist-pac

Bug#1068502: marked as done (Dead upstream and broken, remove or switch to a fork?)

2025-04-15 Thread Debian Bug Tracking System
Your message dated Tue, 15 Apr 2025 17:35:24 + with message-id and subject line Bug#1101522: Removed package(s) from unstable has caused the Debian Bug report #1068502, regarding Dead upstream and broken, remove or switch to a fork? to be marked as done. This means that you claim that the pro

Bug#1065802: marked as done (liboqs: FTBFS: Configuring incomplete, errors occurred!)

2025-04-15 Thread Debian Bug Tracking System
Your message dated Tue, 15 Apr 2025 17:34:54 + with message-id and subject line Bug#1100144: Removed package(s) from unstable has caused the Debian Bug report #1065802, regarding liboqs: FTBFS: Configuring incomplete, errors occurred! to be marked as done. This means that you claim that the p

Bug#1027825: marked as done (bind-dyndb-ldap: FTBFS in bullseye (‘dns_dyndbctx_t’ has no member named ‘refvar’))

2025-04-15 Thread Debian Bug Tracking System
Your message dated Tue, 15 Apr 2025 17:33:04 + with message-id and subject line Bug#1099981: Removed package(s) from unstable has caused the Debian Bug report #1027825, regarding bind-dyndb-ldap: FTBFS in bullseye (‘dns_dyndbctx_t’ has no member named ‘refvar’) to be marked as done. This mea

Bug#1012893: marked as done (anfo: ftbfs with GCC-12)

2025-04-15 Thread Debian Bug Tracking System
Your message dated Tue, 15 Apr 2025 17:34:21 + with message-id and subject line Bug#1099985: Removed package(s) from unstable has caused the Debian Bug report #1012893, regarding anfo: ftbfs with GCC-12 to be marked as done. This means that you claim that the problem has been dealt with. If t

Bug#1064294: marked as done (bind-dyndb-ldap: FTBFS: error: Install BIND9 development files)

2025-04-15 Thread Debian Bug Tracking System
Your message dated Tue, 15 Apr 2025 17:33:04 + with message-id and subject line Bug#1099981: Removed package(s) from unstable has caused the Debian Bug report #1064294, regarding bind-dyndb-ldap: FTBFS: error: Install BIND9 development files to be marked as done. This means that you claim tha

Bug#1061888: marked as done (anfo: NMU diff for 64-bit time_t transition)

2025-04-15 Thread Debian Bug Tracking System
Your message dated Tue, 15 Apr 2025 17:34:21 + with message-id and subject line Bug#1099985: Removed package(s) from unstable has caused the Debian Bug report #1061888, regarding anfo: NMU diff for 64-bit time_t transition to be marked as done. This means that you claim that the problem has b

Bug#1060107: marked as done (urweb: FTBFS: http.c:119:32: error: pointer ‘buf’ may be used after ‘realloc’)

2025-04-15 Thread Debian Bug Tracking System
Your message dated Tue, 15 Apr 2025 17:33:56 + with message-id and subject line Bug#1099983: Removed package(s) from unstable has caused the Debian Bug report #1060107, regarding urweb: FTBFS: http.c:119:32: error: pointer ‘buf’ may be used after ‘realloc’ to be marked as done. This means th

Bug#1008980: marked as done (adabrowse: depends on unavailable asis)

2025-04-15 Thread Debian Bug Tracking System
Your message dated Tue, 15 Apr 2025 17:32:35 + with message-id and subject line Bug#1099979: Removed package(s) from unstable has caused the Debian Bug report #1008980, regarding adabrowse: depends on unavailable asis to be marked as done. This means that you claim that the problem has been d

  1   2   >