Re: Status of the t64 transition

2024-04-18 Thread Andreas Metzler
On 2024-04-18 Sebastian Ramacher wrote: [...] > Let's start with the first category. Those are packages that could be > binNMUed, but there are issues that make those rebuilds not have the > desired effect. This list include packages that > * are BD-Uninstallabe, > * FTBFS but with out

Bug#1069262: bookworm-pu: package u-boot/2023.01+dfsg-2+deb12u1

2024-04-18 Thread Vagrant Cascadian
Package: release.debian.org Severity: normal Tags: bookworm User: release.debian@packages.debian.org Usertags: pu X-Debbugs-Cc: u-b...@packages.debian.org, vagr...@debian.org Control: affects -1 + src:u-boot [ Reason ] Fixes the timer clock used by various "orion" based platforms, such as

Processed: bookworm-pu: package u-boot/2023.01+dfsg-2+deb12u1

2024-04-18 Thread Debian Bug Tracking System
Processing control commands: > affects -1 + src:u-boot Bug #1069262 [release.debian.org] bookworm-pu: package u-boot/2023.01+dfsg-2+deb12u1 Added indication that 1069262 affects src:u-boot -- 1069262: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1069262 Debian Bug Tracking System Contact

Re: Re-planning for 12.6

2024-04-18 Thread Steve McIntyre
Hiya! Not wanting to pester *too* much, but where are we up to? On Tue, Apr 02, 2024 at 10:53:49PM +0100, Steve McIntyre wrote: >On Mon, Apr 01, 2024 at 01:07:27PM +0100, Adam Barratt wrote: >>Hi, >> >>As we had to postpone 12.6, let's look at alternative dates. >> >>April 13th >>- Not great for

Bug#1067944: marked as done (nmu: openjdk-17_17.0.11~7ea-1)

2024-04-18 Thread Debian Bug Tracking System
Your message dated Thu, 18 Apr 2024 21:57:42 +0200 with message-id and subject line Re: Bug#1067944: nmu: openjdk-17_17.0.11~7ea-1 has caused the Debian Bug report #1067944, regarding nmu: openjdk-17_17.0.11~7ea-1 to be marked as done. This means that you claim that the problem has been dealt

Bug#1068366: marked as done (nmu: gyoto_2.0.2-1.1)

2024-04-18 Thread Debian Bug Tracking System
Your message dated Thu, 18 Apr 2024 21:56:47 +0200 with message-id and subject line Re: Bug#1068366: nmu: gyoto_2.0.2-1.1 has caused the Debian Bug report #1068366, regarding nmu: gyoto_2.0.2-1.1 to be marked as done. This means that you claim that the problem has been dealt with. If this is not

Processed: bullseye-pu: package libapache2-mod-auth-openidc/2.4.9.4-0+deb11u4

2024-04-18 Thread Debian Bug Tracking System
Processing control commands: > affects -1 + src:libapache2-mod-auth-openidc Bug #1069253 [release.debian.org] bullseye-pu: package libapache2-mod-auth-openidc/2.4.9.4-0+deb11u4 Added indication that 1069253 affects src:libapache2-mod-auth-openidc -- 1069253:

Bug#1069252: bookworm-pu: package libapache2-mod-auth-openidc/2.4.12.3-2+deb12u1

2024-04-18 Thread Moritz Schlarb
Package: release.debian.org Severity: normal Tags: bookworm X-Debbugs-Cc: libapache2-mod-auth-open...@packages.debian.org, t...@security.debian.org Control: affects -1 + src:libapache2-mod-auth-openidc User: release.debian@packages.debian.org Usertags: pu [ Reason ] Backported the patch to

Bug#1069253: bullseye-pu: package libapache2-mod-auth-openidc/2.4.9.4-0+deb11u4

2024-04-18 Thread Moritz Schlarb
Package: release.debian.org Severity: normal Tags: bullseye X-Debbugs-Cc: libapache2-mod-auth-open...@packages.debian.org, t...@security.debian.org Control: affects -1 + src:libapache2-mod-auth-openidc User: release.debian@packages.debian.org Usertags: pu [ Reason ] Backported the patch to

Processed: bookworm-pu: package libapache2-mod-auth-openidc/2.4.12.3-2+deb12u1

2024-04-18 Thread Debian Bug Tracking System
Processing control commands: > affects -1 + src:libapache2-mod-auth-openidc Bug #1069252 [release.debian.org] bookworm-pu: package libapache2-mod-auth-openidc/2.4.12.3-2+deb12u1 Added indication that 1069252 affects src:libapache2-mod-auth-openidc -- 1069252:

Status of the t64 transition

2024-04-18 Thread Sebastian Ramacher
Hi, as the progress on the t64 transition is slowing down, I want to give an overview of some of the remaining blockers that we need to tackle to get it unstuck. I tried to identify some clusters of issues, but there might be other classes of issues. Let's start with the first category. Those

Re: R 4.4.0 coming April 24

2024-04-18 Thread Dirk Eddelbuettel
Hi Paul, On 18 April 2024 at 11:50, Paul Gevers wrote: | Hi Dirk, | | On 18-04-2024 4:41 a.m., Dirk Eddelbuettel wrote: | > I uploaded a first | > beta release r-base_4.3.3.20240409-1 to 'experimental' a week ago, I just | > followed up with a rc release r-base_4.3.3.20240416-1. | | Thanks

Re: R 4.4.0 coming April 24

2024-04-18 Thread Paul Gevers
Hi Dirk, On 18-04-2024 4:41 a.m., Dirk Eddelbuettel wrote: I uploaded a first beta release r-base_4.3.3.20240409-1 to 'experimental' a week ago, I just followed up with a rc release r-base_4.3.3.20240416-1. Thanks for preparing in experimental, as that triggers some QA. Given these