Bug#1104012: valkey: CVE-2025-21605

Source: valkey Version: 8.0.2+dfsg1-1 Severity: grave Tags: security upstream Forwarded: https://github.com/valkey-io/valkey/pull/1994 X-Debbugs-Cc: car...@debian.org, Debian Security Team Hi, The following vulnerability was published for valkey. CVE-2025-21605[0]: | Redis is an open source, in

Bug#1104010: redis: CVE-2025-21605

Source: redis Version: 5:7.0.15-3 Severity: grave Tags: security upstream Justification: user security hole X-Debbugs-Cc: car...@debian.org, Debian Security Team Control: found -1 5:7.0.15-1~deb12u3 Control: found -1 5:7.0.15-1 Hi, The following vulnerability was published for redis. CVE-2025-2

Bug#1103894: marked as done (RUSTSEC-2025-0020)

Your message dated Thu, 24 Apr 2025 06:50:16 + with message-id and subject line Bug#1103894: fixed in rust-pyo3 0.22.6-3 has caused the Debian Bug report #1103894, regarding RUSTSEC-2025-0020 to be marked as done. This means that you claim that the problem has been dealt with. If this is not

Bug#1104011: redict: CVE-2025-21605

Source: redict Version: 7.3.2+ds-1 Severity: grave Tags: security upstream X-Debbugs-Cc: car...@debian.org, Debian Security Team Hi, The following vulnerability was published for redict. CVE-2025-21605[0]: | Redis is an open source, in-memory database that persists on disk. | In versions starti

Processed: redis: CVE-2025-21605

Processing control commands: > found -1 5:7.0.15-1~deb12u3 Bug #1104010 [src:redis] redis: CVE-2025-21605 Marked as found in versions redis/5:7.0.15-1~deb12u3. > found -1 5:7.0.15-1 Bug #1104010 [src:redis] redis: CVE-2025-21605 Marked as found in versions redis/5:7.0.15-1. -- 1104010: https://b

Bug#1103423: src:kitty: fails to migrate to testing for too long: FTBFS on s390x

Hi, Looping in Pranav, On 24-04-2025 00:18, Chris Hofstaedtler wrote: * Nilesh Patra [250423 20:54]: Upstream has explicitly denied to provide any support for s390x see[1]. And I don't think I have the interest, time and energy to support a port this for big endian arch myself. That's OK.

Bug#1103906: qemu-efi-aarch64: Secure Boot regression for some arm64 VMs

On Wed, Apr 23, 2025, 17:41 Mathias Gibbens wrote: > control: retitle -1 qemu-efi-aarch64: Secure Boot regression for some > arm64 VMs > control: reassign -1 qemu-efi-aarch64 2025.02-7 > control: severity -1 serious > control: affects -1 incus > > Release 2025.02-5 of src:edk2 dropped the patch

Processed: your mail

Processing commands for cont...@bugs.debian.org: > tags 1103992 + pending Bug #1103992 [src:logcheck] logcheck: Could not run journalctl or save output Added tag(s) pending. > End of message, stopping processing here. Please contact me if you need assistance. -- 1103992: https://bugs.debian.org/

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

Processing control commands: > severity -1 important Bug #1103627 [src:openjdk-20] openjdk-20: Remove from Debian? Severity set to 'important' from 'serious' -- 1103627: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1103627 Debian Bug Tracking System Contact ow...@bugs.debian.org with proble

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

Control: severity -1 important On 19.04.25 20:58, Jeremy Bícha wrote: 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. OpenJ

Processed: qemu-efi-aarch64: Secure Boot regression for some arm64 VMs

Processing control commands: > retitle -1 qemu-efi-aarch64: Secure Boot regression for some arm64 VMs Bug #1103906 [incus] incus: can't get a shell on bookwork (debian/12) arm64 virtual machine Changed Bug title to 'qemu-efi-aarch64: Secure Boot regression for some arm64 VMs' from 'incus: can't

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

On Sat, 19 Apr 2025 15:08:13 +0530 Pirate Praveen wrote: > 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 > Revers

Bug#1102592: src:lsp-plugins: fails to migrate to testing for too long

Source: lsp-plugins Followup-For: Bug #1102592 X-Debbugs-Cc: noisyc...@tutanota.com, s...@debian.org Hi there, I think migration of lsp-plugins to testing is currently blocked because a removal from armel was not requested? Current excuses says: ``` - Migration status for lsp-plugins (1.2.16-1

Processed: Bug#1103018 marked as pending in ruby-rmagick

Processing control commands: > tag -1 pending Bug #1103018 [ruby-rmagick] ruby-rmagick fails to coinstall Added tag(s) pending. -- 1103018: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1103018 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems

Bug#1103018: marked as done (ruby-rmagick fails to coinstall)

Your message dated Wed, 23 Apr 2025 22:34:26 + with message-id and subject line Bug#1103018: fixed in ruby-rmagick 6.0.1-3 has caused the Debian Bug report #1103018, regarding ruby-rmagick fails to coinstall to be marked as done. This means that you claim that the problem has been dealt with.

Bug#1103018: marked as pending in ruby-rmagick

Control: tag -1 pending Hello, Bug #1103018 in ruby-rmagick 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/ruby-team/ruby-rmagick/-/commit/e715734c71543d73ecf2

Bug#1102386: scaphandre: FTBFS: [ERROR] (mdbook::utils): Caused By: Duplicate file in SUMMARY.md: "references/sensor-msr_rapl.md"

Source: scaphandre Followup-For: Bug #1102386 X-Debbugs-Cc: noisyc...@tutanota.com Control: tags -1 + patch Came across this while doing other work, you will find a patch in attachment. Cheers! mdbook-fix.patch Description: application/mbox

Bug#1103423: src:kitty: fails to migrate to testing for too long: FTBFS on s390x

* Nilesh Patra [250423 20:54]: Your package src:kitty has been trying to migrate for 31 days [2], hence this bug report. The current output of the migration software for this package is copied to the bottom of this report and should list the reason why the package is blocked. This migration is

Processed: Re: scaphandre: FTBFS: [ERROR] (mdbook::utils): Caused By: Duplicate file in SUMMARY.md: "references/sensor-msr_rapl.md"

Processing control commands: > tags -1 + patch Bug #1102386 [src:scaphandre] scaphandre: FTBFS: [ERROR] (mdbook::utils): Caused By: Duplicate file in SUMMARY.md: "references/sensor-msr_rapl.md" Added tag(s) patch. -- 1102386: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1102386 Debian B

Bug#1103200: marked as pending in r-bioc-rtracklayer

Control: tag -1 pending Hello, Bug #1103200 in r-bioc-rtracklayer 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/r-pkg-team/r-bioc-rtracklayer/-/commit/4edeaf6

Bug#1103086: marked as done (damo: FTBFS in testing/i386: make[1]: *** [debian/rules:43: override_dh_auto_test] Error 1)

Your message dated Wed, 23 Apr 2025 21:19:51 + with message-id and subject line Bug#1103086: fixed in damo 2.7.7-2 has caused the Debian Bug report #1103086, regarding damo: FTBFS in testing/i386: make[1]: *** [debian/rules:43: override_dh_auto_test] Error 1 to be marked as done. This means

Bug#1103901: marked as done (locales-all: Only locales with UTF-8 available)

Your message dated Wed, 23 Apr 2025 22:10:53 +0200 with message-id and subject line Re: Bug#1103901: locales-all: Only locales with UTF-8 available has caused the Debian Bug report #1103901, regarding locales-all: Only locales with UTF-8 available to be marked as done. This means that you claim t

Bug#1103992: logcheck: Could not run journalctl or save output

