Processed: forcibly merging 1067508 1067509

2024-03-22 Thread Debian Bug Tracking System
Processing commands for cont...@bugs.debian.org: > forcemerge 1067508 1067509 Bug #1067508 [debhelper] debhelper: lost most of its dependencies in 13.15 Bug #1067509 [debhelper] debhelper: Can't locate Debian/Debhelper/Dh_Lib.pm in @INC 1036884 was blocked by: 1067193 1067189 1067190 1062847

Processed: debhelper: lost most of its dependencies in 13.15

2024-03-22 Thread Debian Bug Tracking System
Processing control commands: > block 1036884 by -1 Bug #1036884 [release.debian.org] transition: time64_t 1036884 was blocked by: 1066794 1066049 1065787 1062847 1067175 1067189 1067171 1055530 1067192 1067190 1065816 1067069 1067458 1067288 1067193 1055352 1065973 1067170 1036884 was not

Re: CRAN Package Matrix update and a possible transition or not

2024-03-22 Thread Dirk Eddelbuettel
On 27 February 2024 at 19:01, Dirk Eddelbuettel wrote: | A couple of days ago, the (effective) Maintainer and rather active developer | of the Matrix package Mikael Jagan (CC'ed) posted on the r-package-devel list | (the primary list for R package development) that the upcoming change of |

Bug#987013: Release goal proposal: Remove Berkeley DB

2024-03-22 Thread Marco Moock
On Sat, 4 Feb 2023 08:50:29 +0100 Paul Gevers wrote: > > Remove Berkeley DB (finally) > > Sure. But I agree with several readers of this bug that there should > be a plan. We shouldn't kill it until the users are able to sanely > move away from it. I doubt that will happen automatically, so >

Re: Bug#1067490: tracker.debian.org: Display release-team blocks more prominently

2024-03-22 Thread Raphael Hertzog
Hi, top-posting and leaving quite some context because the main point of my message is to actually share your bug report to the release team. If I remember correctly, tracker.debian.org is not doing any fancy treatment. We are just turning some YAML into HTML:

Processed: affects 1067288, block 1036884 with 1067288, merging 1067458 1067288

2024-03-22 Thread Debian Bug Tracking System
Processing commands for cont...@bugs.debian.org: > affects 1067288 + src:pulseaudio Bug #1067288 [src:orc] pulseaudio: FTBFS on x86: cpu-volume-test fails, segfault in svolume_orc_test Added indication that 1067288 affects src:pulseaudio > block 1036884 with 1067288 Bug #1036884

Bug#1067476: marked as done (nmu: systemd_255.4-1+b1)

2024-03-22 Thread Debian Bug Tracking System
Your message dated Fri, 22 Mar 2024 10:21:44 +0100 with message-id and subject line Re: Bug#1067476: nmu: systemd_255.4-1+b1 has caused the Debian Bug report #1067476, regarding nmu: systemd_255.4-1+b1 to be marked as done. This means that you claim that the problem has been dealt with. If this

Bug#1067477: marked as done (nmu: mesa_23.3.5-1)

2024-03-22 Thread Debian Bug Tracking System
Your message dated Fri, 22 Mar 2024 10:21:58 +0100 with message-id and subject line Re: Bug#1067477: nmu: mesa_23.3.5-1 has caused the Debian Bug report #1067477, regarding nmu: mesa_23.3.5-1 to be marked as done. This means that you claim that the problem has been dealt with. If this is not the

Processed: nmu: systemd_255.4-1+b1

2024-03-22 Thread Debian Bug Tracking System
Processing control commands: > affects -1 + src:systemd Bug #1067476 [release.debian.org] nmu: systemd_255.4-1+b1 Added indication that 1067476 affects src:systemd -- 1067476: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1067476 Debian Bug Tracking System Contact ow...@bugs.debian.org with

Bug#1067476: nmu: systemd_255.4-1+b1

2024-03-22 Thread Andrey Rakhmatullin
Package: release.debian.org Severity: normal X-Debbugs-Cc: syst...@packages.debian.org Control: affects -1 + src:systemd User: release.debian@packages.debian.org Usertags: binnmu nmu systemd_255.4-1+b1 . armel armhf . unstable . -m "Rebuild on buildds"

Processed: nmu: mesa_23.3.5-1

2024-03-22 Thread Debian Bug Tracking System
Processing control commands: > affects -1 + src:mesa Bug #1067477 [release.debian.org] nmu: mesa_23.3.5-1 Added indication that 1067477 affects src:mesa -- 1067477: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1067477 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems

Bug#1067477: nmu: mesa_23.3.5-1

2024-03-22 Thread Andrey Rakhmatullin
Package: release.debian.org Severity: normal X-Debbugs-Cc: m...@packages.debian.org Control: affects -1 + src:mesa User: release.debian@packages.debian.org Usertags: binnmu nmu mesa_23.3.5-1 . armel armhf . unstable . -m "Rebuild after a nolibva binary upload"

Bug#1067475: marked as done (nmu: util-linux_2.39.3-10)

2024-03-22 Thread Debian Bug Tracking System
Your message dated Fri, 22 Mar 2024 12:17:03 +0500 with message-id and subject line Re: nmu: util-linux_2.39.3-10 has caused the Debian Bug report #1067475, regarding nmu: util-linux_2.39.3-10 to be marked as done. This means that you claim that the problem has been dealt with. If this is not

Processed: nmu: util-linux_2.39.3-10

2024-03-22 Thread Debian Bug Tracking System
Processing control commands: > affects -1 + src:util-linux Bug #1067475 [release.debian.org] nmu: util-linux_2.39.3-10 Added indication that 1067475 affects src:util-linux -- 1067475: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1067475 Debian Bug Tracking System Contact

Bug#1067475: nmu: util-linux_2.39.3-10

2024-03-22 Thread Andrey Rakhmatullin
Package: release.debian.org Severity: normal X-Debbugs-Cc: util-li...@packages.debian.org Control: affects -1 + src:util-linux User: release.debian@packages.debian.org Usertags: binnmu nmu util-linux_2.39.3-10 . armel armhf . unstable . -m "Rebuild on buildds"