Re: Making trixie debootstrap-able again?

[Cyril Brulebois]

Hi,

Cyril Brulebois  (2024-04-26):
> I'm not sure how we reached this situation but there are a bunch of
> packages in trixie that are not in a suitable state. To reproduce, a
> simple `debootstrap trixie /tmp/trixie` on amd64 is sufficient.

That works again, presumably following the configuration changes in
britney made it complete again, finally migrating stuff.

> Note: I've limited my exploration to amd64, which kept me busy
> already…

That proviso is still true.


Cheers,
-- 
Cyril Brulebois (k...@debian.org)
D-I release manager -- Release team member -- Freelance Consultant


signature.asc
Description: PGP signature

Bug#1059852: transition: glibc 2.38

[Aurelien Jarno]

Hi,

On 2024-01-02 13:23, Aurelien Jarno wrote:
> Package: release.debian.org
> Severity: normal
> User: release.debian@packages.debian.org
> Usertags: transition
> X-Debbugs-Cc: gl...@packages.debian.org
> Control: affects -1 + src:glibc
> 
> Dear release team,
> 
> I would like to get a transition slot for glibc 2.38. It has been
> available in experimental for a few months and does not have any known
> issue anymore. It has been built successfully on all release
> architectures and most ports architectures, and the experimental
> pseudo-excuses look good overall.
> 
> As glibc is using symbol versioning, there is no soname change. That
> said a few packages are using libc internal symbols and have to be
> rebuilt for this transition. Here is the corresponding ben file:
> 
>   title = "glibc";
>   is_affected = .depends ~ /libc[0-9.]* \(<   is_good = .depends ~ /libc[0-9.]* \(<< 2.39\)/;
>   is_bad = .depends ~ /libc[0-9.]* \(<< 2.38\)/;
> 
> The main symbol related changes in this version are the addition of
> strlcat and strlcpy and related functions, coming from the BSD world. A
> few packages have their own implementation exported in their symbols
> file. With glibc 2.38 starting to provide those functions, the packages
> stops providing compatibility functions and the associated symbols,
> causing them to FTBFS. Many of them have been identified thanks to the
> hurd-amd64 bootstrap and have been fixed. The known remaining ones are:
>  - #1055297 ruby3.1: fails to build against glibc 2.38
>  - #1055316 heimdal: fails to build against glibc 2.38
> 
> Other than that a few symbols have been added to support the C2X binary
> constant handling in scanf family of functions. There are unlikely to be
> widely used at this point and thus that new packages start to use them,
> blocking their migration to testing during the transition.
> 
> Thanks for considering.

As discussed on IRC, I just uploaded it.

Regards
Aurelien

-- 
Aurelien Jarno  GPG: 4096R/1DDD8C9B
aurel...@aurel32.net http://aurel32.net

Processed: transition: nginx ABI change: nginx-abi-1.24.0-1 -> nginx-abi-1.26.0-1

[Debian Bug Tracking System]

Processing control commands:

> affects -1 + src:nginx
Bug #1070321 [release.debian.org] transition: nginx ABI change: 
nginx-abi-1.24.0-1 -> nginx-abi-1.26.0-1
Added indication that 1070321 affects src:nginx

-- 
1070321: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1070321
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems

Bug#1070321: transition: nginx ABI change: nginx-abi-1.24.0-1 -> nginx-abi-1.26.0-1

[Jan Mojzis]

Package: release.debian.org
Severity: normal
User: release.debian@packages.debian.org
Usertags: transition
X-Debbugs-Cc: ng...@packages.debian.org
Control: affects -1 + src:nginx

Hi,

a new version 1.26.0 of nginx has been released.

I have uploaded version 1.26.0-1~exp1 to the experimental and
would like to upload the new nginx 1.26.0-1 version to the unstable.

And with the upload of 1.26.0-1 nginx to unstable,
the nginx ABI version changes at the same time. Previous ABI 
nginx-abi-1.24.0-1, new ABI nginx-abi-1.26.0-1.

Therefore, we would also need to rebuild all 3rd party nginx modules 
(libnginx-mod-* packages)
which depends on nginx. Hence the transition request.

Furthermore, this upload/rebuild solves the problem that arises at time_t 64 
transition:
https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1069997


Ben file:

title = "nginx";
is_affected = .build-depends ~ /nginx-dev/;
is_good = .depends ~ /nginx-abi-1.26.0-1/;
is_bad = .depends ~ /nginx-abi-1.24.0-1/;


Please when the nginx 1.26.0-1 arives to the unstable,
can You schedule binNMUs for the above mentioned packages in unstable on all 
architectures.

Thanks
Jan

PS: ABI versioning is a relatively new feature in nginx, so this is the first 
transition request.
And any ideas how to automate the transitions are welcome

Processed: Re: nmu: golang-github-cowsql-go-cowsql

[Debian Bug Tracking System]

Processing control commands:

> retitle -1 nmu: golang-github-cowsql-go-cowsql
Bug #1064869 [release.debian.org] nmu: cowsql, golang-github-cowsql-go-cowsql
Changed Bug title to 'nmu: golang-github-cowsql-go-cowsql' from 'nmu: cowsql, 
golang-github-cowsql-go-cowsql'.
> affects -1 - src:cowsql
Bug #1064869 [release.debian.org] nmu: golang-github-cowsql-go-cowsql
Removed indication that 1064869 affects src:cowsql

-- 
1064869: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1064869
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems

Bug#1064869: nmu: golang-github-cowsql-go-cowsql

[Mathias Gibbens]

Control: retitle -1 nmu: golang-github-cowsql-go-cowsql
Control: affects -1 - src:cowsql


  I've backported a newer version of cowsql, which resolves the need
for a binNMU of that package.

  A binNMU is still requested for golang-github-cowsql-go-cowsql in
bookworm-backports.

Mathias


signature.asc
Description: This is a digitally signed message part

Bug#1067821: bookworm-pu: package nvidia-graphics-drivers/535.161.08-2~deb12u1

[Andreas Beckmann]

On 28/04/2024 22.39, Adam D. Barratt wrote:

On Sun, 2024-04-28 at 13:43 +0200, Andreas Beckmann wrote:

Please reject nvidia-graphics-drivers/535.161.08-1~deb12u1, nvidia-
driver-full is uninstallable on ppc64el (but that was hidden by the
other t64 transition blockers).


Done, thanks for letting us know.


nvidia-graphics-drivers (and the remainder of the 535 nvidia driver 
stack) has migrated to testing, so I've uploaded 535.161.08-2~deb12u1 
and now the 535 stack should be ready for inclusion in the next bookworm 
point release.



Andreas

Bug#1068762: bookworm-pu: package oar/2.5.9-1+deb12u1

[Vincent Danjean]

  Hi,

  Do you need more information in order to allow us or not to proceed with a 
oar stable update?
Please, let us known.

  Best regards,
Vincent