Bug#1103197: marked as done (pympress: FTBFS: error: error in setup.cfg: command 'compile_catalog' has no such option 'use-fuzzy')

Your message dated Thu, 17 Apr 2025 00:51:30 + with message-id and subject line Bug#1103197: fixed in pympress 1.8.5-3 has caused the Debian Bug report #1103197, regarding pympress: FTBFS: error: error in setup.cfg: command 'compile_catalog' has no such option 'use-fuzzy' to be marked as done

Processed: Re: rust-wide: FTBFS in testing/i386: dh_auto_test: error: /usr/share/dh-rust/bin/cargo test returned exit code 101

Processing control commands: > severity -1 important Bug #1103130 [src:rust-wide] rust-wide: FTBFS in testing/i386: dh_auto_test: error: /usr/share/dh-rust/bin/cargo test returned exit code 101 Severity set to 'important' from 'serious' > block -1 by 1095862 Bug #1103130 [src:rust-wide] rust-wide

Bug#1103227: [R-pkg-team] Bug#1103227: [reply ] r-bioc-grohmm: FTBFS: DecayAlgorithm.c:94:15: error: expected identifier or '(' before 'false'

Le Thu, Apr 17, 2025 at 01:37:01PM +0800, liwenjun a écrit : > > I founded a commit on the upstream for fixing this problem: > > Bioconductor Code: groHMM > > > Or you might prefer to upgrade the major

Bug#1103400: [thunderbird on armhf] E: Package 'thunderbird' has no installation candidate

Package: thunderbird Version: 1:128.9.0esr-1~deb12u1 Severity: grave Dear maintainers I am instaling Debian OS on many targets on architectures armhf,arm64, armd64 abd i386. On armhf, thunderbird is not available for unknowed raeson, ansible@vn-debian-armhf-110:~$ uname -a Linux vn-debian-a

Bug#1103227: [reply ] r-bioc-grohmm: FTBFS: DecayAlgorithm.c:94:15: error: expected identifier or '(' before 'false'

Package: src:r-bioc-grohmm Version: 1.40.3-2 Severity: serious Tags: ftbfs trixie sid Dear maintainer: I founded a commit on the upstream for fixing this problem: Bioconductor Code: groHMM Or you mig

Bug#1103199: [R-pkg-team] Bug#1103199: Bug#1103199: [PATCH] Fix for FTBFS with R 4.5.0

Le Wed, Apr 16, 2025 at 05:21:59PM +0900, Charles Plessy a écrit : > > Instead of carrying a patch, I would like to propose to upgrade to the new > upstream version that will be released very soon. Hi again, I tested an upgrade locally, but it gets convoluted with the Bioconductor transition th

Processed: Re: ceph: FTBFS in testing/arm64: c++: fatal error: Killed signal terminated program cc1plus

Processing commands for cont...@bugs.debian.org: > severity 1103358 important Bug #1103358 [src:ceph] ceph: FTBFS in testing/arm64: c++: fatal error: Killed signal terminated program cc1plus Severity set to 'important' from 'serious' > tag 1103358 + moreinfo Bug #1103358 [src:ceph] ceph: FTBFS in

Bug#1103358: ceph: FTBFS in testing/arm64: c++: fatal error: Killed signal terminated program cc1plus

severity 1103358 important tag 1103358 + moreinfo thanks Hi, ceph builds fine on arm64 and I just did a successfull rebuild as well. Looking at the buildlog, it looks more like the issues comming from the crude cpu/ram-based calculation to set the number of parallel jobs. I've replaced that w

Bug#1102160: upgrade-reports: Bookworm to Trixie [amd64][EFI] initramfs unpacking failed invalid magic at start of compressed archive

ke 16.4.2025 klo 20.40 Pascal Hambourg (pas...@plouf.fr.eu.org) kirjoitti: > > On 16/04/2025 at 15:51, Martin-Éric Racine wrote: > > ke 16.4.2025 klo 15.41 Pascal Hambourg (pas...@plouf.fr.eu.org) kirjoitti: > >> On 16/04/2025 at 13:38, Martin-Éric Racine wrote: > >>> > >>> As the attached screensh

Bug#1103396: rmysql-connector-python: CVE-2025-30714

Source: mysql-connector-python Version: 9.2.0-1 Severity: grave Tags: security upstream X-Debbugs-Cc: car...@debian.org, Debian Security Team Hi, The following vulnerability was published for mysql-connector-python. CVE-2025-30714[0]: | Vulnerability in the MySQL Connectors product of Oracle My

Bug#1103371: marked as done (fwupd: FTBFS in testing/armhf: ../plugins/modem-manager/fu-dfota-updater.c:165:71: error: passing argument 5 of ‘g_ascii_string_to_unsigned’ from incompatible pointer type

System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: fwupd Version: 2.0.8-1 Severity: serious Justification: FTBFS Tags: trixie sid ftbfs User: lu...@debian.org Usertags: ftbfs-20250416 ftbfs-trixie Hi, During a rebuild of all packages in testing (trixie), your package

Bug#1103300: marked as done (rust-ring:FTBFS:build failed(abort: could not determine source-distribution conditions of build/ring-ea02091f2e9fc04e/out/libring_core_0_17_14__test.a）)

Your message dated Thu, 17 Apr 2025 02:37:20 + with message-id and subject line Bug#1103300: fixed in rust-ring 0.17.14-2 has caused the Debian Bug report #1103300, regarding rust-ring:FTBFS:build failed(abort: could not determine source-distribution conditions of build/ring-ea02091f2e9fc04e

Bug#1102946: marked as done (python-pyepics: FTBFS in testing: ImportError: /usr/lib/python3/dist-packages/wx/_core.cpython-313-x86_64-linux-gnu.so: undefined symbol: _ZN14wxTranslations27GetBestAvail

