Processed: Come on…

Processing commands for cont...@bugs.debian.org: > severity 1104721 wishlist Bug #1104721 [python3-ruff] ruff: ruff fails to run on Asahi Linux kernel (Apple M2) because jemalloc complains about page size Severity set to 'wishlist' from 'serious' > thanks Stopping processing here. Please contact

Bug#1104721: Come on…

severity 1104721 wishlist thanks Asahi linux kernel for apple m2 is not in debian, I don't see why this would be an RC bug. -- Salvo Tomaselli "Io non mi sento obbligato a credere che lo stesso Dio che ci ha dotato di senso, ragione ed intelletto intendesse che noi ne facessimo a meno."

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

Hi release team e.a., Pinging this bug in order to reset the autoremoval timer: systraq_20201231-5.dsc which fixes this bug (present in both unstable and testing) entered unstable at 2025-05-04. We currently have: https://qa.debian.org/excuses.php?package=systraq : "Too young, only 6 of 10 day

Bug#1105023: marked as done (forgejo-cli:FTBFS:build failed(Error: Permission denied (os error 13)))

Your message dated Sat, 10 May 2025 06:04:15 + with message-id and subject line Bug#1105023: fixed in forgejo-cli 0.3.0-3 has caused the Debian Bug report #1105023, regarding forgejo-cli:FTBFS:build failed(Error: Permission denied (os error 13)) to be marked as done. This means that you claim

Processed: Please do not create random wrong RC bugs

Processing commands for cont...@bugs.debian.org: > notfound 1104616 1.30-12 Bug #1104616 [mini-httpd] mini-httpd: CGI scripts do not emit logs, please backport fix Ignoring request to alter found versions of bug #1104616 to the same values previously set > severity 1104616 normal Bug #1104616 [m

Bug#1105023: forgejo-cli:FTBFS:build failed(Error: Permission denied (os error 13))

Hi Gui-Yue, On 5/10/25 06:55, Yue Gui wrote: The problem arises because `forgejo-cli` (specifically the `fj` binary) attempts to create a user-specific keys file (as indicated by `keys file not found, creating` and the error at `src/keys.rs:43:9`) when its `completion` subcommand is invoked.

Bug#1105023: forgejo-cli:FTBFS:build failed(Error: Permission denied (os error 13))

Source: forgejo-cli Version: 0.3.0-2 Severity: serious Tags: FTBFS, patch Dear forgejo-cli maintainer, The package forgejo-cli build failed on riscv64.The crucial buildd log below: ``` debian/rules execute_after_dh_auto_install make[1]: Entering directory '/build/reproducible-path/forgejo-cli-0

Bug#1096318: marked as done (pympress: Fails to start due to changes in Python 3 / GIR about iterable GObject)

Your message dated Sat, 10 May 2025 04:34:10 + with message-id and subject line Bug#1096318: fixed in pympress 1.8.5-4 has caused the Debian Bug report #1096318, regarding pympress: Fails to start due to changes in Python 3 / GIR about iterable GObject to be marked as done. This means that y

Bug#1096318: marked as pending in pympress

Control: tag -1 pending Hello, Bug #1096318 in pympress reported by you has been fixed in the Git repository and is awaiting an upload. You can see the commit message below and you can check the diff of the fix at: https://salsa.debian.org/python-team/packages/pympress/-/commit/b128496a5020d39bf

Processed: Bug#1096318 marked as pending in pympress

Processing control commands: > tag -1 pending Bug #1096318 [pympress] pympress: Fails to start due to changes in Python 3 / GIR about iterable GObject Added tag(s) pending. -- 1096318: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1096318 Debian Bug Tracking System Contact ow...@bugs.debian

Processed: Re: Bug#1096318: pympress: Fails to start due to changes in Python 3 / GIR about iterable GObject

Processing control commands: > tags -1 + patch Bug #1096318 [pympress] pympress: Fails to start due to changes in Python 3 / GIR about iterable GObject Added tag(s) patch. -- 1096318: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1096318 Debian Bug Tracking System Contact ow...@bugs.debian.

Bug#1096318: pympress: Fails to start due to changes in Python 3 / GIR about iterable GObject

Control: tags -1 + patch There is a one-line fix for this in the relevant upstream bug: https://github.com/Cimbali/pympress/issues/330 --- i/pympress/builder.py +++ w/pympress/builder.py @@ -76,7 +76,7 @@ class Builder(Gtk.Builder): Args: a_widget (:class:`~GObject.Object`

Processed: bug 1104846 is forwarded to https://github.com/mvertes/txt2man/issues/41

Processing commands for cont...@bugs.debian.org: > forwarded 1104846 https://github.com/mvertes/txt2man/issues/41 Bug #1104846 [txt2man] [:space:] instead of [[:space:]] annoys new gawk Set Bug forwarded-to-address to 'https://github.com/mvertes/txt2man/issues/41'. > thanks Stopping processing her

Bug#1104982: rust-graphene-sys FTBFS with the nocheck build profile

Source: rust-graphene-sys Version: 0.20.7-1 Severity: serious Tags: ftbfs rust-graphene-sys fails to build from source when enabling the nocheck build profile. A build ends as follows: debian/rules execute_before_dh_auto_build make[1]: Entering directory '/build/reproducible-path/rust-graphene

Processed: severity of 1093917 is serious, severity of 1093908 is serious

Processing commands for cont...@bugs.debian.org: > severity 1093917 serious Bug #1093917 [src:nvidia-graphics-drivers-tesla-535] nvidia-graphics-drivers-tesla-535: CVE-2024-0131, CVE-2024-0147, CVE-2024-0149, CVE-2024-0150 Severity set to 'serious' from 'important' > severity 1093908 serious Bug

Bug#1094257: mpris-proxy running as root

On 2025-05-09 10:25, Jeremy Bícha wrote: On Fri, May 9, 2025 at 11:27 AM Antonio Russo wrote: I'm tagging this bug as a security bug because it needlessly starts a process that should not be running as root. Have you sent your patch to the security contact at https://www.bluez.org/development

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

Your message dated Fri, 09 May 2025 09:18:58 + with message-id and subject line Bug#1104947: Removed package(s) from unstable has caused the Debian Bug report #1082351, regarding Removal notice: obsolete to be marked as done. This means that you claim that the problem has been dealt with. If

Bug#1103801: CVE-2024-40446: code injection vulnerability

On 09.05.25 11:52, Shang-Hung, Wan wrote: Hello Shang-Hung, as you've noticed I've took my web page offline: running a web server carrying a vulnerable cgi script is probably not the best idea. ;-) There is a comment [1] that stated that he contacted the author John, and he said version 1.75

Processed: fixed 1100595 in 1.19.0-1+deb11u2

Processing commands for cont...@bugs.debian.org: > fixed 1100595 1.19.0-1+deb11u2 Bug #1100595 [src:simplesamlphp] simplesamlphp: CVE-2025-27773 The source 'simplesamlphp' and version '1.19.0-1+deb11u2' do not appear to match any binary packages Marked as fixed in versions simplesamlphp/1.19.0-1+

Bug#1073665: marked as done (libreswan: move aliased files from / to /usr (DEP17))

Your message dated Fri, 09 May 2025 21:21:00 + with message-id and subject line Bug#1073665: fixed in libreswan 5.2-2.2 has caused the Debian Bug report #1073665, regarding libreswan: move aliased files from / to /usr (DEP17) to be marked as done. This means that you claim that the problem ha

Bug#1104010: marked as done (redis: CVE-2025-21605)

Your message dated Fri, 09 May 2025 21:06:02 + with message-id and subject line Bug#1104010: fixed in redis 5:7.0.15-3.1 has caused the Debian Bug report #1104010, regarding redis: CVE-2025-21605 to be marked as done. This means that you claim that the problem has been dealt with. If this is

Bug#1104872: python-django: CVE-2025-32873 -- Denial-of-service possibility in strip_tags()

Colin Watson wrote: > since upstream seems to have removed setup.py, you need > pybuild-plugin-pyproject now. I've done loads of those conversions > so let me know if you need help with it. Thanks, I'll have a poke in a bit and see how I get on. I should probably learn how this new Python build

Bug#1104846: rpma: FTBFS: src2man: errors found in the "/<>/src/include/librpma.h" file

On Fri, 9 May 2025 14:27:02 +0200 Santiago Vila wrote: > Thanks a lot for the bug tidy up. Yes, I agree with > everything you said. I'm just fixing the reassign > as it seems it didn't work. > > Joao Eriberto: Please read the full report here: > > https://bugs.debian.org/cgi-bin/bugreport.cgi?b

Bug#1103559: marked as done (reportbug: Gtk couldn't be initialized.)

Your message dated Sat, 10 May 2025 05:55:14 +0930 with message-id <52cbd394-633f-4348-a1e0-c7be0bec8...@lists.savchenko.net> and subject line Re: Bug#1103559: Info received (reportbug: Gtk couldn't be initialized.) has caused the Debian Bug report #1103559, regarding reportbug: Gtk couldn't be in

Bug#1105005: gimp: ZDI-CAN-26752

Source: gimp Version: 3.0.2-3 Severity: grave Tags: security upstream Justification: user security hole X-Debbugs-Cc: car...@debian.org, Debian Security Team Hi There is ZDI-CAN-26752 report (with no CVE assignment yet), reported upstream at https://gitlab.gnome.org/GNOME/gimp/-/issues/13910 Up

Bug#1104704: marked as done (rust-timerfd: FTBFS: signal: 11, SIGSEGV: invalid memory reference)

Your message dated Fri, 09 May 2025 18:20:16 + with message-id and subject line Bug#1104704: fixed in rust-rustix 0.38.37-2 has caused the Debian Bug report #1104704, regarding rust-timerfd: FTBFS: signal: 11, SIGSEGV: invalid memory reference to be marked as done. This means that you claim t

Processed: pending

Processing commands for cont...@bugs.debian.org: > tags 1104704 + pending Bug #1104704 [rust-rustix] rust-timerfd: FTBFS: signal: 11, SIGSEGV: invalid memory reference Added tag(s) pending. > End of message, stopping processing here. Please contact me if you need assistance. -- 1104704: https:/

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

Your message dated Fri, 09 May 2025 09:20:57 + with message-id and subject line Bug#1104951: Removed package(s) from unstable has caused the Debian Bug report #1082414, regarding Removal notice: obsolete to be marked as done. This means that you claim that the problem has been dealt with. If

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

Hi Joost, Defintily helps a lot, thanks for the testing! I've also set up a testing envioronment (two VMs, one as IDP, one as SP) and also tested the areas where the patch touch the code and I think everything is working fine, so I think the package is ready for LTS. I'll finish testing and add

Processed: mpris-proxy running as root

Processing control commands: > tag -1 security Bug #1094257 [bluez] Do not start mpris-proxy for root user Added tag(s) security. -- 1094257: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1094257 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems

Bug#1104988: autogen has an undeclared file conflict on /usr/share/aclocal/autoopts.m4

On 2025-05-09 Helmut Grohne wrote: > Package: autogen > Version: 1:5.19.96-3 > Severity: serious > User: debian...@lists.debian.org > Usertags: fileconflict > Control: affects -1 + libopts25-dev > autogen has an undeclared file conflict. This may result in an unpack > error from dpkg. > The file

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

Your message dated Fri, 09 May 2025 09:22:32 + with message-id and subject line Bug#1104954: Removed package(s) from unstable has caused the Debian Bug report #1083255, regarding Removal notice: obsolete to be marked as done. This means that you claim that the problem has been dealt with. If

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

Your message dated Fri, 09 May 2025 09:14:48 + with message-id and subject line Bug#1104938: Removed package(s) from unstable has caused the Debian Bug report #1081937, regarding Removal notice: obsolete to be marked as done. This means that you claim that the problem has been dealt with. If

Bug#1086653: marked as done (openvpn: FTBFS: FAIL: t_cltsrv.sh)

Your message dated Fri, 09 May 2025 16:32:09 + with message-id and subject line Bug#1086653: fixed in openvpn 2.6.3-1+deb12u3 has caused the Debian Bug report #1086653, regarding openvpn: FTBFS: FAIL: t_cltsrv.sh to be marked as done. This means that you claim that the problem has been dealt

Bug#1094257: mpris-proxy running as root

On Fri, May 9, 2025 at 11:27 AM Antonio Russo wrote: > I'm tagging this bug as a security bug because it needlessly > starts a process that should not be running as root. Have you sent your patch to the security contact at https://www.bluez.org/development/security-bugs/ yet? I wouldn't consider

Bug#1094257: mpris-proxy running as root

Control: tag -1 security Hello, I'm tagging this bug as a security bug because it needlessly starts a process that should not be running as root. Best, Antonio

Processed: closing 1104467

Processing commands for cont...@bugs.debian.org: > close 1104467 Bug #1104467 [raku-json-class,raku-license-spdx,raku-meta6,raku-test-meta] 4 packages have an undeclared file conflict on 6 files Marked Bug as done > thanks Stopping processing here. Please contact me if you need assistance. -- 1

Bug#1104467: closing 1104467

close 1104467 thanks This bug is fixed with the packages built with dh_raku >= 0.19

Bug#1104846: rpma: FTBFS: src2man: errors found in the "/<>/src/include/librpma.h" file

Control: reassing -1 txt2man Control: affects -1 src:rpma Control: retitle -1 [:space:] instead of [[:space:]] annoys new gawk On Wed, May 07, 2025 at 08:53:53AM +, Santiago Vila wrote: > Package: src:rpma > Severity: serious > Tags: ftbfs trixie sid > During a rebuild of all packages in unst

Bug#1104992: marked as done (openssh: _PATH_PASSWD_PROG define will change when rebuilt during trixie lifetime)

Your message dated Fri, 9 May 2025 14:27:17 +0100 with message-id and subject line Re: Bug#1104992: openssh: _PATH_PASSWD_PROG define will change when rebuilt during trixie lifetime has caused the Debian Bug report #1104992, regarding openssh: _PATH_PASSWD_PROG define will change when rebuilt dur

Bug#1104992: openssh: _PATH_PASSWD_PROG define will change when rebuilt during trixie lifetime

Source: openssh Version: 1:10.0p1-2 Severity: serious Hi, openssh's configure detects a value for _PATH_PASSWD_PROG. This relies on the `passwd` program being available at configure time. This is currently true on the Debian buildds running bookworm; their deboostrap installs passwd into the

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

Your message dated Fri, 09 May 2025 09:23:00 + with message-id and subject line Bug#1104955: Removed package(s) from unstable has caused the Debian Bug report #1082356, regarding Removal notice: obsolete to be marked as done. This means that you claim that the problem has been dealt with. If

Processed (with 1 error): fixed 1104992 in 1:10.0p1-5, severity of 1104992 is important

Processing commands for cont...@bugs.debian.org: > tags 1104992 pending Bug #1104992 [src:openssh] openssh: _PATH_PASSWD_PROG define will change when rebuilt during trixie lifetime Added tag(s) pending. > severity 1104992 important # probably irrelevant on PAM systems Unknown command or malforme

Bug#1104085: marked as done (phpwebcounter: Does not work on PHP 8.4)

Your message dated Fri, 09 May 2025 12:49:16 + with message-id and subject line Bug#1104085: fixed in phpwebcounter 1.0-6 has caused the Debian Bug report #1104085, regarding phpwebcounter: Does not work on PHP 8.4 to be marked as done. This means that you claim that the problem has been deal

Bug#1104986: rust-gdk4 FTBFS with the nocheck build profile

Source: rust-gdk4 Version: 0.9.6-1 Severity: serious Tags: ftbfs rust-gdk4 fails to build from source in unstable when enabling the nocheck build profile. A build ends as follows: debian/rules execute_before_dh_auto_build make[1]: Entering directory '/build/reproducible-path/rust-gdk4-0.9.6' c

Processed: [:space:] instead of [[:space:]] annoys new gawk

Processing commands for cont...@bugs.debian.org: > found 1104846 1.7.1-4 Bug #1104846 [txt2man] [:space:] instead of [[:space:]] annoys new gawk Marked as found in versions txt2man/1.7.1-4. > thanks Stopping processing here. Please contact me if you need assistance. -- 1104846: https://bugs.debi

Processed: Re: Bug#1104846: rpma: FTBFS: src2man: errors found in the "/<>/src/include/librpma.h" file

Processing commands for cont...@bugs.debian.org: > reassign 1104846 txt2man Bug #1104846 [src:rpma] [:space:] instead of [[:space:]] annoys new gawk Bug reassigned from package 'src:rpma' to 'txt2man'. No longer marked as found in versions rpma/1.3.0-2. Ignoring request to alter fixed versions of

Bug#1104846: rpma: FTBFS: src2man: errors found in the "/<>/src/include/librpma.h" file

reassign 1104846 txt2man thanks Thanks a lot for the bug tidy up. Yes, I agree with everything you said. I'm just fixing the reassign as it seems it didn't work. Joao Eriberto: Please read the full report here: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1104846 Thanks.

Processed (with 1 error): Re: Bug#1104846: rpma: FTBFS: src2man: errors found in the "/<>/src/include/librpma.h" file

Processing control commands: > reassing -1 txt2man Unknown command or malformed arguments to command. > affects -1 src:rpma Bug #1104846 [src:rpma] rpma: FTBFS: src2man: errors found in the "/<>/src/include/librpma.h" file Added indication that 1104846 affects src:rpma > retitle -1 [:space:] ins

Bug#1104988: autogen has an undeclared file conflict on /usr/share/aclocal/autoopts.m4

Package: autogen Version: 1:5.19.96-3 Severity: serious User: debian...@lists.debian.org Usertags: fileconflict Control: affects -1 + libopts25-dev autogen has an undeclared file conflict. This may result in an unpack error from dpkg. The file /usr/share/aclocal/autoopts.m4 is contained in the pa

Processed: autogen has an undeclared file conflict on /usr/share/aclocal/autoopts.m4

Processing control commands: > affects -1 + libopts25-dev Bug #1104988 [autogen] autogen has an undeclared file conflict on /usr/share/aclocal/autoopts.m4 Added indication that 1104988 affects libopts25-dev -- 1104988: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1104988 Debian Bug Trackin

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

Your message dated Fri, 09 May 2025 09:21:28 + with message-id and subject line Bug#1104952: Removed package(s) from unstable has caused the Debian Bug report #1082416, regarding Removal notice: obsolete to be marked as done. This means that you claim that the problem has been dealt with. If

Bug#1103801: CVE-2024-40446: code injection vulnerability

Hello Hilmar, Yes, version 1.74 is not affected because I think the vulnerable feature was added in 1.76. (or 1.75, I can’t find the source code of 1.75 so I can’t make sure of it) There is a comment [1] that stated that he contacted the author John, and he said version 1.75 in the source code

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

Hi Jeremy, I have submitted a merge request for the Regress test at https://gitlab.gnome.org/GNOME/gobject-introspection-tests/-/merge_requests/18 Thanks, Pranav From: Jeremy Bícha Sent: Tuesday, May 6, 2025 4:01 AM To: Pranav P Cc: Berli Gayathri; 1101.

Bug#1090361: marked as done (linux-headers-6.12.5-amd64: aptitude install fail)

Your message dated Fri, 09 May 2025 11:32:20 + with message-id and subject line Bug#1090361: fixed in nvidia-open-gpu-kernel-modules 535.247.01-1~deb12u1 has caused the Debian Bug report #1090361, regarding linux-headers-6.12.5-amd64: aptitude install fail to be marked as done. This means th

Bug#1104068: marked as done (nvidia-graphics-drivers: CVE-2025-23244)

Your message dated Fri, 09 May 2025 11:32:13 + with message-id and subject line Bug#1104068: fixed in nvidia-graphics-drivers 535.247.01-1~deb12u1 has caused the Debian Bug report #1104068, regarding nvidia-graphics-drivers: CVE-2025-23244 to be marked as done. This means that you claim that

Bug#1104076: marked as done (nvidia-open-gpu-kernel-modules: CVE-2025-23244)

Your message dated Fri, 09 May 2025 11:32:20 + with message-id and subject line Bug#1104076: fixed in nvidia-open-gpu-kernel-modules 535.247.01-1~deb12u1 has caused the Debian Bug report #1104076, regarding nvidia-open-gpu-kernel-modules: CVE-2025-23244 to be marked as done. This means that

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

Your message dated Fri, 09 May 2025 09:15:17 + with message-id and subject line Bug#1104940: Removed package(s) from unstable has caused the Debian Bug report #1081936, regarding Removal notice: obsolete to be marked as done. This means that you claim that the problem has been dealt with. If

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

Your message dated Fri, 09 May 2025 09:17:21 + with message-id and subject line Bug#1104944: Removed package(s) from unstable has caused the Debian Bug report #1082349, regarding Removal notice: obsolete to be marked as done. This means that you claim that the problem has been dealt with. If

Bug#1103503: isc-dhcp-client: In /etc/apparmor.d/local, sbin.dhclient should be renamed to usr.sbin.dhclient for consistency

On 2025-04-22 13:01:02 +0200, Vincent Lefevre wrote: > > I suppose it makes apparmor.service fail to start? > > No, I don't see any error with apparmor.service (and the documentation > does not suggest that there would be a fatal error for that). It actually fails to start (I had forgotten to res

Bug#1092732: marked as done (fail2ban fails to start without python3-setuptools installed)

Your message dated Fri, 09 May 2025 10:39:14 + with message-id and subject line Bug#1104790: fixed in fail2ban 1.1.0-8 has caused the Debian Bug report #1104790, regarding fail2ban fails to start without python3-setuptools installed to be marked as done. This means that you claim that the pro

Bug#1104790: marked as done (fail2ban crashes on startup in trixie (no module named distutils?))

Your message dated Fri, 09 May 2025 10:39:14 + with message-id and subject line Bug#1104790: fixed in fail2ban 1.1.0-8 has caused the Debian Bug report #1104790, regarding fail2ban crashes on startup in trixie (no module named distutils?) to be marked as done. This means that you claim that t

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

Your message dated Fri, 09 May 2025 09:20:26 + with message-id and subject line Bug#1104950: Removed package(s) from unstable has caused the Debian Bug report #1082411, regarding Removal notice: obsolete to be marked as done. This means that you claim that the problem has been dealt with. If

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

Your message dated Fri, 09 May 2025 09:13:45 + with message-id and subject line Bug#1104935: Removed package(s) from unstable has caused the Debian Bug report #1082344, regarding Removal notice: obsolete to be marked as done. This means that you claim that the problem has been dealt with. If

Bug#1051986: fixed in scalapack 2.2.1-3

This bug has definitely not been fixed. Here is a simple reproducer for Debian bookworm: # apt install cmake libscalapack-mpi-dev # cat

Bug#1104872: python-django: CVE-2025-32873 -- Denial-of-service possibility in strip_tags()

On Thu, May 08, 2025 at 11:02:01AM -0700, Chris Lamb wrote: Hi Colin, I noticed you apparently tried to upload 3:4.2.21-1 for this yesterday (judging from git), but I don't see it on https://tracker.debian.org/pkg/python-django nor in the ftp-master logs. Could you check whether the upload got

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

Your message dated Fri, 09 May 2025 09:16:21 + with message-id and subject line Bug#1104942: Removed package(s) from unstable has caused the Debian Bug report #1082407, regarding Removal notice: obsolete to be marked as done. This means that you claim that the problem has been dealt with. If

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

Your message dated Fri, 09 May 2025 09:19:57 + with message-id and subject line Bug#1104949: Removed package(s) from unstable has caused the Debian Bug report #1082410, regarding Removal notice: obsolete to be marked as done. This means that you claim that the problem has been dealt with. If

Bug#1051986: fixed in scalapack 2.2.1-3

Oh, I see it is fixed in testing. Could this please be backported to stable as well? Cheers, Henri On 5/9/25 09:23, Henri Menke wrote: > This bug has definitely not been fixed. Here is a simple reproducer for > Debian bookworm: > > # apt install cmake libscalapack-mpi-dev > # cat

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

Your message dated Fri, 09 May 2025 09:22:02 + with message-id and subject line Bug#1104953: Removed package(s) from unstable has caused the Debian Bug report #1082423, regarding Removal notice: obsolete to be marked as done. This means that you claim that the problem has been dealt with. If

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

Your message dated Fri, 09 May 2025 09:18:23 + with message-id and subject line Bug#1104946: Removed package(s) from unstable has caused the Debian Bug report #1082409, regarding Removal notice: obsolete to be marked as done. This means that you claim that the problem has been dealt with. If

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

Your message dated Fri, 09 May 2025 09:19:29 + with message-id and subject line Bug#1104948: Removed package(s) from unstable has caused the Debian Bug report #1082355, regarding Removal notice: obsolete to be marked as done. This means that you claim that the problem has been dealt with. If

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

Your message dated Fri, 09 May 2025 09:15:47 + with message-id and subject line Bug#1104941: Removed package(s) from unstable has caused the Debian Bug report #1082405, regarding Removal notice: obsolete to be marked as done. This means that you claim that the problem has been dealt with. If

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

Your message dated Fri, 09 May 2025 09:17:52 + with message-id and subject line Bug#1104945: Removed package(s) from unstable has caused the Debian Bug report #1082408, regarding Removal notice: obsolete to be marked as done. This means that you claim that the problem has been dealt with. If

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

Your message dated Fri, 09 May 2025 09:16:49 + with message-id and subject line Bug#1104943: Removed package(s) from unstable has caused the Debian Bug report #1082348, regarding Removal notice: obsolete to be marked as done. This means that you claim that the problem has been dealt with. If

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

Your message dated Fri, 09 May 2025 09:14:18 + with message-id and subject line Bug#1104937: Removed package(s) from unstable has caused the Debian Bug report #1101173, regarding Removal notice: obsolete to be marked as done. This means that you claim that the problem has been dealt with. If

Bug#1102991: marked as done (haskell-cryptol: unsatisfiable build-depencny in unstable on libghc-base-compat-dev (< 0.13))

Your message dated Fri, 09 May 2025 09:14:48 + with message-id and subject line Bug#1104938: Removed package(s) from unstable has caused the Debian Bug report #1102991, regarding haskell-cryptol: unsatisfiable build-depencny in unstable on libghc-base-compat-dev (< 0.13) to be marked as done.

Processed: closing 1104471

Processing commands for cont...@bugs.debian.org: > close 1104471 Bug #1104471 [raku-json-class,raku-json-unmarshal,raku-license-spdx,raku-meta6,raku-test-meta] 5 packages have an undeclared file conflict on /usr/lib/perl6/vendor/precomp/B202134926643267DBA87C686CDAE403DD76376F/DB/DB27F6C72B99F9

Bug#1104471: closing 1104471

close 1104471 thanks This bug is fixed with the packages built with dh_raku >= 0.19

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

Hi Tobias, I managed to perform a (somewhat shallow) test of https://people.debian.org/~tobi/simplesamlphp/simplesamlphp_1.19.0-1+deb11u2~_all.deb ; all results look good to me: I can do a saml login using that package. And the "SimpleSAMLphp installation page" looks good to me too. Since I do h

Bug#1104969: autogen: trying to overwrite '/usr/share/aclocal/autoopts.m4', which is also in package libopts25-dev

Package: autogen Version: 1:5.18.16-5.1 Severity: serious Tags: ftbfs X-Debbugs-Cc: Bastian Germann Control: affects -1 src:gcc-xtensa https://buildd.debian.org/status/fetch.php?pkg=gcc-xtensa&arch=amd64&ver=14%2Bb3&stamp=1746776863&raw=0 ... Unpacking autogen (1:5.18.16-5.1) ... dpkg: error pro

Processed: autogen: trying to overwrite '/usr/share/aclocal/autoopts.m4', which is also in package libopts25-dev

Processing control commands: > affects -1 src:gcc-xtensa Bug #1104969 [autogen] autogen: trying to overwrite '/usr/share/aclocal/autoopts.m4', which is also in package libopts25-dev Added indication that 1104969 affects src:gcc-xtensa -- 1104969: https://bugs.debian.org/cgi-bin/bugreport.cgi?bu

Bug#1104543: marked as done (nmu: nodejs_20.19.0+dfsg1-1)

Your message dated Fri, 9 May 2025 09:54:12 +0200 with message-id and subject line Re: Bug#1104543: nmu: nodejs_20.19.0+dfsg1-1 has caused the Debian Bug report #1104543, regarding nmu: nodejs_20.19.0+dfsg1-1 to be marked as done. This means that you claim that the problem has been dealt with. If