Processed: ansible-core removed ansible.parsing.utils.jsonify (impacting ansible-mitogen)

2025-04-19 Thread Debian Bug Tracking System
Processing control commands: > affects -1 + ansible-mitogen Bug #1103648 [src:ansible-core] ansible-core removed ansible.parsing.utils.jsonify (impacting ansible-mitogen) Added indication that 1103648 affects ansible-mitogen -- 1103648: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1103648

Bug#1103648: ansible-core removed ansible.parsing.utils.jsonify (impacting ansible-mitogen)

2025-04-19 Thread Salvatore Bonaccorso
Source: ansible-core Version: 2.19.0~beta1-2 Severity: serious Tags: upstream Justification: causes release regression in related strategy package Forwarded: https://github.com/ansible/ansible/issues/85017 X-Debbugs-Cc: car...@debian.org Control: affects -1 + ansible-mitogen Hi, With the recent u

Bug#1091504: marked as done (puppetdb: FTBFS in bookworm and trixie because of expired certificate)

2025-04-19 Thread Debian Bug Tracking System
Your message dated Sun, 20 Apr 2025 00:34:14 + with message-id and subject line Bug#1091504: fixed in puppetdb 8.4.1-4 has caused the Debian Bug report #1091504, regarding puppetdb: FTBFS in bookworm and trixie because of expired certificate to be marked as done. This means that you claim tha

Bug#1103630: marked as done (dh-python: 6.20250414 causes showtime to fail to build)

2025-04-19 Thread Debian Bug Tracking System
Your message dated Sun, 20 Apr 2025 00:04:31 + with message-id and subject line Bug#1103630: fixed in showtime 48.0-4 has caused the Debian Bug report #1103630, regarding dh-python: 6.20250414 causes showtime to fail to build to be marked as done. This means that you claim that the problem ha

Bug#1102581: marked as done (showtime: does not start)

2025-04-19 Thread Debian Bug Tracking System
Your message dated Sun, 20 Apr 2025 00:04:30 + with message-id and subject line Bug#1102581: fixed in showtime 48.0-4 has caused the Debian Bug report #1102581, regarding showtime: does not start to be marked as done. This means that you claim that the problem has been dealt with. If this is

Bug#1103645: persepolis: fails to build with dh-python 6.20250414

2025-04-19 Thread Jeremy Bícha
Source: persepolis Version: 5.0.2-1 Severity: serious Tags: ftbfs X-Debbugs-CC: by...@debian.org persepolis fails to build with dh-python 6.20250414 which is now in Unstable. See the similar https://bugs.debian.org/1103630 It appears like this failure is rare in Debian. These 2 are the only packa

Processed: Re: Bug#1103630: dh-python: 6.20250414 causes showtime to fail to build

2025-04-19 Thread Debian Bug Tracking System
Processing control commands: > reassign -1 src:showtime Bug #1103630 [src:dh-python] dh-python: 6.20250414 causes showtime to fail to build Bug reassigned from package 'src:dh-python' to 'src:showtime'. No longer marked as found in versions dh-python/6.20250414. Ignoring request to alter fixed ve

Processed: Re: Bug#1103630: dh-python: 6.20250414 causes showtime to fail to build

2025-04-19 Thread Debian Bug Tracking System
Processing control commands: > severity -1 normal Bug #1103630 [src:dh-python] dh-python: 6.20250414 causes showtime to fail to build Severity set to 'normal' from 'grave' -- 1103630: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1103630 Debian Bug Tracking System Contact ow...@bugs.debian.

Bug#1103630: dh-python: 6.20250414 causes showtime to fail to build

2025-04-19 Thread Stefano Rivera
Control: severity -1 normal Hi Jeremy (2025.04.19_19:40:44_+) I agree that that's a regression, but it doesn't seem to be a serious one. It's trying to edit a file, and for some reason that file wasn't writeable. I can make it force permissions to be writeable before fixing the file, an

Processed: Re: Bug#1102299: patchelf: FTBFS on mips64el

2025-04-19 Thread Debian Bug Tracking System
Processing control commands: > forwarded -1 https://github.com/NixOS/patchelf/issues/594 Bug #1102299 [src:patchelf] patchelf: FTBFS on mips64el Set Bug forwarded-to-address to 'https://github.com/NixOS/patchelf/issues/594'. -- 1102299: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1102299 D

Processed: dh-python: 6.20250414 causes showtime to fail to build

2025-04-19 Thread Debian Bug Tracking System
Processing control commands: > affects -1 src:showtime Bug #1103630 [src:dh-python] dh-python: 6.20250414 causes showtime to fail to build Added indication that 1103630 affects src:showtime -- 1103630: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1103630 Debian Bug Tracking System Contact

Processed: Re: Bug#1102299: patchelf: FTBFS on mips64el

2025-04-19 Thread Debian Bug Tracking System
Processing control commands: > tags -1 + unreproducible Bug #1102299 [src:patchelf] patchelf: FTBFS on mips64el Added tag(s) unreproducible. -- 1102299: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1102299 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems

Bug#1102299: patchelf: FTBFS on mips64el

2025-04-19 Thread Sergio Durigan Junior
Control: forwarded -1 https://github.com/NixOS/patchelf/issues/594 On Saturday, April 19 2025, I wrote: > On Saturday, April 19 2025, I wrote: > > I'll keep debugging it. And so I did. First of all, I've just uploaded patchelf 0.18.0-1.4 which will skip the failing test on mips64el, since I hav

Bug#1103636: kdeconnect does not work anymore after upgrade to trixie

2025-04-19 Thread Soren Stoutner
You might be up against the “trixie installs a firewall by default that blocks mDNS, which breaks KDE Connect and printing” problem. Which firewall packages do you have installed? -- Soren Stoutner so...@debian.org signature.asc Description: This is a digitally signed message part.

