Bug#1122038: libc6-dev: symbols not covering GLIBC_ABI_GNU_TLS on i386
Hi,
On 2025-12-07 19:42, Adrian Bunk wrote:
> On Sat, Dec 06, 2025 at 10:46:44PM +0100, Aurelien Jarno wrote:
> > On 2025-12-06 19:58, Adrian Bunk wrote:
> > > Updating trixie to the latest 2.41 git would bring the same issue there.
> >
> > Actually not, given trixie uses binutils 2.44.
>
> My understanding is that there are 3 separate issues here:
>
> 1. the binutils bug emitting it for all binaries (#1122125)
>
> 2. dpkg-gensymbols not handling some symbols
This is actually dpkg-shlibdeps (#1122107)
> 3. relaxing the dependencies in forky/i386 again (#1122038)
>
> Fixing item 1 alone would not make any difference without a fix for
> item 2.
Yes, but it doesn't prevent it to be fixed.
Also fixing item 2 without item 1 would already help, given the
libraries are unaffected.
> Item 2 should be resolved also for future cases, none of the first two
It must be fixed, as we already have the GLIBC_ABI_DT_X86_64_PLT flag
also introduced in 2.42, but that require non default compiling flag.
> items might be necessary for resolving item 3:
>
> The commits adding fix+symbol got backported to the 2.41 branch,
> this means we can get the symbol in trixie without the linker
> emitting which results in all supported setups being covered after
> the next trixie point release with that - and the workaround forcing
> 2.42 can then be dropped on/after January 10th.
On theory yes, but I think your are a bit optimistic there:
We might probably need to wait for more than that, as people doesn't
necessary upgrade to the latest point release just before trying to
upgrade to forky. We probably want to wait up to the next point release
for safety and avoid breaking many systems.
In addition, at this stage I am a bit reluctant to push all of this to
trixie for January 10th, as there might be other unnoticed side effects.
The issue has been there for 1.5 month, and to the best of my knowledge
nobody noticed that, even in other distributions.
So at the end it might be way faster to fix 1 and 2.
> Installing a forky package in bookworm (or in not up-to-date trixie)
> might result in non-working binaries despite the package dependencies
> permitting it, but this is anyway not officially supported.
Cherry-picking packages is different than upgrading, so yes I agree.
Regards
Aurelien
--
Aurelien Jarno GPG: 4096R/1DDD8C9B
aurelien@aurel32.net http://aurel32.net
Reply to: