Re: Re-planning for 12.6

2024-04-03 Thread Andrew M.A. Cater
On Mon, Apr 01, 2024 at 01:07:27PM +0100, Adam D. Barratt wrote: > Hi, > > As we had to postpone 12.6, let's look at alternative dates. > Can do all, I think, Andy (amaca...@debian.org) > > Adam >

Bug#1068345: trixie-pu: package chromium/123.0.6312.105-1~deb13u1

2024-04-03 Thread Andres Salomon
Package: release.debian.org Severity: normal Tags: trixie User: release.debian@packages.debian.org Usertags: pu Given the time_t transition, several folks have requested chromium updates via t-p-u. The current version in testing (122.0.6261.57-1) has 20 CVEs that are fixed in newer

Bug#1068344: bookworm-pu: package curl/7.88.1-10+deb12u6

2024-04-03 Thread Guilherme Puida Moreira
Package: release.debian.org Severity: normal Tags: bookworm X-Debbugs-Cc: c...@packages.debian.org, guilhe...@puida.xyz Control: affects -1 + src:curl User: release.debian@packages.debian.org Usertags: pu [ Reason ] 1. Fix CVE-2004 > When a protocol selection parameter option disables all

Processed: bookworm-pu: package curl/7.88.1-10+deb12u6

2024-04-03 Thread Debian Bug Tracking System
Processing control commands: > affects -1 + src:curl Bug #1068344 [release.debian.org] bookworm-pu: package curl/7.88.1-10+deb12u6 Added indication that 1068344 affects src:curl -- 1068344: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1068344 Debian Bug Tracking System Contact

Bug#1068084: bookworm-pu: package intel-microcode/3.20240312.1~deb12u1

2024-04-03 Thread Henrique de Moraes Holschuh
Uploaded. On Mon, Apr 1, 2024, at 08:48, Jonathan Wiltshire wrote: > Control: tag -1 confirmed > > On Sat, Mar 30, 2024 at 07:47:05AM -0300, Henrique de Moraes Holschuh wrote: >> As requested by the security team, I would like to bring the microcode >> update level for Intel processors in

Bug#1064810: Bug#1067055: openmpi: error: implicit declaration of function 'OPAL_THREAD_ADD_FETCH64'

2024-04-03 Thread Alastair McKinstry
On 02/04/2024 21:29, Sebastian Ramacher wrote: To be honest, I don't see these two changes (changing mpi-defaults to mpich on 32 bit; breaking 32 bit build of openmpi) to be ready. It'd be preferable to reinstate a 32-bit compatible pmix and fix openmpi on 32 bit until the time_t transition is

Bug#1068326: bookworm-pu: package mksh/59c-28+deb12u1

2024-04-03 Thread Thorsten Glaser
Package: release.debian.org Severity: normal Tags: bookworm X-Debbugs-Cc: m...@packages.debian.org, t...@mirbsd.de Control: affects -1 + src:mksh User: release.debian@packages.debian.org Usertags: pu I would like to ask for pre-approval to uploading a proposed stable update for mksh. [

Processed: bookworm-pu: package mksh/59c-28+deb12u1

2024-04-03 Thread Debian Bug Tracking System
Processing control commands: > affects -1 + src:mksh Bug #1068326 [release.debian.org] bookworm-pu: package mksh/59c-28+deb12u1 Added indication that 1068326 affects src:mksh -- 1068326: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1068326 Debian Bug Tracking System Contact

Bug#1064810: Bug#1067055: openmpi: error: implicit declaration of function 'OPAL_THREAD_ADD_FETCH64'

2024-04-03 Thread Alastair McKinstry
On 02/04/2024 21:29, Sebastian Ramacher wrote: OpenMPI 5 drops 32-bit support, but otherwise does not change the API/ABI. So it is technically not a transition, but breaks 32-bit builds. Doesn't make it better. This is not the time to do that without tests builds and bugs filed. The