Bug#1016576: transition: glibc 2.34
Control: tags -1 confirmed
Control: forwarded -1 https://release.debian.org/transitions/html/glibc-2.34.html
On 2022-08-03 11:49:20 +0200, Aurelien Jarno wrote:
> Package: release.debian.org
> Severity: normal
> User: release.debian.org@packages.debian.org
> Usertags: transition
> X-Debbugs-Cc: debian-glibc@lists.debian.org
>
> Dear release team,
>
> I would like to get a transition slot for glibc 2.34. It has been
> available in experimental for a few months, and does not have any known
> major issue. It has been built successfully on all release architectures
> and many ports architectures.
Please go ahead.
Cheers
>
> This transition is a bit more complex than the previous ones, as this
> version merges a few libraries (libpthread, libdl, libutil, libanl) into
> libc. This handled transparently at runtime.
>
> This is also supposed to be handled transparently at link time by
> providing empty static archives for libpthread.a, libdl.a, libutil.a,
> libanl.a. That said it appears that the path to libpthread.so and
> libdl.so is encoded in a few cmake files). Breaks against the affected
> -dev packages have been added, and they will need to be binNMUed. Here
> is the list:
>
> assimp
> deal.ii
> dolfin
> eckit
> fclib
> fltk1.3
> insighttoolkit4
> insighttoolkit5
> ismrmrd
> libminc
> log4cplus
> mathgl
> mimalloc
> mongo-c-driver
> mrpt
> netcdf
> netcdf-parallel
> ns3
> openms
> trilinos
> visp
> votca
> vtk6
> vtk7
>
> In addition some symbols from libresolv symbols also got moved to libc,
> and their __ prefix dropped at the same time. While there compatibility
> symbols for dynamic linking, it it not the case for static linking.
> Static libraries with reference to those symbols needs to be binNMUed.
> Breaks against the affected -dev packages have been added, and they will
> need to be binNMUed. Here is the list:
>
> boinc
> cups
> dante
> glib2.0
> gloox
> haskell-resolv
> heimdal
> hesiod
> libasyncns
> libaws
> libdkim
> libinfinity
> libpg-query
> libre
> libspf2
> libstrophe
> linux-atm
> loudmouth
> mongo-c-driver
> mysql-8.0
> ncbi-igblast
> nfs-utils
> ola
> openafs
> opendkim
> opendmarc
> openldap
> open-vm-tools
> openzwave
> pidgin-librvp
> proftpd-dfsg
> shishi
> slurm-wlm
> taningia
>
> A few issues found through the autopkgtest pseudo excuses for
> experimental have been fixed. Most of the remaining are either due to
> the added breaks (see above), britney bugs or packages parts of the
> transition. There are a few remaining though, but at this stage it's
> probably better to move forward and get them fixed later, otherwise new
> ones keep appearing. Here is the list:
>
> castle-game-engine: #1016556
> dash: #1016554
> fpc: #1016556
> scalpel: #1016560
> securefs: #993515
> wmanager: #1016540
> wcc: #1014729 (A binNMU fixes the issue, but not sure why)
>
> A tracker is already setup at:
> https://release.debian.org/transitions/html/glibc-2.34.html
>
> Thanks for considering.
>
> Regards
> Aurelien
>
--
Sebastian Ramacher
Reply to: