Bug#1103050: marked as done (fonts-culmus: Upgrade from bookworm fails: file conflict on /etc/fonts/conf.avail/65-culmus.conf)

Your message dated Mon, 05 May 2025 03:48:57 + with message-id and subject line Bug#1103050: fixed in culmus 0.140-3 has caused the Debian Bug report #1103050, regarding fonts-culmus: Upgrade from bookworm fails: file conflict on /etc/fonts/conf.avail/65-culmus.conf to be marked as done. Thi

Processed: bug 1101031 is forwarded to https://github.com/cctbx/dxtbx/pull/751

Processing commands for cont...@bugs.debian.org: > forwarded 1101031 https://github.com/cctbx/dxtbx/pull/751 Bug #1101031 [src:cctbx] cctbx: autopkgtest regression in testing Set Bug forwarded-to-address to 'https://github.com/cctbx/dxtbx/pull/751'. > thanks Stopping processing here. Please conta

Bug#1104514: screen: outputs some data to the main screen instead of the alternate screen

Control: retitle -1 screen: corrupts the main terminal screen after detach due to lack of utmp in systemd 257 On 2025-05-04 23:51:46 +0200, Vincent Lefevre wrote: > In short, the issue may be been introduced with the systemd upgrade > from 256.7-1 to 257.5-2 (the very old machine on which I do no

Processed: Re: screen: outputs some data to the main screen instead of the alternate screen

Processing control commands: > retitle -1 screen: corrupts the main terminal screen after detach due to lack > of utmp in systemd 257 Bug #1104514 [screen] screen: outputs some data to the main screen instead of the alternate screen Changed Bug title to 'screen: corrupts the main terminal screen

Bug#1104085: phpwebcounter: Does not work on PHP 8.4

Hi William, Thanks for reaching out. I confirm that I no longer wish to remain in the Maintainer field, as I’m currently too busy to properly maintain the package. It’s fine to keep the Debian QA Group as the maintainer. Thanks again for handling the updates! Best regards, Gilmar dos Reis Queir

Bug#1104706: qtorganizer-mkcal: FTBFS: FAIL! : tst_engine::testSimpleRangeRead() Compared values are not the same

Package: src:qtorganizer-mkcal Version: 0.1.0~git20250424.45906b1-1 Severity: serious Tags: ftbfs trixie sid Dear maintainer: During a rebuild of all packages in unstable, your package failed to build: [...] 1: PASS

Processed: re: winedbg recursively forks until the memory is exhausted

Processing control commands: > tag -1 moreinfo Bug #1104317 [wine] winedbg recursively forks until the memory is exhausted Ignoring request to alter tags of bug #1104317 to the same tags previously set -- 1104317: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1104317 Debian Bug Tracking Syst

Processed: re: winedbg recursively forks until the memory is exhausted

Processing control commands: > tag -1 moreinfo Bug #1104317 [wine] winedbg recursively forks until the memory is exhausted Added tag(s) moreinfo. -- 1104317: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1104317 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems

Bug#1104317: winedbg recursively forks until the memory is exhausted

control: tag -1 moreinfo Michael Krylov > Package: wine > Version: 10.0~repack-3 > Severity: critical > Justification: causes serious data loss I do not see this problem with 10.0~repack-3. Are you sure this wasn't with 10.0~rc2~repack-3? That was the first version built with binutils 2.44 tha

Processed: Re: Bug#1099530: libm4ri compiled with -mavx2, baseline violation

Processing control commands: > severity -1 serious Bug #1099530 [src:libm4ri] libm4ri compiled with -mavx2, baseline violation Severity set to 'serious' from 'important' > tags -1 ftbfs Bug #1099530 [src:libm4ri] libm4ri compiled with -mavx2, baseline violation Added tag(s) ftbfs. > affects -1 src

Bug#1104514: screen: outputs some data to the main screen instead of the alternate screen

On 2025-05-01 14:30:00 +0200, Vincent Lefevre wrote: > What's strange is that I think that I've never noticed this issue > before today, while it is now often reproducible. It could be Actually I'm not sure (see below). > related to some other upgrade on the system. I upgraded sys

Bug#1104704: rust-timerfd: FTBFS: signal: 11, SIGSEGV: invalid memory reference

Source: rust-timerfd Version: 1.5.0-1 Severity: serious Tags: ftbfs Hi, rust-timerfd fails to build from source on arm64, on my laptop and on reproduce.debian.net. Log from reproduce: https://reproduce.debian.net/arm64/api/v0/builds/176670/log Last log lines: running 7 tests test structs:

Bug#1104085: phpwebcounter: Does not work on PHP 8.4

Hi, Do you still want to be in the maintainer field? All the changes are ready in I changed the maintainer to the Debian QA group. Let me know if that needs to be reverted. -- William Desportes Le 4 mai 2025 23:03:49 GMT+02:00, GILMAR DOS REIS Que

Bug#1066488: marked as done (qrouter: FTBFS: qrouter.c:880:4: error: implicit declaration of function ‘find_free_antenna_taps’ [-Werror=implicit-function-declaration])

Your message dated Sun, 04 May 2025 21:17:06 + with message-id and subject line Bug#1066488: fixed in qrouter 1.4.88-1 has caused the Debian Bug report #1066488, regarding qrouter: FTBFS: qrouter.c:880:4: error: implicit declaration of function ‘find_free_antenna_taps’ [-Werror=implicit-funct

Bug#1104702: php-horde-css-parser: CVE-2020-13756 (in embeded Sabberworm CSS Parser)

Source: php-horde-css-parser Version: 1.0.11-8 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 php-horde-css-parser. CVE-2020-13756[0]: | Sabberworm PHP CSS Parser b

Bug#1104085: phpwebcounter: Does not work on PHP 8.4

Hello Eriberto, could you make an NMU for me? I am a bit busy now. Thanks.

Bug#1102539: libstdc++-riscv64-unknown-elf: diff for NMU version 4+nmu1

On Fri, Apr 11, 2025 at 02:08:17PM -0700, Keith Packard wrote: > > > It has the same problem: > > > dpkg: warning: while removing binutils-arm-none-eabi, directory > > '/usr/lib/arm-none-eabi' not empty so not removed > > Yup, but that's just a warning and not an install failure. Thanks for > t

Bug#1104685: marked as done (rescue: fails to migrate to testing: not built on buildd: arch all)

Your message dated Sun, 04 May 2025 20:47:04 + with message-id and subject line Bug#1104685: fixed in rescue 1.101 has caused the Debian Bug report #1104685, regarding rescue: fails to migrate to testing: not built on buildd: arch all to be marked as done. This means that you claim that the p

Bug#1104697: RFS: ruby-dbf 4.3.2-2

Control: tags -1 +pending The following packages are ready to be uploaded (I also verified the points listed on http://wiki.debian.org/Teams/Ruby/Packaging#Requesting_Sponsorship). I am opening this pull request to close the bug 1104697: https://salsa.debian.org/ruby-team/ruby-dbf/-/merge_request

Processed: RFS: ruby-dbf 4.3.2-2

Processing control commands: > tags -1 +pending Bug #1104697 [src:ruby-dbf] ruby-dbf: FTBFS caused by failure/Error: expect(record.name.encode('UTF-8').unpack1('H4')).to eq 'd0b0' Added tag(s) pending. -- 1104697: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1104697 Debian Bug Tracking Sys

Processed: Bug#1104685 marked as pending in rescue

Processing control commands: > tag -1 pending Bug #1104685 [src:rescue] rescue: fails to migrate to testing: not built on buildd: arch all Added tag(s) pending. -- 1104685: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1104685 Debian Bug Tracking System Contact ow...@bugs.debian.org with pr

Bug#1104685: marked as pending in rescue

Control: tag -1 pending Hello, Bug #1104685 in rescue 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/installer-team/rescue/-/commit/f382dc42d36a47e8625dc6b2614

Processed: Re: Bug#1104177: libc++-18-dev fails to coinstall

Processing control commands: > found -1 1:18.1.8-17 Bug #1104177 [libc++-18-dev,libunwind-18-dev,libc++abi1-18,libc++abi-18-dev,libunwind-18] libc++-18-dev fails to coinstall Marked as found in versions llvm-toolchain-18/1:18.1.8-17. -- 1104177: https://bugs.debian.org/cgi-bin/bugreport.cgi?bu

Bug#1104177: libc++-18-dev fails to coinstall

Control: found -1 1:18.1.8-17 On Sat, 26 Apr 2025 at 15:34:17 +0200, Helmut Grohne wrote: libc++-18-dev explicitly declares the ability to coinstall via Multi-Arch: same. Attempting to do this practically fails though. $ mmdebstrap --variant=essential --verbose unstable /dev/null --architectur

Bug#1102957: [Pkg-openssl-devel] Bug#1102957: geventhttpclient: FTBFS in testing: dh_auto_test: error: pybuild --test --test-pytest -i python{version} -p 3.13 returned exit code 13

On 2025-04-30 15:26:54 [+0200], Chris Hofstaedtler wrote: > Control: reassign -1 libssl3t64 > Control: affects -1 src:geventhttpclient … > Unsurprisingly this is caused by libssl. debbisect points to: > > bisection finished successfully > last good timestamp: 20250408T205804Z > first bad times

Bug#1104570: marked as done (usermetricsservice: preinst fails, calls adduser without Pre-Depend-ing on it)

Your message dated Sun, 04 May 2025 19:37:33 + with message-id and subject line Bug#1102247: fixed in libusermetrics 1.3.3-2 has caused the Debian Bug report #1102247, regarding usermetricsservice: preinst fails, calls adduser without Pre-Depend-ing on it to be marked as done. This means tha

Bug#1102247: marked as done (usermetricsservice: addgroup/user in preinst fails)

Your message dated Sun, 04 May 2025 19:37:33 + with message-id and subject line Bug#1102247: fixed in libusermetrics 1.3.3-2 has caused the Debian Bug report #1102247, regarding usermetricsservice: addgroup/user in preinst fails to be marked as done. This means that you claim that the problem

Processed: Bug#1102247 marked as pending in libusermetrics

Processing control commands: > tag -1 pending Bug #1102247 [usermetricsservice] usermetricsservice: addgroup/user in preinst fails Bug #1104570 [usermetricsservice] usermetricsservice: preinst fails, calls adduser without Pre-Depend-ing on it Added tag(s) pending. Added tag(s) pending. -- 1102

Bug#1102247: marked as pending in libusermetrics

Control: tag -1 pending Hello, Bug #1102247 in libusermetrics 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/ubports-team/libusermetrics/-/commit/5009deb99012b

Bug#1104697: ruby-dbf: FTBFS caused by failure/Error: expect(record.name.encode('UTF-8').unpack1('H4')).to eq 'd0b0'

Source: ruby-dbf Version: 4.3.2-1 Severity: serious Justification: FTBFS Tags: ftbfs patch User: debian-r...@lists.debian.org Usertags: ruby3.3 I've been testing a patch to fix this bug so that CI tests can run successfully again and make it reproducible again. The patch is quite simple and just a

Bug#1104360: marked as done (perlimports: FTBFS: dh_auto_test: error: make -j8 test TEST_VERBOSE=1 returned exit code 2)

Your message dated Sun, 04 May 2025 19:14:06 + with message-id and subject line Bug#1104360: fixed in perlimports 0.57-1 has caused the Debian Bug report #1104360, regarding perlimports: FTBFS: dh_auto_test: error: make -j8 test TEST_VERBOSE=1 returned exit code 2 to be marked as done. T

Bug#984982: marked as done (plexus-languages: Build-Depends on no longer available libsisu-maven-plugin-java)

Your message dated Sun, 4 May 2025 20:53:36 +0200 with message-id <7347xoeiogcnffhevmgtaztbsxshdlvelwnbdfy6wcrifbxlek@ymdplmfgyv53> and subject line Re: #984982: plexus-languages: Build-Depends on no longer available libsisu-maven-plugin-java has caused the Debian Bug report #984982, regarding pl

Processed: bug 1104360 is forwarded to https://github.com/perl-ide/App-perlimports/issues/121, tagging 1104360

Processing commands for cont...@bugs.debian.org: > forwarded 1104360 https://github.com/perl-ide/App-perlimports/issues/121 Bug #1104360 [src:perlimports] perlimports: FTBFS: dh_auto_test: error: make -j8 test TEST_VERBOSE=1 returned exit code 2 Set Bug forwarded-to-address to 'https://github.co

Bug#946206: marked as done (esys-particle: autopkgtest times out when module import fails)

Your message dated Sun, 04 May 2025 18:20:39 + with message-id and subject line Bug#946206: fixed in esys-particle 2.3.5+dfsg2-11 has caused the Debian Bug report #946206, regarding esys-particle: autopkgtest times out when module import fails to be marked as done. This means that you claim t

Bug#1038920: My steps to resolve this.

Having just hit this issue, here are some notes for anyone else in a hurry to fix it before their certificates expire: 1. I have a Gandi API token, which is deprecated but still works. I've not attempted to fix that yet. 2. I'm running Debian 12.10 with automatic updates. I currently have py

Bug#1070069: fossil: CVE-2024-24795 unreleated breakage

Hi, Attached is a debdiff for bookworm. I'd like to send a PU very soon (like, tomorrow) since the deadline for the next point release is next week-end Notes for the bookworm PU: Minimal backport of upstream changes, that make the HTTP client code a bit more robust. Later history of src/htt

Bug#1103559: reportbug: Gtk couldn't be initialized.

Hello Andrew, please send us a detailed description how you start reportbug. and more information how we can reproduce the problem. On Sat, 19 Apr 2025 13:12:37 +0930 and...@lists.savchenko.net wrote: Version: 13.1.0 Interestingly, `reportbug --configure` works just fine. Regards -- Mechti

Bug#1104578: jabber-muc: preinst fails, calls adduser without Pre-Depend-ing on it

Control: tags -1 patch On Fri, 2 May 2025 11:24:06 +0200 Chris Hofstaedtler wrote: You may consider replacing adduser with a sysusers fragment, see https://manpages.debian.org/unstable/debhelper/dh_installsysusers.1.en.html The following debdiff should fix this bug, but I have not tested it.

Processed: Re: jabber-muc: preinst fails, calls adduser without Pre-Depend-ing on it

Processing control commands: > tags -1 patch Bug #1104578 [jabber-muc] jabber-muc: preinst fails, calls adduser without Pre-Depend-ing on it Added tag(s) patch. -- 1104578: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1104578 Debian Bug Tracking System Contact ow...@bugs.debian.org with pr

Bug#1098555: marked as done (golang-github-go-fed-httpsig FTBFS with Go 1.24)

Your message dated Sun, 04 May 2025 16:19:38 + with message-id and subject line Bug#1098555: fixed in golang-github-go-fed-httpsig 1.1.0-3 has caused the Debian Bug report #1098555, regarding golang-github-go-fed-httpsig FTBFS with Go 1.24 to be marked as done. This means that you claim that

Processed: bug 1101238 is forwarded to https://github.com/lgi-devs/lgi/issues/336

Processing commands for cont...@bugs.debian.org: > forwarded 1101238 https://github.com/lgi-devs/lgi/issues/336 Bug #1101238 [src:lua-lgi] lua-lgi: FTBFS: tests/pango.lua:43: failure Set Bug forwarded-to-address to 'https://github.com/lgi-devs/lgi/issues/336'. > thanks Stopping processing here. P

Bug#1098555: marked as pending in golang-github-go-fed-httpsig

Control: tag -1 pending Hello, Bug #1098555 in golang-github-go-fed-httpsig 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/go-team/packages/golang-github-go-f

Bug#946206: Processed: notfound 1104325 in 2.3.5+dfsg2-10

Hi, * Santiago Vila [250504 18:08]: El 1/5/25 a las 14:19, Chris Hofstaedtler escribió: In my opinion, _both_ FoundationPy.so and libFoundationPy.so link to a python-version specific library (libboost_python313.so.1.83.0). Therefore, they shall NOT be installed into usr/lib/python3/dist-packag

Processed: Bug#1098555 marked as pending in golang-github-go-fed-httpsig

Processing control commands: > tag -1 pending Bug #1098555 [src:golang-github-go-fed-httpsig] golang-github-go-fed-httpsig FTBFS with Go 1.24 Added tag(s) pending. -- 1098555: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1098555 Debian Bug Tracking System Contact ow...@bugs.debian.org with

Bug#946206: Processed: notfound 1104325 in 2.3.5+dfsg2-10

El 1/5/25 a las 14:19, Chris Hofstaedtler escribió: In my opinion, _both_ FoundationPy.so and libFoundationPy.so link to a python-version specific library (libboost_python313.so.1.83.0). Therefore, they shall NOT be installed into usr/lib/python3/dist-packages, but into /usr/lib/python3.13/site-p

Bug#1082562: marked as done (dyssol: FTBFS build fails with sundials 7)

Your message dated Sun, 04 May 2025 16:05:16 + with message-id and subject line Bug#1082562: fixed in dyssol 1.4.0-1 has caused the Debian Bug report #1082562, regarding dyssol: FTBFS build fails with sundials 7 to be marked as done. This means that you claim that the problem has been dealt w

Bug#1100010: marked as done (schleuder: API daemon fails: undefined method `register' for module Rack::Handler (NoMethodError))

Your message dated Sun, 04 May 2025 15:52:46 + with message-id and subject line Bug#1100010: fixed in thin 1.8.2+git20250216.de6b618-1 has caused the Debian Bug report #1100010, regarding schleuder: API daemon fails: undefined method `register' for module Rack::Handler (NoMethodError) to be m

Bug#1104345: marked as done (autopkgtests fails preventing other packages migration)

Your message dated Sun, 04 May 2025 15:52:46 + with message-id and subject line Bug#1104345: fixed in thin 1.8.2+git20250216.de6b618-1 has caused the Debian Bug report #1104345, regarding autopkgtests fails preventing other packages migration to be marked as done. This means that you claim th

Bug#1104685: rescue: fails to migrate to testing: not built on buildd: arch all

Source: rescue Version: 1.100 Severity: serious Tags: sid trixie User: release.debian@packages.debian.org Usertags: out-of-sync X-Debbugs-CC: nstee...@gmail.com Hi, your upload of rescue 1.100 included arch:all binaries. The release policy is to forbid non-buildd-built binaries. This prob

Bug#1103129: marked as done (libbiosoup-dev: Installs arch dependent cmake files)

Your message dated Sun, 04 May 2025 15:49:52 + with message-id and subject line Bug#1103129: fixed in libbiosoup-dev 0.11.0-3 has caused the Debian Bug report #1103129, regarding libbiosoup-dev: Installs arch dependent cmake files to be marked as done. This means that you claim that the probl

Bug#1104151: marked as done (src:python-xarray: fails to migrate to testing for too long)

Your message dated Sun, 04 May 2025 15:38:37 + with message-id and subject line Bug#1104151: fixed in python-xarray 2025.03.1-5 has caused the Debian Bug report #1104151, regarding src:python-xarray: fails to migrate to testing for too long to be marked as done. This means that you claim that

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

Processing control commands: > retitle -1 libbiosoup-dev: Installs arch dependent cmake files Bug #1103129 [libbiosoup-dev] libbioparser-dev: FTBFS in testing/i386: make[1]: *** [debian/rules:11: override_dh_auto_configure] Error 2 Changed Bug title to 'libbiosoup-dev: Installs arch dependent cma

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

Control: retitle -1 libbiosoup-dev: Installs arch dependent cmake files This is because libbiosoup-dev has the following in its .cmake files: contents of /usr/lib/cmake/biosoup/biosoupConfigVersion.cmake 75 # if the installed or the using project don't have CMAKE_SIZEOF_VOID_P set, ignore it:

Processed: reassinging 1100010 and 1104345 to thin

Processing commands for cont...@bugs.debian.org: > reassign 1100010 src:thin Bug #1100010 [schleuder] schleuder: API daemon fails: undefined method `register' for module Rack::Handler (NoMethodError) Bug reassigned from package 'schleuder' to 'src:thin'. No longer marked as found in versions schl

Processed: reassign

Processing commands for cont...@bugs.debian.org: > reassign 1103129 libbiosoup-dev Bug #1103129 [src:libbioparser-dev] libbioparser-dev: FTBFS in testing/i386: make[1]: *** [debian/rules:11: override_dh_auto_configure] Error 2 Bug reassigned from package 'src:libbioparser-dev' to 'libbiosoup-dev'

Bug#1104273: rust-ureq: autopkgtests fail on all archs

On Sun, May 04, 2025 at 04:44:53PM +0200, Jonas Smedegaard wrote: > Quoting Chris Hofstaedtler (2025-05-04 14:06:37) > > thanks for your time at MiniDebConf. > > Likewise. Have you left by now, or do we have a chance of bumbing into > each other later tonight or at breakfast tomorrow as well? I'

Bug#1104653: marked as done (orange-spectroscopy: FTBFS: ERROR tests/test_xas.py - ValueError: Cannot parse dataset /<>/.pybuild/cpython3_3.13_orange-spectroscopy/build/orangecontrib/spec

Your message dated Sun, 04 May 2025 14:58:48 + with message-id and subject line Bug#1104653: fixed in orange-spectroscopy 0.8.1+git20250328-4 has caused the Debian Bug report #1104653, regarding orange-spectroscopy: FTBFS: ERROR tests/test_xas.py - ValueError: Cannot parse dataset /<>/.pybui

Bug#1104273: rust-ureq: autopkgtests fail on all archs

Quoting Chris Hofstaedtler (2025-05-04 14:06:37) > thanks for your time at MiniDebConf. Likewise. Have you left by now, or do we have a chance of bumbing into each other later tonight or at breakfast tomorrow as well? > On Mon, Apr 28, 2025 at 08:39:03AM +0200, Chris Hofstaedtler wrote: > > Sour

Bug#1088816: CVE-2025-27773 / #1100595 / Re: simplesamlphp 2.x for trixie? (Re: Bug#1088816: Current version not supported)

Hi Joost, If you'd like to test the simplesamlphp packages for bullsyes, I've prepared packages and placed them for your convenience here: https://people.debian.org/~tobi/simplesamlphp/ -- Cheers, tobi On Mon, 28 Apr 2025 13:50:24 + Tobias Frost wrote: > Hi Joost, >   > I've been wokin

Processed: raise severity

Processing control commands: > severity -1 grave Bug #1094257 [bluez] Do not start mpris-proxy for root user Severity set to 'grave' from 'important' > tag -1 + patch Bug #1094257 [bluez] Do not start mpris-proxy for root user Added tag(s) patch. -- 1094257: https://bugs.debian.org/cgi-bin/bugre

Bug#1104528: marked as done (scikit-build-core: FTBFS: E DeprecationWarning: The --no-wheel option is deprecated. It has no effect, wheel is no longer bundled in virtualenv. This option will be remove

Your message dated Sun, 04 May 2025 13:40:18 + with message-id and subject line Bug#1104528: fixed in scikit-build-core 0.11.1-2 has caused the Debian Bug report #1104528, regarding scikit-build-core: FTBFS: E DeprecationWarning: The --no-wheel option is deprecated. It has no effect, wheel is

Bug#1104671: marked as done (python3-zarr: fails on big-endian archs, causing xarray to break)

Your message dated Sun, 04 May 2025 13:10:03 + with message-id and subject line Bug#1104671: fixed in zarr 3.0.6-2 has caused the Debian Bug report #1104671, regarding python3-zarr: fails on big-endian archs, causing xarray to break to be marked as done. This means that you claim that the pro

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

Your message dated Sun, 4 May 2025 07:28:54 -0500 with message-id <26647.23942.462197.667...@rob.eddelbuettel.com> and subject line Re: Bug#1103373: rjava: FTBFS in testing/armel: configure: error: One or more Java configuration variables are not set. has caused the Debian Bug report #1103373, reg

Bug#1081879: marked as done (rust-safe-arch: FTBFS: error[E0425]: cannot find function `abs_i16_m256i` in this scope)

Your message dated Sun, 04 May 2025 12:30:16 + with message-id and subject line Bug#1081879: fixed in rust-safe-arch 0.7.4-2.1 has caused the Debian Bug report #1081879, regarding rust-safe-arch: FTBFS: error[E0425]: cannot find function `abs_i16_m256i` in this scope to be marked as done. Th

Processed: reopening 1104151, notfixed 1104151 in 2025.03.1-2

Processing commands for cont...@bugs.debian.org: > reopen 1104151 Bug #1104151 {Done: Paul Gevers } [src:python-xarray] src:python-xarray: fails to migrate to testing for too long 'reopen' may be inappropriate when a bug has been closed with a version; all fixed versions will be cleared, and you

Bug#1104273: rust-ureq: autopkgtests fail on all archs

Hi Jonas, thanks for your time at MiniDebConf. On Mon, Apr 28, 2025 at 08:39:03AM +0200, Chris Hofstaedtler wrote: > Source: rust-ureq > Your package's autopkgtests fail on all archs: [..] I re-checked, and rust-ureq has a _lot_ of reverse-dependencies, as can be seen here: https://codesearch.d

Bug#1104671: python3-zarr: fails on big-endian archs, causing xarray to break

Dear Julian, On Sun, 04 May 2025 11:30:18 +0100 Julian Gilbey wrote: Package: python3-zarr Version: 3.0.6-1 Severity: serious X-Debbugs-Cc: Antonio Valentino The python-xarray autopkgtest is failing on s390x, because the arch is big-endian and so the lookup for the dtype in from_numpy fails;

Bug#1101229: marked as done (indi-eqmod: FTBFS: /<>/ahpgtbase.cpp:218:73: error: too few arguments to function 'int ahp_gt_get_pwm_frequency(int)')

Your message dated Sun, 04 May 2025 11:34:34 + with message-id and subject line Bug#1101229: fixed in indi-eqmod 1.0+20230126190232-2 has caused the Debian Bug report #1101229, regarding indi-eqmod: FTBFS: /<>/ahpgtbase.cpp:218:73: error: too few arguments to function 'int ahp_gt_get_pwm_freq

Bug#1083254: marked as done (Removal notice: obsolete)

Your message dated Sun, 04 May 2025 11:10:35 + with message-id and subject line Bug#1104631: Removed package(s) from unstable has caused the Debian Bug report #1083254, regarding Removal notice: obsolete to be marked as done. This means that you claim that the problem has been dealt with. If

Processed: mpich pc

Processing commands for cont...@bugs.debian.org: > forwarded 1102928 https://github.com/pmodels/mpich/issues/6845 Bug #1102928 [mpich] mpich: mpi-c.pc no longer available, causing mpi-defaults autopkgtest regression Set Bug forwarded-to-address to 'https://github.com/pmodels/mpich/issues/6845'. >

Bug#1103205: marked as done (ruby-pry-byebug: FTBFS: ERROR: Test "ruby3.3" failed. Exiting.)

Your message dated Sun, 04 May 2025 11:09:17 + with message-id and subject line Bug#1104606: Removed package(s) from unstable has caused the Debian Bug report #1103205, regarding ruby-pry-byebug: FTBFS: ERROR: Test "ruby3.3" failed. Exiting. to be marked as done. This means that you claim tha

Bug#1102618: marked as done (ruby-pry-byebug: Does not install in unstable)

Your message dated Sun, 04 May 2025 11:09:17 + with message-id and subject line Bug#1104606: Removed package(s) from unstable has caused the Debian Bug report #1102618, regarding ruby-pry-byebug: Does not install in unstable to be marked as done. This means that you claim that the problem has

Bug#1104359: marked as done (ruby-android-key-attestation: FTBFS: unsatisfiable build-dependency: pry (< 0.15) but 0.15.2-1 is to be installed)

Your message dated Sun, 04 May 2025 11:08:50 + with message-id and subject line Bug#1104601: Removed package(s) from unstable has caused the Debian Bug report #1104359, regarding ruby-android-key-attestation: FTBFS: unsatisfiable build-dependency: pry (< 0.15) but 0.15.2-1 is to be installed

Bug#1075399: marked as done (psicode: ftbfs with GCC-14)

Your message dated Sun, 04 May 2025 11:07:39 + with message-id and subject line Bug#1104559: Removed package(s) from unstable has caused the Debian Bug report #1075399, regarding psicode: ftbfs with GCC-14 to be marked as done. This means that you claim that the problem has been dealt with. I

Bug#1104654: marked as done (litestar: FTBFS: E DeprecationWarning: Use of deprecated parameter 'random'.)

Your message dated Sun, 04 May 2025 10:49:48 + with message-id and subject line Bug#1104654: fixed in litestar 2.15.2-2 has caused the Debian Bug report #1104654, regarding litestar: FTBFS: E DeprecationWarning: Use of deprecated parameter 'random'. to be marked as done. This means that you

Bug#1104671: python3-zarr: fails on big-endian archs, causing xarray to break

Package: python3-zarr Version: 3.0.6-1 Severity: serious X-Debbugs-Cc: Antonio Valentino The python-xarray autopkgtest is failing on s390x, because the arch is big-endian and so the lookup for the dtype in from_numpy fails; zarr/core/metadata/v3.py only lists in dtype_to_data_type, for example, "

Processed: python-pyface: FTBFS in testing: AttributeError: partially initialized module 'wx' from '/usr/lib/python3/dist-packages/wx/__init__.py' has no attribute '__version__' (most likely due to a

Processing control commands: > severity -1 important Bug #1102963 [src:python-pyface] python-pyface: FTBFS in testing: AttributeError: partially initialized module 'wx' from '/usr/lib/python3/dist-packages/wx/__init__.py' has no attribute '__version__' (most likely due to a circular import) Sev

Bug#1102963: python-pyface: FTBFS in testing: AttributeError: partially initialized module 'wx' from '/usr/lib/python3/dist-packages/wx/__init__.py' has no attribute '__version__' (most likely due to

Control: severity -1 important I also can't reproduce the error, builds fine in clean and unclean environments. I tried with the latest (8.0.0) version. Since no one seems to be able to reproduce it, I am downgrading the severity to important to keep it non RC. If this is an actual error and someo

Processed: tagging 1103668

Processing commands for cont...@bugs.debian.org: > tags 1103668 + patch Bug #1103668 [whalebuilder] whalebuilder: Could not run Added tag(s) patch. > thanks Stopping processing here. Please contact me if you need assistance. -- 1103668: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1103668 D

Processed: Re: akregator: crashes due to package missing apparmor profile

Processing control commands: > severity -1 important Bug #1103882 [akregator] akregator: crashes due to package missing apparmor profile Severity set to 'important' from 'grave' -- 1103882: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1103882 Debian Bug Tracking System Contact ow...@bugs.d

Bug#1103882: akregator: crashes due to package missing apparmor profile

Control: severity -1 important Hi, On Tue, 22 Apr 2025 14:11:54 +0200 Karsten wrote: > Package: akregator > Version: 4:24.12.3-1 > Severity: grave > Justification: renders package unusable > X-Debbugs-Cc: fzu...@googlemail.com > > Dear Maintainer, > >* What led up to the situation? >

Bug#1104668: src:mimalloc: fails to migrate to testing for too long

Source: mimalloc Version: 3.0.1+ds-2.1 Severity: serious Control: close -1 3.0.3+ds-1 Tags: sid trixie User: release.debian@packages.debian.org Usertags: out-of-sync Control: block -1 by 1103589 Dear maintainer(s), The Release Team considers packages that are out-of-sync between testing and

Processed: src:mimalloc: fails to migrate to testing for too long

Processing control commands: > close -1 3.0.3+ds-1 Bug #1104668 [src:mimalloc] src:mimalloc: fails to migrate to testing for too long Marked as fixed in versions mimalloc/3.0.3+ds-1. Bug #1104668 [src:mimalloc] src:mimalloc: fails to migrate to testing for too long Marked Bug as done > block -1

Processed: fixed 1103726 in 2.4.1-1.1

Processing commands for cont...@bugs.debian.org: > fixed 1103726 2.4.1-1.1 Bug #1103726 {Done: devel } [src:klog] klog: FTBFS on many archs: type_trait:65:1: error: Parse error at "std" Marked as fixed in versions klog/2.4.1-1.1. > thanks Stopping processing here. Please contact me if you need a

Bug#1101052: src:systraq: fails to migrate to testing for too long

On Sun, May 04, 2025 at 08:56:47AM +0200, Paul Gevers wrote: > Hi Joost, > > This bug is causing systraq to be removed from testing in two days, before > the current version in unstable is ready to migrate. I'm pinging it for you > now, because it resets the autoremoval timer a bit, allowing the v

Bug#1104657: marked as done (skanpage: FTBFS: Could not find a configuration file for package "KSaneCore6" that is compatible with requested version "25.04".)

Your message dated Sun, 04 May 2025 07:40:12 + with message-id and subject line Bug#1104657: fixed in skanpage 25.04.0-2 has caused the Debian Bug report #1104657, regarding skanpage: FTBFS: Could not find a configuration file for package "KSaneCore6" that is compatible with requested version

Bug#1103668: whalebuilder: Could not run

Hi, I've prepared NMU fixing this issue and uploaded to archive with DELAY 2 days. Feel free to remove or upload another version. Debdiff attached. --abhijith diff -Nru whalebuilder-0.11/debian/changelog whalebuilder-0.11+nmu1/debian/changelog --- whalebuilder-0.11/debian/changelog 2024-01-31

Bug#1092440: patch for FTBFS with Python 3.13: error: implicit declaration of function '_PyImport_FixupExtensionObject'

Control: tags -1 + patch I can get the build succeed with this patch, but I am not entirely sure if that is the correct solution because I am not confident in my C skills. So if someone can give it a look and see if the patch is sane, it'd be nice. -- Best, Ananthu From: Ananthu C V Date: Sun,

Processed: patch for FTBFS with Python 3.13: error: implicit declaration of function '_PyImport_FixupExtensionObject'

Processing control commands: > tags -1 + patch Bug #1092440 [src:libapache2-mod-python] FTBFS with Python 3.13: error: implicit declaration of function '_PyImport_FixupExtensionObject' Added tag(s) patch. -- 1092440: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1092440 Debian Bug Tracking

Processed: Re: Bug#1104655: skanlite: FTBFS: Could not find a configuration file for package "KSaneWidgets6" that is compatible with requested version "25.04".

Processing control commands: > fixed -1 25.04.0-2 Bug #1104655 [src:skanlite] skanlite: FTBFS: Could not find a configuration file for package "KSaneWidgets6" that is compatible with requested version "25.04". The source 'skanlite' and version '25.04.0-2' do not appear to match any binary packa

Processed: Re: Bug#1104652: libksane: FTBFS: Could not find a configuration file for package "KSaneCore6" that is compatible with requested version "25.04".

Processing control commands: > fixed -1 25.04.0-2 Bug #1104652 [src:libksane] libksane: FTBFS: Could not find a configuration file for package "KSaneCore6" that is compatible with requested version "25.04". The source 'libksane' and version '25.04.0-2' do not appear to match any binary packages

Bug#1104652: marked as done (libksane: FTBFS: Could not find a configuration file for package "KSaneCore6" that is compatible with requested version "25.04".)

Your message dated Sun, 04 May 2025 09:18:33 +0200 with message-id <2783917.mvXUDI8C0e@grummly> and subject line Re: Bug#1104652: libksane: FTBFS: Could not find a configuration file for package "KSaneCore6" that is compatible with requested version "25.04". has caused the Debian Bug report #1104

Bug#1104655: marked as done (skanlite: FTBFS: Could not find a configuration file for package "KSaneWidgets6" that is compatible with requested version "25.04".)

Your message dated Sun, 04 May 2025 09:19:11 +0200 with message-id <5887480.DvuYhMxLoT@grummly> and subject line Re: Bug#1104655: skanlite: FTBFS: Could not find a configuration file for package "KSaneWidgets6" that is compatible with requested version "25.04". has caused the Debian Bug report #1

Processed: Re: Bug#1104655: skanlite: FTBFS: Could not find a configuration file for package "KSaneWidgets6" that is compatible with requested version "25.04".

Processing control commands: > fixed -1 25.04.0-2 Bug #1104655 [src:skanlite] skanlite: FTBFS: Could not find a configuration file for package "KSaneWidgets6" that is compatible with requested version "25.04". The source 'skanlite' and version '25.04.0-2' do not appear to match any binary packa

Bug#1104655: skanlite: FTBFS: Could not find a configuration file for package "KSaneWidgets6" that is compatible with requested version "25.04".

control: fixed -1 25.04.0-2

Processed: Re: Bug#1104652: libksane: FTBFS: Could not find a configuration file for package "KSaneCore6" that is compatible with requested version "25.04".

Processing control commands: > fixed -1 25.04.0-2 Bug #1104652 [src:libksane] libksane: FTBFS: Could not find a configuration file for package "KSaneCore6" that is compatible with requested version "25.04". The source 'libksane' and version '25.04.0-2' do not appear to match any binary packages

Bug#1104652: libksane: FTBFS: Could not find a configuration file for package "KSaneCore6" that is compatible with requested version "25.04".

control: fixed -1 25.04.0-2

Bug#1104494: marked as done (lib32stdc++-12-dev and libx32stdc++-12-dev have an undeclared file conflict on /usr/lib/gcc/x86_64-linux-gnu/12/libstdc++.so)

Your message dated Sun, 4 May 2025 09:01:26 +0200 with message-id <8f8c1c6a-011b-4671-a367-bb0c69450...@debian.org> and subject line fixed in 12.4.0-7 has caused the Debian Bug report #1104494, regarding lib32stdc++-12-dev and libx32stdc++-12-dev have an undeclared file conflict on /usr/lib/gcc/x8

Bug#1101052: src:systraq: fails to migrate to testing for too long

Hi Joost, This bug is causing systraq to be removed from testing in two days, before the current version in unstable is ready to migrate. I'm pinging it for you now, because it resets the autoremoval timer a bit, allowing the version in unstable to age. Paul OpenPGP_signature.asc Descripti