Your message dated Wed, 16 Apr 2025 13:12:15 -0400 (EDT) with message-id and subject line Fixed in 4.2.3+dfsg-2 has caused the Debian Bug report #1102946, regarding python-pyepics: FTBFS in testing: ImportError: /usr/lib/python3/dist-packages/wx/_core.cpython-313-x86_64-linux-gnu.so: undefined s

Bug#1103184: marked as done (cairosvg: FTBFS: dh_install: warning: Cannot find (any matches for) "usr/bin/cairosvg")

Your message dated Thu, 17 Apr 2025 00:49:10 + with message-id and subject line Bug#1103184: fixed in cairosvg 2.7.1-2 has caused the Debian Bug report #1103184, regarding cairosvg: FTBFS: dh_install: warning: Cannot find (any matches for) "usr/bin/cairosvg" to be marked as done. This means

Bug#1103197: marked as pending in pympress

Control: tag -1 pending Hello, Bug #1103197 in pympress 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/pympress/-/commit/001ea289d70980097

Processed: tagging 1103385

Processing commands for cont...@bugs.debian.org: > tags 1103385 + upstream Bug #1103385 [src:mysql-8.0] mysql-8.0: CVE-2025-30722 CVE-2025-30721 CVE-2025-30715 CVE-2025-30705 CVE-2025-30704 CVE-2025-30703 CVE-2025-30699 CVE-2025-30696 CVE-2025-30695 CVE-2025-30693 CVE-2025-30689 CVE-2025-30688

Processed: Bug#1103197 marked as pending in pympress

Processing control commands: > tag -1 pending Bug #1103197 [src:pympress] pympress: FTBFS: error: error in setup.cfg: command 'compile_catalog' has no such option 'use-fuzzy' Added tag(s) pending. -- 1103197: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1103197 Debian Bug Tracking System C

Processed: Bug#1103184 marked as pending in cairosvg

Processing control commands: > tag -1 pending Bug #1103184 [src:cairosvg] cairosvg: FTBFS: dh_install: warning: Cannot find (any matches for) "usr/bin/cairosvg" Added tag(s) pending. -- 1103184: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1103184 Debian Bug Tracking System Contact ow...@b

Bug#1103184: marked as pending in cairosvg

Control: tag -1 pending Hello, Bug #1103184 in cairosvg 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/cairosvg/-/commit/9db9127ec43329524

Bug#1103360: firefox-esr: FTBFS in testing/arm64: make[6]: *** [/build/reproducible-path/firefox-esr-128.9.0esr/config/makefiles/rust.mk:500: force-cargo-library-build] Error 101

On 17/04/25 at 06:07 +0900, Mike Hommey wrote: > On Wed, Apr 16, 2025 at 08:40:14PM +0200, Lucas Nussbaum wrote: > > Source: firefox-esr > > Version: 128.9.0esr-2 > > Severity: serious > > Justification: FTBFS > > Tags: trixie sid ftbfs > > User: lu...@debian

Bug#1103369: r-cran-webgestaltr: FTBFS in testing/armhf: make: *** [debian/rules:4: binary-arch] Error 25