Source: logcheck Version: 1.4.3 Severity: serious On a fresh minimal trixie install, logcheck fails to read the systemd journal and exits with the following error: > Logcheck failed: Your log entries may not have been checked. > > Details: > Could not run journalctl or save output Adding th

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

Hi, sorry to bother again. Sadly the bugfix wasn't entirely OK. all-knowing-dns will terminate after 10 minutes because of a hardcoded (and unchangeable) timeout. This was work-arounded in https://github.com/all-knowing-dns/all-knowing-dns/pull/6 Just pulling this change isn't quite enough

Bug#1102958: Failure due to /tmp permissions

The tests are failing, because pdsh identities the module directory as insecure during the test run in the build environment. pdsh@sbuild: module path "/build/reproducible-path/pdsh-2.34/src/modules/.libs" insecure. pdsh@sbuild: "/tmp": Owner not root, current uid, or pdsh executable owner

Bug#1103423: src:kitty: fails to migrate to testing for too long: FTBFS on s390x

Hi Paul, On 17/04/25 4:20 pm, Paul Gevers wrote: > Source: kitty > Version: 0.39.1-1 > Severity: serious > Control: close -1 0.40.0-1 > Tags: sid trixie > User: release.debian@packages.debian.org > Usertags: out-of-sync > X-Debbugs-CC: debian-s...@lists.debian.org > User: debian-s...@lists.deb

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

Processing control commands: > tags -1 + patch Bug #980148 [mesa-vulkan-drivers] mesa-vulkan-drivers: file content conflict in Multi-Arch:same package Added tag(s) patch. -- 980148: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=980148 Debian Bug Tracking System Contact ow...@bugs.debian.org

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

Control: tags -1 + patch On Wed, 23 Apr 2025 at 15:59:00 +0100, Simon McVittie wrote: I think the "option 2" that I proposed is entirely feasible for trixie, actually. I'm testing an implementation now. https://salsa.debian.org/xorg-team/lib/mesa/-/merge_requests/55 works successfully on my I

Processed: Bug#1103200 marked as pending in r-bioc-rtracklayer

Processing control commands: > tag -1 pending Bug #1103200 [src:r-bioc-rtracklayer] r-bioc-rtracklayer: FTBFS: ucsc/common.c:249:9: error: too many arguments to function 'free' Added tag(s) pending. -- 1103200: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1103200 Debian Bug Tracking System

Bug#1103987: marked as done (rust-crossbeam-channel: RUSTSEC-2025-0024)

Your message dated Wed, 23 Apr 2025 18:17:39 + with message-id and subject line Bug#1103987: fixed in rust-crossbeam-channel 0.5.15-1 has caused the Debian Bug report #1103987, regarding rust-crossbeam-channel: RUSTSEC-2025-0024 to be marked as done. This means that you claim that the problem

Bug#1102746: marked as done (lomiri-docviewer-app: BD-Uninstallable on mips64el)

Your message dated Wed, 23 Apr 2025 20:14:01 +0200 with message-id and subject line Re: Bug#1102746: lomiri-docviewer-app: BD-Uninstallable on mips64el has caused the Debian Bug report #1102746, regarding lomiri-docviewer-app: BD-Uninstallable on mips64el to be marked as done. This means that yo

Processed: bug 1098720 is forwarded to https://github.com/processone/tsung/pull/409

Processing commands for cont...@bugs.debian.org: > forwarded 1098720 https://github.com/processone/tsung/pull/409 Bug #1098720 [src:tsung] tsung: Tsung uses functions removed in Erlang 27 Set Bug forwarded-to-address to 'https://github.com/processone/tsung/pull/409'. > thanks Stopping processing h

Processed: tagging 1098720

Processing commands for cont...@bugs.debian.org: > tags 1098720 - pending Bug #1098720 [src:tsung] tsung: Tsung uses functions removed in Erlang 27 Removed tag(s) pending. > thanks Stopping processing here. Please contact me if you need assistance. -- 1098720: https://bugs.debian.org/cgi-bin/bug

Bug#1103894: RUSTSEC-2025-0020

Source: rust-pyo3 Followup-For: Bug #1103894 X-Debbugs-Cc: noisyc...@tutanota.com Control: tags -1 + pending It looks like the fix [1] can be easily backported to v0.22, so we can avoid a transition to v0.24 late in the trixie freeze. Fixed in VCS, waiting for upload. Thanks! [1] https://github

Processed: Re: Bug#1102928: mpich: mpi-defaults autopkgtest regressions on 32-bit

Processing control commands: > clone 1102928 -2 Bug #1102928 [mpich] mpich: mpi-defaults autopkgtest regressions on 32-bit Bug 1102928 cloned as bug 1103991 > retitle 1102928 mpich: mpi-c.pc no longer available, causing mpi-defaults > autopkgtest regression Bug #1102928 [mpich] mpich: mpi-default

Bug#1102928: mpich: mpi-defaults autopkgtest regressions on 32-bit

Control: clone 1102928 -2 Control: retitle 1102928 mpich: mpi-c.pc no longer available, causing mpi-defaults autopkgtest regression Control: retitle -2 mpich: mpi-fort.pc no longer available, causing mpi-defaults autopkgtest regression On Wed, 23 Apr 2025 at 10:58:30 +0100, Alastair McKinstry w

Processed: Re: RUSTSEC-2025-0020

Processing control commands: > tags -1 + pending Bug #1103894 [src:rust-pyo3] RUSTSEC-2025-0020 Added tag(s) pending. -- 1103894: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1103894 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems

Bug#1103787: gpgme1.0: Testsuite error on 32bit archs with 64bit time (FAIL with gnupg 2.4, SKIP with 2.2)

On 2025-04-21 Andreas Metzler wrote: > Source: gpgme1.0 [...] > FAIL! : AddExistingSubkeyJobTest::testAddExistingSubkeyWithExpiration() > Compared values are not the same >Actual (result.code()) : 0 >Expected (static_cast(GPG_ERR_INV_TIME)): 161 >Loc: [../../../

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

Your message dated Wed, 23 Apr 2025 16:36:20 + with message-id and subject line Bug#1103362: fixed in python-msgspec 0.19.0-2 has caused the Debian Bug report #1103362, regarding python-msgspec: FTBFS in testing/arm64: make: *** [debian/rules:19: binary-arch] Error 25 to be marked as done. T

Processed: Re: rust-crossbeam-channel: RUSTSEC-2025-0024

Processing control commands: > tags -1 + pending Bug #1103987 [src:rust-crossbeam-channel] rust-crossbeam-channel: RUSTSEC-2025-0024 Added tag(s) pending. -- 1103987: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1103987 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems

Processed: reassign 1102704 to libg2c-dev

Processing commands for cont...@bugs.debian.org: > reassign 1102704 libg2c-dev 2.1.0-1 Bug #1102704 [libg2c-dev,liblapack-doc] libg2c-dev and liblapack-doc have an undeclared file conflict on /usr/share/man/man3/second.3.gz Bug reassigned from package 'libg2c-dev,liblapack-doc' to 'libg2c-dev'. I

Bug#1103987: rust-crossbeam-channel: RUSTSEC-2025-0024

Source: rust-crossbeam-channel Version: 0.5.14-1 Severity: grave Tags: upstream Forwarded: https://github.com/crossbeam-rs/crossbeam/pull/1187 X-Debbugs-Cc: car...@debian.org Hi See https://rustsec.org/advisories/RUSTSEC-2025-0024.html | crossbeam-channel: double free on Drop https://github.com

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

On Tue, 15 Apr 2025 at 16:52:56 +0200, Helmut Grohne wrote: On Tue, Apr 15, 2025 at 01:47:54PM +0100, Simon McVittie wrote: I think a regression for amd64/i386 co-installation would have a considerably larger practical negative impact on Debian users This reasoning convinces me. As it stands,

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

Hi Chris, Thanks for reporting this and I would love to look into this. I am actually working on a few other bugs as well. I will try to check this one in parallel. Please give me some time. Thanks, Pranav From: Chris Hofstaedtler Sent: Saturday, April 1

Bug#1102704: libg2c-dev and liblapack-doc have an undeclared file conflict on /usr/share/man/man3/second.3.gz

Agreed. Wil remove the conflict from libg2c-dev Alastair On 23/04/2025 14:49, Sébastien Villemot wrote: Le samedi 12 avril 2025 à 11:32 +0200, Helmut Grohne a écrit : Package: libg2c-dev,liblapack-doc Severity: serious User: debian...@lists.debian.org Usertags: fileconflict The file /usr/sh

Processed: severity 1103114 wishlist

Processing commands for cont...@bugs.debian.org: > severity 1103114 wishlist Bug #1103114 [src:cloudkitty] cloudkitty: FTBFS in testing/i386: OverflowError: timestamp out of range for platform time_t Severity set to 'wishlist' from 'serious' > End of message, stopping processing here. Please con

Bug#1102704: libg2c-dev and liblapack-doc have an undeclared file conflict on /usr/share/man/man3/second.3.gz

Le samedi 12 avril 2025 à 11:32 +0200, Helmut Grohne a écrit : > Package: libg2c-dev,liblapack-doc > Severity: serious > User: debian...@lists.debian.org > Usertags: fileconflict > > The file /usr/share/man/man3/second.3.gz is contained in the packages > * libg2c-dev/2.1.0-1 as present in trixie|

Bug#1103097: marked as done (seqan3: FTBFS in testing/i386: alphabet_base.hpp:56:24: error: static assertion failed: alphabet size must be >= 1)

Your message dated Wed, 23 Apr 2025 13:35:46 + with message-id and subject line Bug#1103097: fixed in seqan3 3.4.0~rc.3+ds-4 has caused the Debian Bug report #1103097, regarding seqan3: FTBFS in testing/i386: alphabet_base.hpp:56:24: error: static assertion failed: alphabet size must be >= 1

Bug#1103140: marked as done (python-momepy: FTBFS in testing/i386: tests failed)

Your message dated Wed, 23 Apr 2025 13:20:09 + with message-id and subject line Bug#1103140: fixed in python-momepy 0.8.1-2 has caused the Debian Bug report #1103140, regarding python-momepy: FTBFS in testing/i386: tests failed to be marked as done. This means that you claim that the problem

Bug#1103863: marked as done (openstack-meta-packages: Depends on unavailable ntp)

Your message dated Wed, 23 Apr 2025 13:19:33 + with message-id and subject line Bug#1103863: fixed in openstack-meta-packages 0.38 has caused the Debian Bug report #1103863, regarding openstack-meta-packages: Depends on unavailable ntp to be marked as done. This means that you claim that the

Processed: reintroduce

Processing commands for cont...@bugs.debian.org: > unarchive 996847 Bug #996847 {Done: Debian FTP Masters } [sysrepo-plugind] sysrepo-plugind fails to start Unarchived Bug 996847 > reopen 996847 Bug #996847 {Done: Debian FTP Masters } [sysrepo-plugind] sysrepo-plugind fails to start 'reopen' may

Processed: Bug#1103140 marked as pending in python-momepy

Processing control commands: > tag -1 pending Bug #1103140 [src:python-momepy] python-momepy: FTBFS in testing/i386: tests failed Added tag(s) pending. -- 1103140: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1103140 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems

Bug#1103140: marked as pending in python-momepy

Control: tag -1 pending Hello, Bug #1103140 in python-momepy 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/openstack-team/third-party/python-momepy/-/commit/f

Bug#1103863: marked as pending in openstack-meta-packages

Control: tag -1 pending Hello, Bug #1103863 in openstack-meta-packages 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/openstack-team/debian/openstack-meta-pack

Processed: Bug#1103863 marked as pending in openstack-meta-packages

Processing control commands: > tag -1 pending Bug #1103863 [src:openstack-meta-packages] openstack-meta-packages: Depends on unavailable ntp Ignoring request to alter tags of bug #1103863 to the same tags previously set -- 1103863: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1103863 Debia

Bug#1103863: marked as pending in openstack-meta-packages

Control: tag -1 pending Hello, Bug #1103863 in openstack-meta-packages 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/openstack-team/debian/openstack-meta-pack

Processed: Bug#1103863 marked as pending in openstack-meta-packages

Processing control commands: > tag -1 pending Bug #1103863 [src:openstack-meta-packages] openstack-meta-packages: Depends on unavailable ntp Added tag(s) pending. -- 1103863: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1103863 Debian Bug Tracking System Contact ow...@bugs.debian.org with

Bug#1103079: marked as done (exprtk: FTBFS in testing/i386: make[1]: *** [debian/rules:12: override_dh_auto_test] Error 1)

Your message dated Wed, 23 Apr 2025 12:19:03 + with message-id and subject line Bug#1103079: fixed in exprtk 0.0.3-3 has caused the Debian Bug report #1103079, regarding exprtk: FTBFS in testing/i386: make[1]: *** [debian/rules:12: override_dh_auto_test] Error 1 to be marked as done. This me

Bug#1094950: closed by Debian FTP Masters (reply to Simon Quigley ) (Bug#1094950: fixed in live-tasks 13.0.2.1)

Hi Jonathan, you uploaded live-tasks 13.0.3, seemingly discarding the 13.0.2.1 changelog. I haven't checked if the bug is now again unfixed... On Sun, Mar 02, 2025 at 06:06:04AM +, Debian Bug Tracking System wrote: > #1094950: live-task-extra: not installable due to missing dnsutils but at

Bug#1095381: marked as done (ruby-omniauth-auth0: FTBFS: Failure/Error: require 'multi_json')

Your message dated Wed, 23 Apr 2025 10:35:25 + with message-id and subject line Bug#1103485: Removed package(s) from unstable has caused the Debian Bug report #1095381, regarding ruby-omniauth-auth0: FTBFS: Failure/Error: require 'multi_json' to be marked as done. This means that you claim th

Bug#1099927: r-cran-testthat does not actually break other packages

In addition to the 3 packages mentioned here, there are 11-13 other R packages that are broken only on less common architectures; these are *not* blocking r-cran-testthat / r-base, but need to be dealt with (e.g. by partial removal) at some point if we want to keep them on amd64. https://bugs.

Processed: severity of 1101728 is serious

Processing commands for cont...@bugs.debian.org: > severity 1101728 serious Bug #1101728 [obs-studio] obs-studio: obs coredumps with message "double free or corruption (out)" when starting virtual camera Severity set to 'serious' from 'important' > thanks Stopping processing here. Please contact

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

Quick update: The function has been restored with a deprecation warning: https://github.com/ansible/ansible/pull/85032 So the beta2 should release today or tomorrow, fixing the autopkgtests of the other dependent packages (see https://lists.debian.org/debian-python/2025/04/msg00029.html).

Bug#1075076: marked as done (i2util: ftbfs with GCC-14)

Your message dated Wed, 23 Apr 2025 10:36:02 + with message-id and subject line Bug#1103656: Removed package(s) from unstable has caused the Debian Bug report #1075076, regarding i2util: ftbfs with GCC-14 to be marked as done. This means that you claim that the problem has been dealt with. If

Bug#1033111: marked as done (python-cmarkgfm: CVE-2023-22483 CVE-2023-22484 CVE-2023-22485 CVE-2023-22486)

Your message dated Wed, 23 Apr 2025 10:19:10 + with message-id and subject line Bug#1033111: fixed in python-cmarkgfm 2024.11.20-1 has caused the Debian Bug report #1033111, regarding python-cmarkgfm: CVE-2023-22483 CVE-2023-22484 CVE-2023-22485 CVE-2023-22486 to be marked as done. This mean

Bug#1103104: marked as done (nlohmann-json3: FTBFS in testing/i386: make[1]: *** [debian/rules:13: override_dh_auto_test] Error 2)

Your message dated Wed, 23 Apr 2025 10:04:33 + with message-id and subject line Bug#1103104: fixed in nlohmann-json3 3.11.3-2.1 has caused the Debian Bug report #1103104, regarding nlohmann-json3: FTBFS in testing/i386: make[1]: *** [debian/rules:13: override_dh_auto_test] Error 2 to be marke

Bug#1089694: mpich: autopkgtest regression

On Wed, 19 Mar 2025 at 18:10:34 -0100, Graham Inggs wrote: It seems the BTS considers that 4.3.0-2 will re-introduce this bug to testing because the changelog entry for 4.2.1-4 above was dropped from debian/changelog. As far as I can see, the BTS is correct: there are changes from 4.2.1-4 and 4

Processed: Bug#1033111 marked as pending in python-cmarkgfm

Processing control commands: > tag -1 pending Bug #1033111 [src:python-cmarkgfm] python-cmarkgfm: CVE-2023-22483 CVE-2023-22484 CVE-2023-22485 CVE-2023-22486 Added tag(s) pending. -- 1033111: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1033111 Debian Bug Tracking System Contact ow...@bugs

Bug#1101694: gjs: test failures on big-endian

Hi @Jeremy Bícha, Sorry, I was preoccupied with other concerns. Yeah, I can duplicate it from my end and observe the same issues. I'll try to provide more short updates since I've started debugging. Thanks, Gayathri. From: Jeremy Bícha Date: Saturday, 19 Apr

Bug#1102390: passenger: missing licenses

Hi Matheus, Your copyright version doe not distinguish the BSD-3-clause variants which I have in my proposed file. Also, your Rene-Nyffenegger license is actually the zlib license, so please refer to that instead of having an additional copy.

Bug#1102928: mpich: mpi-defaults autopkgtest regressions on 32-bit

On 23/04/2025 10:47, Simon McVittie wrote: On Sun, 13 Apr 2025 at 13:14:49 +0300, Adrian Bunk wrote: 214s autopkgtest [01:51:54]: test mpi-compile-run-cc-pkgconf-mpi-c: [--- 214s Package mpi-c was not found in the pkg-config search path. ... This is related to two lines

Bug#1033111: marked as pending in python-cmarkgfm

Control: tag -1 pending Hello, Bug #1033111 in python-cmarkgfm 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/python-cmarkgfm/-/commit/e0c

Processed: lowering severity

Processing control commands: > severity -1 important Bug #1098957 [src:openjdk-21] openjdk-21: Building openjdk on high memory systems fails with java.lang.OutOfMemoryError: Java heap space Severity set to 'important' from 'serious' -- 1098957: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=

Bug#1102928: mpich: mpi-defaults autopkgtest regressions on 32-bit

On Sun, 13 Apr 2025 at 13:14:49 +0300, Adrian Bunk wrote: 214s autopkgtest [01:51:54]: test mpi-compile-run-cc-pkgconf-mpi-c: [--- 214s Package mpi-c was not found in the pkg-config search path. ... This is related to two lines disappearing from the libmpich-dev postinst:

Bug#1098957: lowering severity

Control: severity -1 important I'm lowering the severity. I assume you're not interested in the zero variant, and the hotspot VM seems to build fine. Note, that 32bit support will be dropped for 25, so it's unlikely that you'll see a fix for that, unless you report that upstream yourself.

Bug#1103957: mbrola-en1: restricted use license, missing source

Ansgar, le mer. 23 avril 2025 07:46:30 +0200, a ecrit: > Package: mbrola-en1 > This looks non-free to me. Well, yes? € apt-cache show mbrola-en1 | grep Sect Section: non-free/sound Samuel

Bug#1091737: marked as done (ruby-rails-assets-underscore: FTBFS with ruby3.3: ERROR: Test "ruby3.3" failed.)

Your message dated Wed, 23 Apr 2025 09:38:44 + with message-id and subject line Bug#1103489: Removed package(s) from unstable has caused the Debian Bug report #1091737, regarding ruby-rails-assets-underscore: FTBFS with ruby3.3: ERROR: Test "ruby3.3" failed. to be marked as done. This means

Bug#1092701: marked as done (ruby-rails-assets-underscore: FTBFS with ruby3.3: ERROR: Test "ruby3.3" failed.)

Your message dated Wed, 23 Apr 2025 09:38:44 + with message-id and subject line Bug#1103489: Removed package(s) from unstable has caused the Debian Bug report #1092701, regarding ruby-rails-assets-underscore: FTBFS with ruby3.3: ERROR: Test "ruby3.3" failed. to be marked as done. This means

Bug#1065686: marked as done (golang-github-jackc-pgx: CVE-2024-27289)

Your message dated Wed, 23 Apr 2025 09:34:43 + with message-id and subject line Bug#1065686: fixed in golang-github-jackc-pgx 4.18.1-2 has caused the Debian Bug report #1065686, regarding golang-github-jackc-pgx: CVE-2024-27289 to be marked as done. This means that you claim that the problem

Bug#1103970: valgrind: FTBFS on 32-bit: Cannot find (any matches for) "usr/lib/*/valgrind/libmpiwrap*"

Source: valgrind Version: 1:3.24.0-3 Severity: serious Tags: ftbfs Justification: fails to build from source (but built successfully in the past) X-Debbugs-Cc: debian-...@lists.debian.org, debian-powe...@lists.debian.org, mp...@packages.debian.org User: debian-...@lists.debian.org Usertags: armhf

Bug#1103912: marked as done (provean: autopkgtest failures prevent testing migration)

Your message dated Wed, 23 Apr 2025 09:21:29 + with message-id and subject line Bug#1103912: fixed in provean 1.1.5+ds-5 has caused the Debian Bug report #1103912, regarding provean: autopkgtest failures prevent testing migration to be marked as done. This means that you claim that the proble

Bug#1103136: marked as done (etlcpp: FTBFS in testing/i386: test_atomic.cpp:326:37: error: useless cast to type ‘ptrdiff_t’ {aka ‘int’} [-Werror=useless-cast])

Your message dated Wed, 23 Apr 2025 09:04:30 + with message-id and subject line Bug#1103136: fixed in etlcpp 20.39.4+dfsg-3 has caused the Debian Bug report #1103136, regarding etlcpp: FTBFS in testing/i386: test_atomic.cpp:326:37: error: useless cast to type ‘ptrdiff_t’ {aka ‘int’} [-Werror=

Bug#1103966: undertow: should not be part of trixie

Source: undertow Version: 2.3.18-2 Severity: serious X-Debbugs-Cc: a...@debian.org undertow is a popular Java webserver and servlet engine but also regularly affected by security relevant issues which makes it difficult to maintain. As in previous years I recommend to remove undertow from the test

Bug#1103881: php-laravel-framework: CVE-2025-27515

On Tue, Apr 22, 2025 at 10:46:57PM +0200, Robin Gustafsson wrote: > Hi Moritz, > > Thanks for the report. > > On 4/22/25 14:09, Moritz Mühlenhoff wrote: > > [...] > > The following vulnerability was published for php-laravel-framework. > > > > CVE-2025-27515[0]: > > Thanks. I'll upload a fix fo