Bug#1103553: halide: FTBFS: The following tests FAILED: 345 - correctness_tiled_matmul (ILLEGAL) correctness

2025-04-19 Thread Santiago Vila
El 19/4/25 a las 20:32, Roman Lebedev escribió: The cpuinfo is attached. Right, so that CPU does claim to have AMX support. But is AMX supported in such a virtualized environment? https://community.intel.com/t5/Intel-Tiber-Developer-Cloud/Can-t-run-AMX-Instructions-on-Intel-Xeon-4th-Gen-Scalable

Bug#1103637: libeckit0d: Exception constructor ABI break affecting at least odc, magics++ and python-xarray

2025-04-19 Thread Martin Hostettler
Package: libeckit0d X-Debbugs-Cc: ghisv...@gmail.com Version: 1.29.1-1 Severity: serious Justification: Policy 8.1 Control: affects -1 odc magics++ python-xarray Control: block 1100293 by -1 While investigating a build failure in magics++ [1] i noticed that eckit upstream changed their exception c

Processed (with 3 errors): Debian bugs control

2025-04-19 Thread Debian Bug Tracking System
Processing commands for cont...@bugs.debian.org: > forwarded 1053485 https://jira.mariadb.org/browse/MDEV-36652 Bug #1053485 [src:mariadb] mariadb: FTBFS on sparc64: Post-build test suite fails on main.ctype_binary main.ctype_latin1 Set Bug forwarded-to-address to 'https://jira.mariadb.org/browse

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

2025-04-19 Thread Petter Reinholdtsen
I tried to reproduce this in my sid chroot on a machine running Debian Stable, but here it built just fine for amd64. Was this a problem in some other package which have since been fixed? When I try the same build in a testing/trixy chroot on a different machine, running testing, the build fail l

Processed: libeckit0d: Exception constructor ABI break affecting at least odc, magics++ and python-xarray

2025-04-19 Thread Debian Bug Tracking System
Processing control commands: > affects -1 odc magics++ python-xarray Bug #1103637 [libeckit0d] libeckit0d: Exception constructor ABI break affecting at least odc, magics++ and python-xarray Added indication that 1103637 affects odc, magics++, and python-xarray > block 1100293 by -1 Bug #1100293 {

Bug#1103636: kdeconnect does not work anymore after upgrade to trixie

2025-04-19 Thread Rainer Dorsch
Package: kdeconnect Version: 24.12.0-1+b1 Severity: grave Justification: renders package unusable Dear Maintainer, * What led up to the situation? Upgrade from bookworm to trixie * What exactly did you do (or not do) that was effective (or ineffective)? The mobile device does not s

Bug#1102299: patchelf: FTBFS on mips64el

2025-04-19 Thread Sergio Durigan Junior
On Saturday, April 19 2025, I wrote: > On Saturday, April 19 2025, Chris Hofstaedtler wrote: > >> On Sat, Apr 19, 2025 at 01:27:21PM +0200, Chris Hofstaedtler wrote: >>> On Sat, Apr 19, 2025 at 12:45:08AM -0400, Sergio Durigan Junior wrote: >>> > On Monday, April 07 2025, Graham Inggs wrote: >>> >

Bug#1091557: mariadb: FTBFS multiple archs: Post-build tests randomly fail on reserved port due to lacking builder isolation

2025-04-19 Thread Otto Kekäläinen
Forwarded: https://jira.mariadb.org/browse/MDEV-34788 Control: retitle -1 mariadb: FTBFS multiple archs: Post-build tests fail on reserved port In https://buildd.debian.org/status/fetch.php?pkg=mariadb&arch=amd64&ver=1%3A11.4.5-2%7Eexp1&stamp=1740281411&raw=0 these were passing: main.bind_addres

Processed: reopening 950372

2025-04-19 Thread Debian Bug Tracking System
Processing commands for cont...@bugs.debian.org: > reopen 950372 Bug #950372 {Done: Alex Myczko } [src:radare2] Is radare2 suitable for stable Debian releases? 'reopen' may be inappropriate when a bug has been closed with a version; all fixed versions will be cleared, and you may need to re-add t

Bug#1102595: python3-pytestqt: "Fatal Python error: Aborted" in many packages using python3-pytestqt

2025-04-19 Thread Soren Stoutner
I am the maintainer of electrum. It is scheduled to be removed from testing on May 24 because it transitively depends on python3-pytestqt. https://tracker.debian.org/pkg/electrum However, this bug doesn’t manifest for me. https://salsa.debian.org/cryptocoin-team/electrum/-/pipelines/849296 El

Processed: unarchiving 950372

2025-04-19 Thread Debian Bug Tracking System
Processing commands for cont...@bugs.debian.org: > unarchive 950372 Bug #950372 {Done: Alex Myczko } [src:radare2] Is radare2 suitable for stable Debian releases? Unarchived Bug 950372 > thanks Stopping processing here. Please contact me if you need assistance. -- 950372: https://bugs.debian.or

Processed: Re: Bug#1102581: showtime: does not start

2025-04-19 Thread Debian Bug Tracking System
Processing control commands: > severity -1 serious Bug #1102581 [showtime] showtime: does not start Severity set to 'serious' from 'important' -- 1102581: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1102581 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems

Bug#1103630: dh-python: 6.20250414 causes showtime to fail to build

2025-04-19 Thread Jeremy Bícha
Source: dh-python Version: 6.20250414 Severity: grave Tags: ftbfs sid Control: affects -1 src:showtime I can build the showtime package successfully in Trixie. If I then install the dh-python 6.20250414 packages in my sbuild with unshare, the build fails. The showtime packaging is very simple. Bu

Processed: mariadb: FTBFS multiple archs: Post-build tests randomly fail on reserved port due to lacking builder isolation

2025-04-19 Thread Debian Bug Tracking System
Processing control commands: > retitle -1 mariadb: FTBFS multiple archs: Post-build tests Bug #1091557 [src:mariadb] mariadb: FTBFS on i386: make[1]: *** [debian/rules:146: override_dh_auto_test] Error 1 Changed Bug title to 'mariadb: FTBFS multiple archs: Post-build tests' from 'mariadb: FTBFS

Bug#1103628: rust-gix-features: CVE-2025-31130 / RUSTSEC-2025-0021

2025-04-19 Thread Salvatore Bonaccorso
Source: rust-gix-features Version: 0.39.1-1 Severity: grave Tags: security upstream Justification: user security hole X-Debbugs-Cc: car...@debian.org, Debian Security Team Hi, The following vulnerability was published for rust-gix-features. CVE-2025-31130[0]: | gitoxide is an implementation of

Bug#1102299: patchelf: FTBFS on mips64el

2025-04-19 Thread Sergio Durigan Junior
Control: tags -1 + unreproducible On Saturday, April 19 2025, Chris Hofstaedtler wrote: > On Sat, Apr 19, 2025 at 01:27:21PM +0200, Chris Hofstaedtler wrote: >> On Sat, Apr 19, 2025 at 12:45:08AM -0400, Sergio Durigan Junior wrote: >> > On Monday, April 07 2025, Graham Inggs wrote: >> > > The rec

Bug#1103627: openjdk-20: Remove from Debian?

2025-04-19 Thread Jeremy Bícha
Source: openjdk-20 Version: 20.0.2+9-1 Severity: serious X-Debbugs-CC: d...@ubuntu.com Can we remove OpenJDK 20 from Debian now? It is only in Unstable. It is also not included in any currently supported Ubuntu release. OpenJDK 20 has reached End of Life. Thank you, Jeremy Bícha

Bug#1099751: orca: Orca captures all input when focus changes to firefox

2025-04-19 Thread Jeremy Bícha
> When the focus is set to Firefox, the "browse" mode is activated and seemingly > captures all key presses. Navigating the web site works, but any "normal" > action doesn't. This includes "Tab" in focus mode, but also pressing ctl+l to > jump to the address bar, pressing f10 to open the menu bar o

Bug#1103553: halide: FTBFS: The following tests FAILED: 345 - correctness_tiled_matmul (ILLEGAL) correctness

2025-04-19 Thread Roman Lebedev
On Sat, Apr 19, 2025 at 1:33 PM Santiago Vila wrote: > > El 19/4/25 a las 10:48, Roman Lebedev escribió: > > Does the bug reproduce if the whole build is rerun from scratch? > > I tried six times before reporting: > > Status: failed halide_19.0.0-6_amd64-20250418T100010.385Z > Status: failed

Bug#1103569: [Debian-med-packaging] Bug#1103569: src:orthanc-wsi: fails to migrate to testing for too long

2025-04-19 Thread Paul Gevers
Hi, In my previous reply I may have gotten some details wrong, as I hadn't read the bug about dcmtk yet. On 19-04-2025 20:01, Sébastien Jodogne wrote: If I read that other bug correctly, the changed path in dcmtk broke orthanc. So, the right binary package of src:dcmtk should declare that wit

Bug#1103569: [Debian-med-packaging] Bug#1103569: src:orthanc-wsi: fails to migrate to testing for too long

2025-04-19 Thread Sébastien Jodogne
Hi Paul, > > Unfortunately, I cannot find a clear guide about how I could fix this > > issue, as unstable has already accepted two new releases > > (orthanc-wsi_3.1+dfsg-1 and orthanc-wsi_3.2+dfsg-1) [2]. > > If I read that other bug correctly, the changed path in dcmtk broke > orthanc. So, the ri

Bug#1103577: FTBFS: breezy.tests.fixtures.TimeoutException: 6000

2025-04-19 Thread Jelmer Vernooij
Hi Chris, Is this repeatable or perhaps a flaky test? Cheers, Jelmer On Sat, Apr 19, 2025 at 12:42:27PM +0200, Chris Hofstaedtler wrote: Source: breezy Version: 3.3.11-1 Severity: serious Tags: ftbfs Justification: ftbfs X-Debbugs-Cc: debian-s...@lists.debian.org User: debian-s...@lists.debia

Bug#1102299: patchelf: FTBFS on mips64el

2025-04-19 Thread Chris Hofstaedtler
On Sat, Apr 19, 2025 at 01:27:21PM +0200, Chris Hofstaedtler wrote: > On Sat, Apr 19, 2025 at 12:45:08AM -0400, Sergio Durigan Junior wrote: > > On Monday, April 07 2025, Graham Inggs wrote: > > > The recent upload of patchelf 0.18.0-1.2 FTBFS on mips64el [1]. I've > > > copied what I hope is the

Bug#1102703: marked as done (libam7xxx0.1-bin has an undeclared file conflict on /usr/share/metainfo/it.ao2.libam7xxx.metainfo.xml)

2025-04-19 Thread Debian Bug Tracking System
Your message dated Sat, 19 Apr 2025 16:04:55 + with message-id and subject line Bug#1102703: fixed in libam7xxx 0.1.7-5 has caused the Debian Bug report #1102703, regarding libam7xxx0.1-bin has an undeclared file conflict on /usr/share/metainfo/it.ao2.libam7xxx.metainfo.xml to be marked as do

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

2025-04-19 Thread Paul Gevers
Hi Martin-Éric On 19-04-2025 10:19, Martin-Éric Racine wrote: And what do you expect from the Release Team? A simple question: Will the release team publish Trixie fully knowing that btrtfs hosts will no longer be bootable via UEFI? I hope you made a joke when you said "simple", because it

Processed: Re: naspro-bridges: FTBFS: /usr/include/alsa/seq_event.h:30:2: error: #warning "use #include , should not be used directly" [-Werror=cpp]

2025-04-19 Thread Debian Bug Tracking System
Processing control commands: > reassign -1 dssi-dev Bug #1103192 [src:naspro-bridges] naspro-bridges: FTBFS: /usr/include/alsa/seq_event.h:30:2: error: #warning "use #include , should not be used directly" [-Werror=cpp] Bug reassigned from package 'src:naspro-bridges' to 'dssi-dev'. No longer

Bug#1103192: naspro-bridges: FTBFS: /usr/include/alsa/seq_event.h:30:2: error: #warning "use #include , should not be used directly" [-Werror=cpp]

2025-04-19 Thread Petter Reinholdtsen
Control: reassign -1 dssi-dev Control: found -1 1.1.1~dfsg0-6 Control: affects -1 src:naspro-bridges Issue #1103192 is also reported as issue #1103187, and need to be fixed in dssi-dev. -- Happy hacking Petter Reinholdtsen

Bug#1103569: [Debian-med-packaging] Bug#1103569: src:orthanc-wsi: fails to migrate to testing for too long

2025-04-19 Thread Paul Gevers
Hi Sébastien, On 19-04-2025 10:48, Sébastien Jodogne wrote: This is a duplicate of #1103505 [1]. Close, but not really. That bug is about the failing test, which applies to unstable, this bug is about it not migrating, which is an RC bug against the version in testing. Unfortunately, I c

Bug#1102703: libam7xxx0.1-bin has an undeclared file conflict on /usr/share/metainfo/it.ao2.libam7xxx.metainfo.xml

2025-04-19 Thread Petter Reinholdtsen
I suspect the appropriate fix is to only provide this file from libam7xxx0.1-bin and drop it from libam7xxx0.1. -- Happy hacking Petter Reinholdtsen

Bug#1103548: marked as done (gnome-decoder: The program crashes on stratup)

2025-04-19 Thread Debian Bug Tracking System
Your message dated Sat, 19 Apr 2025 11:11:56 -0400 with message-id and subject line Re: gnome-decoder: The program crashes on stratup has caused the Debian Bug report #1103548, regarding gnome-decoder: The program crashes on stratup to be marked as done. This means that you claim that the proble

Bug#1092436: marked as done (hyprpaper: FTBFS: build-dependency not installable: libwlroots-dev)

2025-04-19 Thread Debian Bug Tracking System
Your message dated Sat, 19 Apr 2025 15:07:59 + with message-id and subject line Bug#1092436: fixed in hyprpaper 0.7.0-1.1 has caused the Debian Bug report #1092436, regarding hyprpaper: FTBFS: build-dependency not installable: libwlroots-dev to be marked as done. This means that you claim tha

Bug#1102951: libkate: FTBFS in testing: dh_install: error: missing files, aborting

2025-04-19 Thread Petter Reinholdtsen
Control: severity -1 important Lucas Nussbaum] > That version is not in testing yet according to > https://tracker.debian.org/pkg/python3-defaults I tried to reproduce this using the following script, but could not. Because of this, I reduce the severity until we can figure out what is going on h

Processed: Re: Bug#1102951: libkate: FTBFS in testing: dh_install: error: missing files, aborting

2025-04-19 Thread Debian Bug Tracking System
Processing control commands: > severity -1 important Bug #1102951 [src:libkate] libkate: FTBFS in testing: dh_install: error: missing files, aborting Severity set to 'important' from 'serious' -- 1102951: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1102951 Debian Bug Tracking System Conta

Bug#1102914: linux-image-6.1.0-33-amd64: Confirming issue with passing through LSI HBA controller

2025-04-19 Thread Salvatore Bonaccorso
Hi, On Sat, Apr 19, 2025 at 10:28:11AM -0400, Joshua Lee wrote: > Package: src:linux > Version: 6.1.133-1 > Followup-For: Bug #1102914 > > Dear Maintainer, > > >    * What led up to the situation? > >    I use a VM to handle my NAS and use PCIe passthrough to pass a HBA >    controller through to

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

2025-04-19 Thread Debian Bug Tracking System
Processing control commands: > forwarded -1 > https://git.libssh.org/projects/libssh.git/commit/?id=af10857aa3216f40c5c2e5d7116803fb03c166f9 Bug #1103224 [src:libssh] libssh: FTBFS: /<>/build-openssl/tests/tests_config.h:3:41: error: missing binary operator before token ".0p2" Set Bug forwarded

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

2025-04-19 Thread Chris Hofstaedtler
Control: forwarded -1 https://git.libssh.org/projects/libssh.git/commit/?id=af10857aa3216f40c5c2e5d7116803fb03c166f9 Control: tags -1 + upstream fixed-upstream On Tue, Apr 15, 2025 at 01:22:22AM +, Santiago Vila wrote: > /<>/build-openssl/tests/tests_config.h:3:41: error: missing > binary op

Bug#1075642: marked as done (wmdate: ftbfs with GCC-14)

2025-04-19 Thread Debian Bug Tracking System
Your message dated Sat, 19 Apr 2025 14:44:56 + with message-id and subject line Bug#1075642: fixed in wmdate 0.7-5 has caused the Debian Bug report #1075642, regarding wmdate: ftbfs with GCC-14 to be marked as done. This means that you claim that the problem has been dealt with. If this is no

Bug#1102914: linux-image-6.1.0-33-amd64: Confirming issue with passing through LSI HBA controller

2025-04-19 Thread Joshua Lee
Package: src:linux Version: 6.1.133-1 Followup-For: Bug #1102914 Dear Maintainer,    * What led up to the situation?    I use a VM to handle my NAS and use PCIe passthrough to pass a HBA    controller through to the VM, woke up today after an automagic    upgrade to lots of wonderful notificat

Processed: retitle 1076350 to Segfault with shared libuv on x86

2025-04-19 Thread Debian Bug Tracking System
Processing commands for cont...@bugs.debian.org: > retitle 1076350 Segfault with shared libuv on x86 Bug #1076350 [nodejs] nodejs: segfault in node when running browserify script on i386 when building node-chai Changed Bug title to 'Segfault with shared libuv on x86' from 'nodejs: segfault in no

Processed: bug 1076350 is forwarded to https://github.com/nodejs/node/issues/57934

2025-04-19 Thread Debian Bug Tracking System
Processing commands for cont...@bugs.debian.org: > forwarded 1076350 https://github.com/nodejs/node/issues/57934 Bug #1076350 [nodejs] nodejs: segfault in node when running browserify script on i386 when building node-chai Set Bug forwarded-to-address to 'https://github.com/nodejs/node/issues/579

Bug#1075457: marked as done (ruby-eb: ftbfs with GCC-14)

2025-04-19 Thread Debian Bug Tracking System
Your message dated Sat, 19 Apr 2025 13:35:17 + with message-id and subject line Bug#1075457: fixed in ruby-eb 2.6-4.1 has caused the Debian Bug report #1075457, regarding ruby-eb: ftbfs with GCC-14 to be marked as done. This means that you claim that the problem has been dealt with. If this i

Bug#1075457: ruby-eb: diff for NMU version 2.6-4.1

2025-04-19 Thread Chris Hofstaedtler
Control: tags 1075457 + patch Dear maintainer, I've prepared an NMU for ruby-eb (versioned as 2.6-4.1). The diff is attached to this message. Regards. diff -Nru ruby-eb-2.6/debian/changelog ruby-eb-2.6/debian/changelog --- ruby-eb-2.6/debian/changelog 2022-07-01 01:10:29.0 +0200 +++ ru

Processed: ruby-eb: diff for NMU version 2.6-4.1

2025-04-19 Thread Debian Bug Tracking System
Processing control commands: > tags 1075457 + patch Bug #1075457 [src:ruby-eb] ruby-eb: ftbfs with GCC-14 Added tag(s) patch. -- 1075457: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1075457 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems

Bug#1101090: marked as done (axc :FTBFS:build failed (error: ‘-fcf-protection=full’ is not supported for this target))

2025-04-19 Thread Debian Bug Tracking System
Your message dated Sat, 19 Apr 2025 13:04:30 + with message-id and subject line Bug#1101090: fixed in axc 0.3.7-2.1 has caused the Debian Bug report #1101090, regarding axc :FTBFS:build failed (error: ‘-fcf-protection=full’ is not supported for this target) to be marked as done. This means t

Bug#1103602: Depends: o-saft, to be removed