Source: r-cran-webgestaltr Version: 0.4.6-1 Severity: serious Justification: FTBFS Tags: trixie sid ftbfs User: lu...@debian.org Usertags: ftbfs-20250416 ftbfs-trixie Hi, During a rebuild of all packages in testing (trixie), your package failed to build on armhf. Relevant part (hopefully

Bug#1075696: yeahconsole: diff for NMU version 0.3.4-6.1

Control: tags 1075696 + patch Control: tags 1075696 + pending Dear maintainer, I've prepared an NMU for yeahconsole (versioned as 0.3.4-6.1) and uploaded it to DELAYED/2. Please feel free to tell me if I should cancel it. Regards. diffstat for yeahconsole-0.3.4 yeahconsole-0.3.4 changelog

Processed: yeahconsole: diff for NMU version 0.3.4-6.1

Processing control commands: > tags 1075696 + patch Bug #1075696 [src:yeahconsole] yeahconsole: ftbfs with GCC-14 Added tag(s) patch. > tags 1075696 + pending Bug #1075696 [src:yeahconsole] yeahconsole: ftbfs with GCC-14 Added tag(s) pending. -- 1075696: https://bugs.debian.org/cgi-bin/bugreport

Bug#1103127: marked as done (node-webfont: FTBFS in testing/i386: dh_auto_test: error: cd ./svgicons2svgfont && sh -ex ../debian/nodejs/svgicons2svgfont/test returned exit code 139)

Your message dated Wed, 16 Apr 2025 22:06:21 + with message-id and subject line Bug#1103127: fixed in node-webfont 11.4.0+dfsg2+~cs35.7.26-13 has caused the Debian Bug report #1103127, regarding node-webfont: FTBFS in testing/i386: dh_auto_test: error: cd ./svgicons2svgfont && sh -ex ../debia

Bug#1103127: marked as pending in node-webfont

Control: tag -1 pending Hello, Bug #1103127 in node-webfont 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/js-team/node-webfont/-/commit/f427e413cf12cc2e0690d3

Processed: bug 1102889 is forwarded to https://lore.kernel.org/regressions/z_6sh7byddqdk...@eldamar.lan/T/#u https://lore.kernel.org/all/20250416202441.3911142-1-alex.william...@redhat.com/

Processing commands for cont...@bugs.debian.org: > forwarded 1102889 > https://lore.kernel.org/regressions/z_6sh7byddqdk...@eldamar.lan/T/#u > https://lore.kernel.org/all/20250416202441.3911142-1-alex.william...@redhat.com/ Bug #1102889 [src:linux] linux-image-6.1.0-33-amd64: KVM GPU passthrough

Bug#1103119: golang-github-go-kit-kit: FTBFS in testing/i386: dh_auto_test: error

This isn't an i386-specific issue, but rather a flaky test (or maybe more than one) that do some sort of time sampling. I've previously filed #1102485 about this showing up as flaky autopkgtests which pass when re-run. I'd strongly prefer the tests actually be fixed than just skipped, but I ha

Bug#1103360: firefox-esr: FTBFS in testing/arm64: make[6]: *** [/build/reproducible-path/firefox-esr-128.9.0esr/config/makefiles/rust.mk:500: force-cargo-library-build] Error 101

On 16/04/25 at 23:30 +0200, Santiago Vila wrote: > El 16/4/25 a las 23:07, Mike Hommey escribió: > > The most relevant part of the log says: (signal: 9, SIGKILL: kill) > > > > This was OOM killed. IOW, not enough memory on the builder you used. > > > > Is this something that runs on buildds or so

Bug#1103365: chirp GUI does not start, undefined symbol

This looks to be related to #1102946, #1102955 and likely fixed by 4.2.3+dfsg-2. Will advise once it migrates to testing.

Processed: mdanalysis

Processing commands for cont...@bugs.debian.org: > forwarded 1103158 https://github.com/MDAnalysis/mdanalysis/issues/4209 Bug #1103158 [src:mdanalysis] mdanalysis: autopkgtest on amd64 times out Set Bug forwarded-to-address to 'https://github.com/MDAnalysis/mdanalysis/issues/4209'. > forwarded 11

Bug#984810: courier-authlib: CVE-2021-28374: /run/courier/authdaemon directory with weak permissions

It is unclear to me why this bug was reopened when it is marked as fixed for all the current version in supported Debian releases. Does anyone know if there is a reason, or should I close it again? -- Soren Stoutner so...@debian.org signature.asc Description: This is a digitally signed messag

Bug#1103360: firefox-esr: FTBFS in testing/arm64: make[6]: *** [/build/reproducible-path/firefox-esr-128.9.0esr/config/makefiles/rust.mk:500: force-cargo-library-build] Error 101

El 16/4/25 a las 23:07, Mike Hommey escribió: The most relevant part of the log says: (signal: 9, SIGKILL: kill) This was OOM killed. IOW, not enough memory on the builder you used. Is this something that runs on buildds or some other machines? Hi. This is an archive rebuild for QA purposes,

Bug#1103360: firefox-esr: FTBFS in testing/arm64: make[6]: *** [/build/reproducible-path/firefox-esr-128.9.0esr/config/makefiles/rust.mk:500: force-cargo-library-build] Error 101

On Wed, Apr 16, 2025 at 08:40:14PM +0200, Lucas Nussbaum wrote: > Source: firefox-esr > Version: 128.9.0esr-2 > Severity: serious > Justification: FTBFS > Tags: trixie sid ftbfs > User: lu...@debian.org > Usertags: ftbfs-20250416 ftbfs-trixie > > Hi, > > Du

Bug#1103371: fwupd: FTBFS in testing/armhf: ../plugins/modem-manager/fu-dfota-updater.c:165:71: error: passing argument 5 of ‘g_ascii_string_to_unsigned’ from incompatible pointer type [-Wincompatible

id ftbfs > User: lu...@debian.org > Usertags: ftbfs-20250416 ftbfs-trixie > > Hi, > > During a rebuild of all packages in testing (trixie), your package failed > to build on armhf. > > > Relevant part (hopefully): > > cc -Iplugins/modem-manager/libfu_plugin_modem_

Bug#1102938: apptainer and singularity-container have an undeclared file conflict on /usr/bin/run-singularity and /usr/bin/singularity

> Le 13/04/2025 à 12:53, Helmut Grohne a écrit : > > The files > > * /usr/bin/run-singularity > > * /usr/bin/singularity > > are contained in the packages > > * apptainer/1.4.0-2+b1 as present in unstable > > * singularity-container/4.1.5+ds4-1+b1 as present in unstable > > Hi debian-hpc, N

Bug#1103306: this looks like a problem with a feature introduced in ruby 3.2

On 4/16/25 5:35 PM, Pirate Praveen wrote: On 4/16/25 5:21 PM, Pirate Praveen wrote: These lines should be removed from gitlab-apt-pin-preferences to allow newer versions from trixie Package: ruby-murmurhash3 Pin: release n=bookworm Pin-Priority: 1000 Package: ruby-grape ruby-bootsnap ruby

Bug#1103373: rjava: FTBFS in testing/armel: configure: error: One or more Java configuration variables are not set.

sid ftbfs | > | User: lu...@debian.org | > | Usertags: ftbfs-20250416 ftbfs-trixie | > | | > | Hi, | > | | > | During a rebuild of all packages in testing (trixie), your package failed | > | to build on armel. | > | > Can you tru 1.0-11-2, please? It has | >

Bug#1103373: rjava: FTBFS in testing/armel: configure: error: One or more Java configuration variables are not set.

On 16/04/25 at 14:51 -0500, Dirk Eddelbuettel wrote: > > On 16 April 2025 at 21:27, Lucas Nussbaum wrote: > | Source: rjava > | Version: 1.0-11-1 > | Severity: serious > | Justification: FTBFS > | Tags: trixie sid ftbfs > | User: lu...@debian.org > | Usertags:

Bug#1101902: ruby-cleanroom: Should ruby-cleanroom be removed from unstable?

Control: severity -1 normal Control: retitle -1 RM: ruby-cleanroom -- RoM; rc-buggy Control: reassign -1 ftp.debian.org Control: affects -1 + src:ruby-cleanroom On Wed, 02 Apr 2025 07:30:11 +0200 Andreas Tille wrote: In case the package should be removed from unstable, you may reassign this bu

Bug#1102160: upgrade-reports: Bookworm to Trixie [amd64][EFI] initramfs unpacking failed invalid magic at start of compressed archive

On 16/04/2025 at 15:51, Martin-Éric Racine wrote: ke 16.4.2025 klo 15.41 Pascal Hambourg (pas...@plouf.fr.eu.org) kirjoitti: On 16/04/2025 at 13:38, Martin-Éric Racine wrote: As the attached screenshot shows, 'fuseblk' seemingly doesn't know anything about the 'subvol' option for btrfs, which

Bug#1103385: mysql-8.0: CVE-2025-30722 CVE-2025-30721 CVE-2025-30715 CVE-2025-30705 CVE-2025-30704 CVE-2025-30703 CVE-2025-30699 CVE-2025-30696 CVE-2025-30695 CVE-2025-30693 CVE-2025-30689 CVE-2025-30

Source: mysql-8.0 X-Debbugs-CC: t...@security.debian.org Severity: grave Tags: security Hi, The following vulnerabilities were published for mysql-8.0. CVE-2025-30722[0]: | Vulnerability in the MySQL Client product of Oracle MySQL | (component: Client: mysqldump). Supported versions that are |

Processed: Re: ruby-cleanroom: Should ruby-cleanroom be removed from unstable?

Processing control commands: > severity -1 normal Bug #1101902 [src:ruby-cleanroom] ruby-cleanroom: Should ruby-cleanroom be removed from unstable? Severity set to 'normal' from 'serious' > retitle -1 RM: ruby-cleanroom -- RoM; rc-buggy Bug #1101902 [src:ruby-cleanroom] ruby-cleanroom: Should rub

Bug#1103373: rjava: FTBFS in testing/armel: configure: error: One or more Java configuration variables are not set.

On 16 April 2025 at 21:27, Lucas Nussbaum wrote: | Source: rjava | Version: 1.0-11-1 | Severity: serious | Justification: FTBFS | Tags: trixie sid ftbfs | User: lu...@debian.org | Usertags: ftbfs-20250416 ftbfs-trixie | | Hi, | | During a rebuild of all packages in testing (trixie), your

Bug#1103211: marked as done (yubikey-manager: FTBFS: E ModuleNotFoundError: No module named 'smartcard.pcsc.PCSCContext')

Your message dated Wed, 16 Apr 2025 19:39:50 + with message-id and subject line Bug#1103039: fixed in yubikey-manager 5.6.1+repack1-1 has caused the Debian Bug report #1103039, regarding yubikey-manager: FTBFS: E ModuleNotFoundError: No module named 'smartcard.pcsc.PCSCContext' to be marked

Bug#1103039: marked as done (ModuleNotFoundError: No module named 'smartcard.pcsc.PCSCContext' since 2.2.1-2 to 2.2.2-1 upgrade)

Your message dated Wed, 16 Apr 2025 19:39:50 + with message-id and subject line Bug#1103039: fixed in yubikey-manager 5.6.1+repack1-1 has caused the Debian Bug report #1103039, regarding ModuleNotFoundError: No module named 'smartcard.pcsc.PCSCContext' since 2.2.1-2 to 2.2.2-1 upgrade to be m

Bug#1103361: golang-github-awslabs-soci-snapshotter: FTBFS with the unshare backend

retitle 1103361 golang-github-awslabs-soci-snapshotter: FTBFS with the unshare backend thanks Some additional notes about this bug: - It also happens on amd64, so it's not arm64-specific. - It happens when using the unshare backend of sbuild, but not when using the traditional schroot backend.

Bug#1103211: marked as done (yubikey-manager: FTBFS: E ModuleNotFoundError: No module named 'smartcard.pcsc.PCSCContext')

Your message dated Wed, 16 Apr 2025 19:39:50 + with message-id and subject line Bug#1103211: fixed in yubikey-manager 5.6.1+repack1-1 has caused the Debian Bug report #1103211, regarding yubikey-manager: FTBFS: E ModuleNotFoundError: No module named 'smartcard.pcsc.PCSCContext' to be marked

Bug#1103039: marked as done (ModuleNotFoundError: No module named 'smartcard.pcsc.PCSCContext' since 2.2.1-2 to 2.2.2-1 upgrade)

Your message dated Wed, 16 Apr 2025 19:39:50 + with message-id and subject line Bug#1103211: fixed in yubikey-manager 5.6.1+repack1-1 has caused the Debian Bug report #1103211, regarding ModuleNotFoundError: No module named 'smartcard.pcsc.PCSCContext' since 2.2.1-2 to 2.2.2-1 upgrade to be m

Bug#1100767: wsdd: Obsolete conffile /etc/default/wsdd

Hi! Wsdd is a binary only package for use with Gnome etc, wsdd-s3rver adds the systemd conf files to run it as a daemon on a samba server to replace samba nmbd. Best Regards, Matt Grant On Wed, 16 Apr 2025, 8:42 pm Adrian Bunk, wrote: > On Sun, Mar 30, 2025 at 04:33:36PM +0200, Michael Biebl

Bug#1102516: marked as done (yubikey-manager_5.6.1-1_all-buildd.changes REJECTED)

Your message dated Wed, 16 Apr 2025 19:39:50 + with message-id and subject line Bug#1102516: fixed in yubikey-manager 5.6.1+repack1-1 has caused the Debian Bug report #1102516, regarding yubikey-manager_5.6.1-1_all-buildd.changes REJECTED to be marked as done. This means that you claim that t

Bug#1103352: dxvk: FTBFS on armhf and other non-x86 non-aarch64 architectures: #error "Unknown CPU Architecture"

Control: forwarded -1 https://github.com/doitsujin/dxvk/pull/4853 On Wed, 16 Apr 2025 at 17:45:32 +0100, Simon McVittie wrote: > There seem to be two places in the dxvk codebase that #error out if the > CPU architecture is not recognised. > > 1. src/util/util_bit.h > 2. src/util/sync/sync_spinloc

Processed: Re: Bug#1103352: dxvk: FTBFS on armhf and other non-x86 non-aarch64 architectures: #error "Unknown CPU Architecture"

Processing control commands: > forwarded -1 https://github.com/doitsujin/dxvk/pull/4853 Bug #1103352 [src:dxvk] dxvk: FTBFS on armhf and other non-x86 non-aarch64 architectures: #error "Unknown CPU Architecture" Set Bug forwarded-to-address to 'https://github.com/doitsujin/dxvk/pull/4853'. -- 1

Bug#1103376: libmypaint: FTBFS in testing/armel: dh_auto_test: error: make -j4 check "TESTSUITEFLAGS=-j4 --verbose" VERBOSE=1 returned exit code 2

Source: libmypaint Version: 1.6.0-3 Severity: serious Justification: FTBFS Tags: trixie sid ftbfs User: lu...@debian.org Usertags: ftbfs-20250416 ftbfs-trixie Hi, During a rebuild of all packages in testing (trixie), your package failed to build on armel. Relevant part (hopefully): > mak

Bug#1103368: dosbox-x: FTBFS in testing/armhf: ../../../src/hardware/esfmu/esfm.c:1915:25: error: ‘asm’ operand has impossible constraints or there are not enough registers

Source: dosbox-x Version: 2025.02.01+dfsg-1 Severity: serious Justification: FTBFS Tags: trixie sid ftbfs User: lu...@debian.org Usertags: ftbfs-20250416 ftbfs-trixie Hi, During a rebuild of all packages in testing (trixie), your package failed to build on armhf. Relevant part (hopefully

Bug#1103377: java3d: FTBFS in testing/armel: [exec] /usr/bin/ld: cannot find -ljvm: No such file or directory

Source: java3d Version: 1.5.2+dfsg-18 Severity: serious Justification: FTBFS Tags: trixie sid ftbfs User: lu...@debian.org Usertags: ftbfs-20250416 ftbfs-trixie Hi, During a rebuild of all packages in testing (trixie), your package failed to build on armel. Relevant part (hopefully): > mak

Processed: Re: Bug#1103367: mdanalysis: FTBFS in testing/armhf: E: Build killed with signal TERM after 150 minutes of inactivity

Processing commands for cont...@bugs.debian.org: > retitle 1103367 FTBFS: autobuilder hangs Bug #1103367 [src:mdanalysis] mdanalysis: FTBFS in testing/armhf: E: Build killed with signal TERM after 150 minutes of inactivity Changed Bug title to 'FTBFS: autobuilder hangs' from 'mdanalysis: FTBFS in

Bug#1103367: mdanalysis: FTBFS in testing/armhf: E: Build killed with signal TERM after 150 minutes of inactivity

retitle 1103367 FTBFS: autobuilder hangs thanks Hello. Some additional notes about this bug: - I can also reproduce it (randomly) on amd64, so it's not armhf-specific. - The same reported effect also happens in the autopkgtests as reported here: https://bugs.debian.org/cgi-bin/bugreport.cgi?bu

Bug#1103373: rjava: FTBFS in testing/armel: configure: error: One or more Java configuration variables are not set.

Source: rjava Version: 1.0-11-1 Severity: serious Justification: FTBFS Tags: trixie sid ftbfs User: lu...@debian.org Usertags: ftbfs-20250416 ftbfs-trixie Hi, During a rebuild of all packages in testing (trixie), your package failed to build on armel. Relevant part (hopefully): > archi

Bug#1103375: libkolabxml: FTBFS in testing/armel: make[3]: *** [CMakeFiles/generate_bindings.dir/build.make:89: bindings/kolabformat.cxx] Error 132

Source: libkolabxml Version: 1.2.1-5 Severity: serious Justification: FTBFS Tags: trixie sid ftbfs User: lu...@debian.org Usertags: ftbfs-20250416 ftbfs-trixie Hi, During a rebuild of all packages in testing (trixie), your package failed to build on armel. Relevant part (hopefully): > mak

Bug#1103374: gfan: FTBFS in testing/armel: testsuite/0500MixedVolume FAILED!

Source: gfan Version: 0.7-2 Severity: serious Justification: FTBFS Tags: trixie sid ftbfs User: lu...@debian.org Usertags: ftbfs-20250416 ftbfs-trixie Hi, During a rebuild of all packages in testing (trixie), your package failed to build on armel. Relevant part (hopefully): > make[1]: Enter

Bug#1103372: freecontact: FTBFS in testing/armel: make[1]: *** [Makefile:475: all-recursive] Error 1

Source: freecontact Version: 1.0.21-14 Severity: serious Justification: FTBFS Tags: trixie sid ftbfs User: lu...@debian.org Usertags: ftbfs-20250416 ftbfs-trixie Hi, During a rebuild of all packages in testing (trixie), your package failed to build on armel. Relevant part (hopefully): > mak

Processed: affects 1102955

Processing commands for cont...@bugs.debian.org: > affects 1102955 src:kicad Bug #1102955 {Done: Scott Talbert } [python3-wxgtk4.0] kicad: FTBFS in testing: ImportError: /usr/lib/python3/dist-packages/wx/_core.cpython-313-x86_64-linux-gnu.so: undefined symbol: _ZN14wxTranslations27GetBestAvaila

Bug#1103367: mdanalysis: FTBFS in testing/armhf: E: Build killed with signal TERM after 150 minutes of inactivity

Source: mdanalysis Version: 2.9.0-1 Severity: serious Justification: FTBFS Tags: trixie sid ftbfs User: lu...@debian.org Usertags: ftbfs-20250416 ftbfs-trixie Hi, During a rebuild of all packages in testing (trixie), your package failed to build on armhf. Relevant part (hopefully): > testsu

Bug#1103371: fwupd: FTBFS in testing/armhf: ../plugins/modem-manager/fu-dfota-updater.c:165:71: error: passing argument 5 of ‘g_ascii_string_to_unsigned’ from incompatible pointer type [-Wincompatible

Source: fwupd Version: 2.0.8-1 Severity: serious Justification: FTBFS Tags: trixie sid ftbfs User: lu...@debian.org Usertags: ftbfs-20250416 ftbfs-trixie Hi, During a rebuild of all packages in testing (trixie), your package failed to build on armhf. Relevant part (hopefully): > cc -Iplug

Processed: golang-github-awslabs-soci-snapshotter: FTBFS with the unshare backend

Processing commands for cont...@bugs.debian.org: > retitle 1103361 golang-github-awslabs-soci-snapshotter: FTBFS with the > unshare backend Bug #1103361 [src:golang-github-awslabs-soci-snapshotter] golang-github-awslabs-soci-snapshotter: FTBFS in testing/arm64: dh_auto_test: error Changed Bug t

Bug#1103370: selint: FTBFS in testing/armhf: make[1]: *** [debian/rules:23: execute_after_dh_auto_test] Error 1

Source: selint Version: 1.5.1-1 Severity: serious Justification: FTBFS Tags: trixie sid ftbfs User: lu...@debian.org Usertags: ftbfs-20250416 ftbfs-trixie Hi, During a rebuild of all packages in testing (trixie), your package failed to build on armhf. Relevant part (hopefully): > mak

Bug#1103365: chirp GUI does not start, undefined symbol

Package: chirp Version: 1:20250221-1 Severity: grave Justification: renders package unusable kjotte@agamemnon:~$ chirpw Traceback (most recent call last): File "/usr/bin/chirpw", line 33, in sys.exit(load_entry_point('chirp==20250221', 'console_scripts', 'chirpw')()) ~~

Bug#1076350: nodejs: segfault in node when running browserify script on i386 when building node-chai

Package: nodejs Version: 20.19.0+dfsg-2 Followup-For: Bug #1076350 This is easy to reproduce with node-webfont: (sid_i386-dchroot)kapouer@barriere:~/node-webfont-11.4.0+dfsg2+~cs35.7.26/svgicons2svgfont$ gdb node GNU gdb (Debian 16.2-8) 16.2 Copyright (C) 2024 Free Software Foundation, Inc. Lice

Bug#1103362: python-msgspec: FTBFS in testing/arm64: make: *** [debian/rules:19: binary-arch] Error 25

Source: python-msgspec Version: 0.19.0-1 Severity: serious Justification: FTBFS Tags: trixie sid ftbfs User: lu...@debian.org Usertags: ftbfs-20250416 ftbfs-trixie Hi, During a rebuild of all packages in testing (trixie), your package failed to build on arm64. Relevant part (hopefully

Bug#1103363: openvdb: FTBFS in testing/arm64: make[3]: *** [openvdb_cmd/vdb_tool/CMakeFiles/vdb_tool.dir/build.make:82: openvdb_cmd/vdb_tool/CMakeFiles/vdb_tool.dir/src/main.cpp.o] Error 1

Source: openvdb Version: 10.0.1-2.3 Severity: serious Justification: FTBFS Tags: trixie sid ftbfs User: lu...@debian.org Usertags: ftbfs-20250416 ftbfs-trixie Hi, During a rebuild of all packages in testing (trixie), your package failed to build on arm64. Relevant part (hopefully): > mak

Bug#1103359: kicad: FTBFS in testing/arm64: ImportError: /usr/lib/python3/dist-packages/wx/_core.cpython-313-aarch64-linux-gnu.so: undefined symbol: _ZN14wxTranslations27GetBestAvailableTranslationERK

Source: kicad Version: 9.0.1+dfsg-1 Severity: serious Justification: FTBFS Tags: trixie sid ftbfs User: lu...@debian.org Usertags: ftbfs-20250416 ftbfs-trixie Hi, During a rebuild of all packages in testing (trixie), your package failed to build on arm64. Relevant part (hopefully): > mak

Bug#1103358: ceph: FTBFS in testing/arm64: c++: fatal error: Killed signal terminated program cc1plus

Source: ceph Version: 18.2.4+ds-13 Severity: serious Justification: FTBFS Tags: trixie sid ftbfs User: lu...@debian.org Usertags: ftbfs-20250416 ftbfs-trixie Hi, During a rebuild of all packages in testing (trixie), your package failed to build on arm64. Relevant part (hopefully): > mak

Processed: affects 1102761

Processing commands for cont...@bugs.debian.org: > affects 1102761 src:apache-log4j2 src:commons-configuration2 > src:apache-curator src:jackson-dataformat-yaml src:jruby-maven-plugins > src:jackson-jaxrs-providers src:jtreg7 src:libspring-java > src:logstash-logback-encoder src:resteasy src:te

Bug#1103356: surf autopkgtest "command 2" is flaky on riscv64

Package: surf Version: 2.1+git20240324-1 Severity: serious Justification: Preventing migrations in ci.d.n Hi. I'm working on src:autopkgtest. Currently, we're having a problem with testing migration because the 2nd listed autopkgtest is failing in ci.debian.net. That's the one with the command

Bug#1095360: marked as done (nghttp2: FTBFS: Could not import extension rubydomain.rubydomain)

Your message dated Wed, 16 Apr 2025 17:50:10 + with message-id and subject line Bug#1095360: fixed in nghttp2 1.64.0-1.1 has caused the Debian Bug report #1095360, regarding nghttp2: FTBFS: Could not import extension rubydomain.rubydomain to be marked as done. This means that you claim that t

Bug#1102955: marked as done (kicad: FTBFS in testing: ImportError: /usr/lib/python3/dist-packages/wx/_core.cpython-313-x86_64-linux-gnu.so: undefined symbol: _ZN14wxTranslations27GetBestAvailableTrans

Your message dated Wed, 16 Apr 2025 13:12:15 -0400 (EDT) with message-id and subject line Fixed in 4.2.3+dfsg-2 has caused the Debian Bug report #1102955, regarding kicad: FTBFS in testing: ImportError: /usr/lib/python3/dist-packages/wx/_core.cpython-313-x86_64-linux-gnu.so: undefined symbol: _Z

Bug#1101305: marked as done (libfuse3-4: regression in 3.17.1-1 for gvfsd-fuse: "both 'want' and 'want_ext' are set")

Your message dated Wed, 16 Apr 2025 17:20:04 + with message-id and subject line Bug#1101305: fixed in fuse3 3.17.1+git250416-1 has caused the Debian Bug report #1101305, regarding libfuse3-4: regression in 3.17.1-1 for gvfsd-fuse: "both 'want' and 'want_ext' are set" to be marked as done. Th

Processed: Re: Bug#1103345: Acknowledgement (golang-1.24-go: vgetrandom cleanup causes SIGSEGVs in programs using Go)

Processing commands for cont...@bugs.debian.org: > affects 1103345 + podman docker.io Bug #1103345 [golang-1.24-go] golang-1.24-go: vgetrandom cleanup causes SIGSEGVs in programs using Go Added indication that 1103345 affects podman and docker.io > thank you Stopping processing here. Please cont

Bug#1103352: dxvk: FTBFS on armhf and other non-x86 non-aarch64 architectures: #error "Unknown CPU Architecture"

Source: dxvk Version: 2.6.1-1 Severity: serious Tags: upstream ftbfs experimental Justification: built successfully in the past on armhf dxvk 2.6.1 with DXVK Native enabled doesn't build successfully on armhf: > c++ -Isrc/wsi/libwsi.a.p -Isrc/wsi -I../src/wsi -Iinclude -I../include > -I../includ

Bug#1103212: marked as done (flatbuffers: FTBFS: /usr/lib/python3/dist-packages/setuptools/dist.py:484: SetuptoolsDeprecationWarning: Pattern '../license' cannot contain '..')

Your message dated Wed, 16 Apr 2025 16:04:30 + with message-id and subject line Bug#1103212: fixed in flatbuffers 23.5.26+dfsg-4 has caused the Debian Bug report #1103212, regarding flatbuffers: FTBFS: /usr/lib/python3/dist-packages/setuptools/dist.py:484: SetuptoolsDeprecationWarning: Patte

Bug#1103348: jcal: Change the souce code repo

Package: jcal Version: 0.4.1-2.2 Severity: grave Tags: upstream l10n Justification: renders package unusable X-Debbugs-Cc: dani.be...@ubuntu.com Dear Maintainer, The package jcal is currently based on the code originally written by Ashkan Ghassemi (R.I.P.) who passed away in 2017. It now exhibits

Bug#1103300: rust-ring:FTBFS:build failed(abort: could not determine source-distribution conditions of build/ring-ea02091f2e9fc04e/out/libring_core_0_17_14__test.a）

The debdiff patch is in the attachment.I have tested that locally,and it works well.Please let me know whether this solution can be accepted. You seem to have totally ignored the existing built-using.patch and added a new patch, furthermore your new patch hardcodes the version number of ring, so

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

On Wed, Apr 16, 2025 at 12:50:13AM +0200, Lorenzo wrote: > > This system doesn't have a /dev/ttyS0, but that doesn't stop the > > getty-ttyS0 service from doing this: > > > > --- 8< --- > > [snip] > > > fi > > + pgrep -x agetty -t hvc0 > > + pgrep -x fgetty -t hvc0 > > > [snip] Ah, right. It

Bug#1103345: golang-1.24-go: vgetrandom cleanup causes SIGSEGVs in programs using Go

Package: golang-1.24-go Version: 1.24.2-1 Severity: grave Tags: upstream Justification: causes non-serious data loss Since the update to trixie on last Friday, we started experiencing random failures on both podman and docker.io either while pulling images, or while running containers. This is du

Bug#1102160: upgrade-reports: Bookworm to Trixie [amd64][EFI] initramfs unpacking failed invalid magic at start of compressed archive

ke 16.4.2025 klo 15.41 Pascal Hambourg (pas...@plouf.fr.eu.org) kirjoitti: > > On 16/04/2025 at 13:38, Martin-Éric Racine wrote: > > > > As the attached screenshot shows, 'fuseblk' seemingly doesn't know > > anything about the 'subvol' option for btrfs, which is what causes the > > failure to mount

Bug#1092673: nvidia-cuda-toolkit-gcc and gcc-13

The release notes for CUDA 12.8 mention support for GCC-13; maybe a new upstream release would help with this bug? https://docs.nvidia.com/cuda/cuda-toolkit-release-notes/index.html Roland.

Bug#1102779: marked as done (apktool: FTBFS: Could not resolve org.yaml:snakeyaml:1.x.)

Your message dated Wed, 16 Apr 2025 13:21:28 + with message-id and subject line Bug#1102761: fixed in snakeyaml 2.0+ds+really1.33-1 has caused the Debian Bug report #1102761, regarding apktool: FTBFS: Could not resolve org.yaml:snakeyaml:1.x. to be marked as done. This means that you claim th

Bug#1103193: marked as done (openhft-chronicle-wire: FTBFS: Could not resolve dependencies for project net.openhft:chronicle-wire:bundle:1.1.13)

Your message dated Wed, 16 Apr 2025 13:21:28 + with message-id and subject line Bug#1102761: fixed in snakeyaml 2.0+ds+really1.33-1 has caused the Debian Bug report #1102761, regarding openhft-chronicle-wire: FTBFS: Could not resolve dependencies for project net.openhft:chronicle-wire:bundle:

Bug#1103185: marked as done (clj-yaml-clojure: FTBFS: Cannot access central (https://repo1.maven.org/maven2/) in offline mode and the artifact org.yaml:snakeyaml:jar:1.x has not been downloaded from i

Your message dated Wed, 16 Apr 2025 13:21:28 + with message-id and subject line Bug#1102761: fixed in snakeyaml 2.0+ds+really1.33-1 has caused the Debian Bug report #1102761, regarding clj-yaml-clojure: FTBFS: Cannot access central (https://repo1.maven.org/maven2/) in offline mode and the art

Bug#1102773: marked as done (resteasy: FTBFS: Could not resolve dependencies for project org.jboss.resteasy:resteasy-yaml-provider:jar:3.6.2.Final)

Your message dated Wed, 16 Apr 2025 13:21:28 + with message-id and subject line Bug#1102761: fixed in snakeyaml 2.0+ds+really1.33-1 has caused the Debian Bug report #1102761, regarding resteasy: FTBFS: Could not resolve dependencies for project org.jboss.resteasy:resteasy-yaml-provider:jar:3.

Bug#1102777: marked as done (testng7: FTBFS: Could not find org.yaml:snakeyaml:1.33.)

Your message dated Wed, 16 Apr 2025 13:21:28 + with message-id and subject line Bug#1102761: fixed in snakeyaml 2.0+ds+really1.33-1 has caused the Debian Bug report #1102761, regarding testng7: FTBFS: Could not find org.yaml:snakeyaml:1.33. to be marked as done. This means that you claim that

Bug#1102778: marked as done (testng: FTBFS: [ERROR] dependency: org.yaml:snakeyaml:jar:1.x)

Your message dated Wed, 16 Apr 2025 13:21:28 + with message-id and subject line Bug#1102761: fixed in snakeyaml 2.0+ds+really1.33-1 has caused the Debian Bug report #1102761, regarding testng: FTBFS: [ERROR] dependency: org.yaml:snakeyaml:jar:1.x to be marked as done. This means that you clai

Bug#1102768: marked as done (libspring-java: FTBFS: Could not resolve org.yaml:snakeyaml:1.17.)

Your message dated Wed, 16 Apr 2025 13:21:28 + with message-id and subject line Bug#1102761: fixed in snakeyaml 2.0+ds+really1.33-1 has caused the Debian Bug report #1102761, regarding libspring-java: FTBFS: Could not resolve org.yaml:snakeyaml:1.17. to be marked as done. This means that you

Bug#1102769: marked as done (logstash-logback-encoder: FTBFS: Could not resolve dependencies for project net.logstash.logback:logstash-logback-encoder:jar:7.2)

Your message dated Wed, 16 Apr 2025 13:21:28 + with message-id and subject line Bug#1102761: fixed in snakeyaml 2.0+ds+really1.33-1 has caused the Debian Bug report #1102761, regarding logstash-logback-encoder: FTBFS: Could not resolve dependencies for project net.logstash.logback:logstash-lo

Bug#1102767: marked as done (jtreg7: FTBFS: Could not find org.yaml:snakeyaml:1.33.)

Your message dated Wed, 16 Apr 2025 13:21:28 + with message-id and subject line Bug#1102761: fixed in snakeyaml 2.0+ds+really1.33-1 has caused the Debian Bug report #1102761, regarding jtreg7: FTBFS: Could not find org.yaml:snakeyaml:1.33. to be marked as done. This means that you claim that

Bug#1102766: marked as done (jackson-jaxrs-providers: FTBFS: Could not resolve dependencies for project com.fasterxml.jackson.jaxrs:jackson-jaxrs-yaml-provider:bundle:2.12.1)

Your message dated Wed, 16 Apr 2025 13:21:28 + with message-id and subject line Bug#1102761: fixed in snakeyaml 2.0+ds+really1.33-1 has caused the Debian Bug report #1102761, regarding jackson-jaxrs-providers: FTBFS: Could not resolve dependencies for project com.fasterxml.jackson.jaxrs:jacks

Bug#1102764: marked as done (jackson-dataformat-yaml: FTBFS: Could not resolve dependencies for project com.fasterxml.jackson.dataformat:jackson-dataformat-yaml:bundle:2.8.11)

Your message dated Wed, 16 Apr 2025 13:21:28 + with message-id and subject line Bug#1102761: fixed in snakeyaml 2.0+ds+really1.33-1 has caused the Debian Bug report #1102761, regarding jackson-dataformat-yaml: FTBFS: Could not resolve dependencies for project com.fasterxml.jackson.dataformat:

Bug#1102765: marked as done (jruby-maven-plugins: FTBFS: Could not resolve dependencies for project org.jruby.maven:ruby-tools:jar:3.0.1)

Your message dated Wed, 16 Apr 2025 13:21:28 + with message-id and subject line Bug#1102761: fixed in snakeyaml 2.0+ds+really1.33-1 has caused the Debian Bug report #1102761, regarding jruby-maven-plugins: FTBFS: Could not resolve dependencies for project org.jruby.maven:ruby-tools:jar:3.0.1

Bug#1102763: marked as done (commons-configuration2: FTBFS: Could not resolve dependencies for project org.apache.commons:commons-configuration2:jar:2.11.0)

Your message dated Wed, 16 Apr 2025 13:21:28 + with message-id and subject line Bug#1102761: fixed in snakeyaml 2.0+ds+really1.33-1 has caused the Debian Bug report #1102761, regarding commons-configuration2: FTBFS: Could not resolve dependencies for project org.apache.commons:commons-config

Bug#1102761: marked as done (apache-log4j2: FTBFS: Could not resolve dependencies for project org.apache.logging.log4j:log4j-core:jar:2.19.0)

Your message dated Wed, 16 Apr 2025 13:21:28 + with message-id and subject line Bug#1102761: fixed in snakeyaml 2.0+ds+really1.33-1 has caused the Debian Bug report #1102761, regarding apache-log4j2: FTBFS: Could not resolve dependencies for project org.apache.logging.log4j:log4j-core:jar:2.1

  1   2   >