2025-04-19 Thread Chris Hofstaedtler
Source: forensics-all Version: 3.59 Severity: serious Your package currently Depends: o-saft, which is to be removed from trixie (#1102172). This is a serious bug, as your package will become uninstallable. It will thus also removed from trixie.

Bug#1101090: axc: diff for NMU version 0.3.7-2.1

2025-04-19 Thread Chris Hofstaedtler
Dear maintainer, I've prepared an NMU for axc (versioned as 0.3.7-2.1). The diff is attached to this message. Regards. diff -Nru axc-0.3.7/debian/changelog axc-0.3.7/debian/changelog --- axc-0.3.7/debian/changelog 2025-03-17 04:45:47.0 +0100 +++ axc-0.3.7/debian/changelog 2025-04-19 13:

Bug#1103599: rust-cargo-test-support: BD-Uninstallable on all archs

2025-04-19 Thread Chris Hofstaedtler
Source: rust-cargo-test-support Version: 0.3.0-1 Severity: serious Tags: ftbfs rust-cargo-test-support's build-depends are unavailable on all archs: rust-cargo-test-support build-depends on missing: - librust-git2-0.19+default-dev:amd64 rust-cargo-test-support build-depends on missing: - librus

Bug#1103598: rust-termwiz: BD-Uninstallable on all archs

2025-04-19 Thread Chris Hofstaedtler
Source: rust-termwiz Version: 0.22.0-2 Severity: serious Tags: ftbfs rust-termwiz build-depends on missing: - librust-finl-unicode-1+default-dev:amd64 (>= 1.2-~~) rust-termwiz build-depends on missing: - librust-finl-unicode-1+default-dev:arm64 (>= 1.2-~~) rust-termwiz build-depends on missing:

Bug#1103595: kitty: FTBFS on s390x: test failures

2025-04-19 Thread Chris Hofstaedtler
Source: kitty Version: 0.40.0-1 Severity: serious Tags: ftbfs User: debian-s...@lists.debian.org X-Debbugs-Cc: debian-s...@lists.debian.org Your package previously built on s390x but now fails with various test failures: https://buildd.debian.org/status/fetch.php?pkg=kitty&arch=s390x&ver=0.40.0-

Bug#1103594: octave-image: autopkgtest failure on all archs

2025-04-19 Thread Chris Hofstaedtler
Source: octave-image Version: 2.16.0-1 Severity: serious X-Debbugs-Cc: raf...@debian.org Your package currently fails its autopkgtests on all architectures. Note that this prevents testing migration. Example on amd64: https://ci.debian.net/data/autopkgtest/testing/amd64/o/octave-image/60157626/

Bug#1103593: python-djvulibre: autopkgtest regression on s390x

2025-04-19 Thread Chris Hofstaedtler
Source: python-djvulibre Version: 0.9.1-1 Severity: serious X-Debbugs-Cc: Colin Watson , debian-s...@lists.debian.org Your package python-djvulibre fails its autopkgtests on s390x: https://ci.debian.net/packages/p/python-djvulibre/testing/s390x/60156109/ PageJobsTestCase.test_decode ... 60s >

Bug#1103591: python-mastodon: autopktest regressions on i386, riscv64

2025-04-19 Thread Chris Hofstaedtler
Source: python-mastodon Version: 2.0.1-1 Severity: serious Your package fails its autopktests on i386 and riscv64, with different failures. i386: https://ci.debian.net/packages/p/python-mastodon/testing/i386/59129591/ test_entity_scheduledstatus 598s > isotime = datetime_val.astimezone(

Bug#1103592: faust: FTBFS on mips64el: dwz: Unknown debugging section .debug_addr causes some builds to fail

2025-04-19 Thread Chris Hofstaedtler
Source: faust Version: 2.79.3+ds-1 Severity: serious Tags: ftbfs Justification: ftbfs Your package FTBFS on mips64el because of the dwz bug #1016936. While its likely dwz's fault, your package is affected by it, and the dwz bug has not moved since November 2024. It seems necessary to apply a wo

Bug#1103590: ccache: autopkgtest regression on all archs

2025-04-19 Thread Chris Hofstaedtler
Source: ccache Version: 4.11.2-1 Severity: serious ccache's autopkgtests fail on all archs. This prevents testing migration. Example: https://ci.debian.net/packages/c/ccache/testing/amd64/60157589/ ... 105s Running test suite profiling_gcc_10+...test.c: warning: filename '/tmp/autopkgtest-lxc.

Processed: Re: chatty: Failed to launch app 'Discussions' on Librem5

2025-04-19 Thread Debian Bug Tracking System
Processing control commands: > severity 1103417 serious Bug #1103417 [chatty] chatty: Failed to launch app 'Discussions' on Librem5 Severity set to 'serious' from 'important' -- 1103417: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1103417 Debian Bug Tracking System Contact ow...@bugs.debia

Bug#1103589: mimalloc: FTBFS on armhf: cc1: error: ‘-mfloat-abi=hard’: selected architecture lacks an FPU

2025-04-19 Thread Chris Hofstaedtler
Source: mimalloc Version: 3.0.3+ds-1 Severity: serious Tags: ftbfs Justification: ftbfs X-Debbugs-Cc: debian-...@lists.debian.org User: debian-...@lists.debian.org Usertags: armhf Version 3.0.1+ds-2.1 built before, but 3.0.3+ds-1 fails: https://buildd.debian.org/status/fetch.php?pkg=mimalloc&arc

Bug#1086314: marked as done (ruby-timeliness: FTBFS: Failure/Error: expect(value).to eq Time.use_zone('Perth') { Time.zone.local(2000,6,1,18,0,0) })

2025-04-19 Thread Debian Bug Tracking System
Your message dated Sat, 19 Apr 2025 11:40:06 + with message-id and subject line Bug#1103492: Removed package(s) from unstable has caused the Debian Bug report #1086314, regarding ruby-timeliness: FTBFS: Failure/Error: expect(value).to eq Time.use_zone('Perth') { Time.zone.local(2000,6,1,18,0,

Bug#1103588: python-xiaomi-ble: autopktest failure on s390x: test_Xiaomi_MS1BB_MI_obj4a08 test_Xiaomi_HS1BB_illuminanca_and_motion test_Xiaomi_XMPIRO2SXS

2025-04-19 Thread Chris Hofstaedtler
Source: python-xiaomi-ble Version: 0.36.0-1 Severity: serious User: debian-s...@lists.debian.org Usertags: s390x python-xiaomi-ble autopktests fail on s390x: https://ci.debian.net/packages/p/python-xiaomi-ble/testing/s390x/59901553/ 39s === FAILURES

Bug#1094553: marked as done (ruby-warden: FTBFS: ERROR: Test "ruby3.3" failed: Failure/Error: app = setup_rack(app, :session => Rack::Session::Pool).to_app)

2025-04-19 Thread Debian Bug Tracking System
Your message dated Sat, 19 Apr 2025 11:38:53 + with message-id and subject line Bug#1103491: Removed package(s) from unstable has caused the Debian Bug report #1094553, regarding ruby-warden: FTBFS: ERROR: Test "ruby3.3" failed: Failure/Error: app = setup_rack(app, :session => Rack::Session::

Bug#1092700: marked as done (ruby-rails-assets-markdown-it-diaspora-mention: FTBFS with ruby3.3: ERROR: Test "ruby3.3" failed.)

2025-04-19 Thread Debian Bug Tracking System
Your message dated Sat, 19 Apr 2025 11:37:38 + with message-id and subject line Bug#1103488: Removed package(s) from unstable has caused the Debian Bug report #1092700, regarding ruby-rails-assets-markdown-it-diaspora-mention: FTBFS with ruby3.3: ERROR: Test "ruby3.3" failed. to be marked as

Bug#1094558: marked as done (ruby-rack-piwik: FTBFS: ERROR: Test "ruby3.3" failed.)

2025-04-19 Thread Debian Bug Tracking System
Your message dated Sat, 19 Apr 2025 11:36:09 + with message-id and subject line Bug#1103486: Removed package(s) from unstable has caused the Debian Bug report #1094558, regarding ruby-rack-piwik: FTBFS: ERROR: Test "ruby3.3" failed. to be marked as done. This means that you claim that the pro

Bug#1033914: marked as done (ruby-rails-assets-blueimp-gallery: autopkgtest regression: Don't know how to build task 'assets:precompile')

2025-04-19 Thread Debian Bug Tracking System
Your message dated Sat, 19 Apr 2025 11:36:59 + with message-id and subject line Bug#1103487: Removed package(s) from unstable has caused the Debian Bug report #1033914, regarding ruby-rails-assets-blueimp-gallery: autopkgtest regression: Don't know how to build task 'assets:precompile' to be

Bug#1076919: marked as done (ruby-influxdb: FTBFS: failing tests)

2025-04-19 Thread Debian Bug Tracking System
Your message dated Sat, 19 Apr 2025 11:34:57 + with message-id and subject line Bug#1103484: Removed package(s) from unstable has caused the Debian Bug report #1076919, regarding ruby-influxdb: FTBFS: failing tests to be marked as done. This means that you claim that the problem has been deal

Bug#1093921: marked as done (ruby-hipchat: FTBFS: Failure/Error: require 'mimemagic')

2025-04-19 Thread Debian Bug Tracking System
Your message dated Sat, 19 Apr 2025 11:34:25 + with message-id and subject line Bug#1103483: Removed package(s) from unstable has caused the Debian Bug report #1093921, regarding ruby-hipchat: FTBFS: Failure/Error: require 'mimemagic' to be marked as done. This means that you claim that the p

Bug#1091659: marked as done (ruby-grape: FTBFS with ruby3.3: ERROR: Test "ruby3.3" failed: expected NoMethodError with message matching /^undefined method `x' for #$/, go

2025-04-19 Thread Debian Bug Tracking System
Your message dated Sat, 19 Apr 2025 11:32:58 + with message-id and subject line Bug#1103436: Removed package(s) from unstable has caused the Debian Bug report #1091659, regarding ruby-grape: FTBFS with ruby3.3: ERROR: Test "ruby3.3" failed: expected NoMethodError with message matching

Processed: hyperkitty: autopkgtest regression with mistune 3.1.3-1

2025-04-19 Thread Debian Bug Tracking System
Processing control commands: > affects -1 src:mistune Bug #1103587 [src:hyperkitty] hyperkitty: autopkgtest regression with mistune 3.1.3-1 Added indication that 1103587 affects src:mistune -- 1103587: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1103587 Debian Bug Tracking System Contact

Bug#1103587: hyperkitty: autopkgtest regression with mistune 3.1.3-1

2025-04-19 Thread Chris Hofstaedtler
Source: hyperkitty Version: 1.3.12-3 Severity: serious X-Debbugs-Cc: mist...@packages.debian.org Control: affects -1 src:mistune hyperkitty's autopkgtests fail with mistune 3.1.3-1 on all archs. Example log: https://ci.debian.net/packages/h/hyperkitty/testing/amd64/60157623/ 338s ===

Bug#1092691: marked as done (ruby-cleanroom: FTBFS with ruby3.3: ERROR: Test "ruby3.3" failed: Failure/Error:)

2025-04-19 Thread Debian Bug Tracking System
Your message dated Sat, 19 Apr 2025 11:29:05 + with message-id and subject line Bug#1101902: Removed package(s) from unstable has caused the Debian Bug report #1092691, regarding ruby-cleanroom: FTBFS with ruby3.3: ERROR: Test "ruby3.3" failed: Failure/Error: to be marked as done. This

Bug#1092690: marked as done (ruby-api-pagination: FTBFS with ruby3.3: ERROR: Test "ruby3.3" failed: Failure/Error: expect(response.header['Per-Page']).to eq('6'))

2025-04-19 Thread Debian Bug Tracking System
Your message dated Sat, 19 Apr 2025 11:31:29 + with message-id and subject line Bug#1103433: Removed package(s) from unstable has caused the Debian Bug report #1092690, regarding ruby-api-pagination: FTBFS with ruby3.3: ERROR: Test "ruby3.3" failed: Failure/Error: expect(response.header[

Bug#1095365: closed by Debian FTP Masters (reply to Julien Plissonneau Duquène ) (Bug#1095365: fixed in pdfsam 4.3.4-2)

2025-04-19 Thread Chris Hofstaedtler
pdfsam is currently blocked by bouncycastle, which has got RC bug #1100227, and is waiting for the maintainer to respond to the patch.

Bug#1102299: patchelf: FTBFS on mips64el

2025-04-19 Thread Chris Hofstaedtler
On Sat, Apr 19, 2025 at 12:45:08AM -0400, Sergio Durigan Junior wrote: > user debian-rele...@lists.debian.org > usertags 1102299 + bsp-2025-04-brazil > thanks > > On Monday, April 07 2025, Graham Inggs wrote: > > > Hi Maintainer > > > > The recent upload of patchelf 0.18.0-1.2 FTBFS on mips64el [

Bug#1103582: virtualbox: CVE-2025-30712 CVE-2025-30719 CVE-2025-30725

2025-04-19 Thread Salvatore Bonaccorso
Source: virtualbox Version: 7.0.20-dfsg-1.2 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 virtualbox. CVE-2025-30712[0]: | Vulnerability in the Oracle VM Virtua

Bug#1103580: FTBFS: attempt to compute `16_usize - 24_usize`, which would overflow

2025-04-19 Thread Chris Hofstaedtler
Source: rust-libxml Version: 0.3.4-1 Severity: serious Tags: ftbfs Justification: ftbfs User: debian...@lists.debian.org Usertags: i386 0.3.3-1 built on i386, but 0.3.4-1 fails: https://buildd.debian.org/status/fetch.php?pkg=rust-libxml&arch=i386&ver=0.3.4-1&stamp=1744884797&raw=0 [libxml 0.3.4]

Bug#1103581: python-tz: autopkgtest regression: cannot stat 'pytz/tests': No such file or directory

2025-04-19 Thread Chris Hofstaedtler
Source: python-tz Version: 2025.2-1 Severity: serious python-tz's autopkgtests fail on all archs: https://ci.debian.net/packages/p/python-tz/testing/amd64/60158064/ 29s autopkgtest [22:21:50]: test unittest: cp -r pytz/tests "$AUTOPKGTEST_TMP" && cd "$AUTOPKGTEST_TMP" && rm -f tests/test_docs.

Processed: coot: autopkgtest regression: ImportError

2025-04-19 Thread Debian Bug Tracking System
Processing control commands: > affects -1 src:rdkit Bug #1103579 [src:coot] coot: autopkgtest regression: ImportError Added indication that 1103579 affects src:rdkit -- 1103579: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1103579 Debian Bug Tracking System Contact ow...@bugs.debian.org wit

Bug#1103579: coot: autopkgtest regression: ImportError

2025-04-19 Thread Chris Hofstaedtler
Source: coot Version: 1.1.15+dfsg-1 Severity: serious X-Debbugs-Cc: rd...@packages.debian.org Control: affects -1 src:rdkit coot's autopkgtests fail with rdkit 202503.1-2: https://ci.debian.net/packages/c/coot/testing/amd64/60162582/ 76s Traceback (most recent call last): 76s File "", line 1

Processed: found 1103504 in 1.12.7+dfsg-1

2025-04-19 Thread Debian Bug Tracking System
Processing commands for cont...@bugs.debian.org: > found 1103504 1.12.7+dfsg-1 Bug #1103504 [orthanc] orthanc: autopkgtest failure Marked as found in versions orthanc/1.12.7+dfsg-1. > thanks Stopping processing here. Please contact me if you need assistance. -- 1103504: https://bugs.debian.org/c

Bug#1094561: ruby-vcr: FTBFS: ERROR: Test "ruby3.3" failed: cannot load such file -- rack/handler/webrick

2025-04-19 Thread Pirate Praveen
On Sat, 19 Apr 2025 15:08:13 +0530 Pirate Praveen wrote: > > ruby-octokitReverse-Depends === * gitlab * ruby-github-pages-health-check * ruby-jekyll-gist * ruby-jekyll-github-metadata * ruby-licensee I could drop ruby-octokit/ruby-licensee dependency from gitlab and file rm for ru

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

2025-04-19 Thread Chris Hofstaedtler
On Wed, Apr 16, 2025 at 09:08:52PM +0200, Lucas Nussbaum wrote: > Source: selint > Version: 1.5.1-1 > Severity: serious > During a rebuild of all packages in testing (trixie), your package failed > to build on armhf. > Can now also be observed on the buildds: https://buildd.debian.org/status/log

Bug#1103577: FTBFS: breezy.tests.fixtures.TimeoutException: 6000

2025-04-19 Thread Chris Hofstaedtler
Source: breezy Version: 3.3.11-1 Severity: serious Tags: ftbfs Justification: ftbfs X-Debbugs-Cc: debian-s...@lists.debian.org User: debian-s...@lists.debian.org Usertags: s390 breezy FTBFS on the s390x buildds: https://buildd.debian.org/status/logs.php?pkg=breezy&ver=3.3.11-1&arch=s390x https://

Bug#1103553: halide: FTBFS: The following tests FAILED: 345 - correctness_tiled_matmul (ILLEGAL) correctness

2025-04-19 Thread Santiago Vila
El 19/4/25 a las 10:48, Roman Lebedev escribió: Does the bug reproduce if the whole build is rerun from scratch? I tried six times before reporting: Status: failed halide_19.0.0-6_amd64-20250418T100010.385Z Status: failed halide_19.0.0-6_amd64-20250418T100011.126Z Status: failed

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

2025-04-19 Thread Martin-Éric Racine
la 19.4.2025 klo 12.43 Pascal Hambourg (pas...@plouf.fr.eu.org) kirjoitti: > > On 19/04/2025 at 10:19, Martin-Éric Racine wrote: > > > > Will the release team publish Trixie fully knowing that btrtfs hosts > > will no longer be bootable via UEFI? > > Not all btrfs hosts are affected. A fresh UEFI t

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

2025-04-19 Thread Pascal Hambourg
On 19/04/2025 at 10:19, Martin-Éric Racine wrote: Will the release team publish Trixie fully knowing that btrtfs hosts will no longer be bootable via UEFI? Not all btrfs hosts are affected. A fresh UEFI trixie btrfs virtual machine boots fine on bookworm QEMU+OVMF. IIUC you wrote that trixie

Bug#1101340: mariadb-server-core: innodb_fatal_semaphore_wait_threshold was exceeded for dict_sys.latch.

2025-04-19 Thread Johnny ström
Well, I figured this might take a long time to get resolved. We had to revert the updates on the affected servers for now. We could do beta testing of new Debian packages before they are released, to see if the problem is resolved or not. Den 4/11/25 kl. 6:15 PM, skrev Otto Kekäläinen: I don't

Bug#1094561: ruby-vcr: FTBFS: ERROR: Test "ruby3.3" failed: cannot load such file -- rack/handler/webrick

2025-04-19 Thread Pirate Praveen
On Fri, 11 Apr 2025 14:24:34 +0200 Lucas Nussbaum wrote: > nanoc > ruby-coveralls > ruby-graphlient This is already removed from the archive. > ruby-html-proofer $ reverse-depends -b ruby-html-proofer Reverse-Testsuite-Triggers == * ruby-jekyll-multiple-languages R

Bug#1103418: openssh-server irregularly crashing since 10.0p1 upgrade

2025-04-19 Thread Liam Stitt
On Fri, 18 Apr 2025, Colin Watson wrote: Ugh, I didn't realize your password would show up in the backtrace! Sorry about that - please change it as soon as possible. Yeah, I caught that after I sent the message and already have. Ah well, it was overdue for rotation anyway. valid. Therefo

  1   2   >