Preparing for glibc 2.34: library locations

Hi, I know it won't be relevant to Debian for a while, but we're planning to upload to the upcoming glibc 2.34 release in Ubuntu fairly soon and I want to make sure we adapt to an upstream way in a way that is aligned with any plans for Debian. The issue is this: 2.33 and previous releases instal

Re: Preparing for glibc 2.34: library locations

On Mon, 26 Jul 2021 at 19:16, Florian Weimer wrote: > * Michael Hudson-Doyle: > > > There is another wrinkle of course in that Debian/Ubuntu install these > > files to /lib/$multiarch/, not /lib or /lib64 as upstream expects. > > > > What I've implemented[0]

Re: Preparing for glibc 2.34: library locations

On Sun, 5 Sept 2021 at 01:48, Aurelien Jarno wrote: > Hi, > > On 2021-07-15 11:11, Michael Hudson-Doyle wrote: > > Hi, > > > > I know it won't be relevant to Debian for a while, but we're planning to > > upload to the upcoming glibc 2.34 release in

Re: Bug#993821: After upgrading libc, some services are unable to restart (including systemd-resolved)

On Tue, 7 Sept 2021 at 10:21, Michael Biebl wrote: > Am 06.09.21 um 23:45 schrieb Vincent Bernat: > > Package: systemd > > Version: 247.9-1 > > Severity: normal > > > > Hey! > > > > After upgrading to libc6 2.32-1, some services are unable to restart. > > In my case, systemd-resolved, systemd

Re: Bug#993821: After upgrading libc, some services are unable to restart (including systemd-resolved)

On Tue, 7 Sept 2021 at 17:49, Michael Biebl wrote: > Control: reassign -1 libc6 > Control: found -1 2.32-1 > Control: severity -1 serious > Control: affects -1 + systemd > > Hi Michael > > Am 07.09.21 um 00:39 schrieb Michael Hudson-Doyle: > > On Tue, 7 Sep

Re: Bug#993821: After upgrading libc, some services are unable to restart (including systemd-resolved)

On Wed, 8 Sept 2021 at 07:04, Michael Biebl wrote: > Hi Aurelien > > Am 07.09.21 um 12:41 schrieb Aurelien Jarno: > > Hi, > > > > On 2021-09-07 10:39, Michael Hudson-Doyle wrote: > > >> What's happening is that systemd is running with the old glibc

Bug#1014729: glibc 2.34 breaks wcc autopkgtest on amd64: open: Invalid argument

It looks like a no-change rebuild fixed this in Ubuntu fwiw. On Mon, 11 Jul 2022 at 09:54, Aurelien Jarno wrote: > Source: glibc, wcc > Control: found -1 glibc/2.34-0experimental4 > Control: found -1 wcc/0.0.2+dfsg-4.1 > Severity: important > Tags: experimental > > Dear maintainers, > > The auto

Bug#1014729: glibc 2.34 breaks wcc autopkgtest on amd64: open: Invalid argument

On Tue, 12 Jul 2022 at 04:30, Aurelien Jarno wrote: > On 2022-07-11 10:06, Michael Hudson-Doyle wrote: > > It looks like a no-change rebuild fixed this in Ubuntu fwiw. > > Thanks, I confirm that in Debian too. Do you have an idea why? It could > be a missing or too loose depend

Bug#1053470: ld.so: ignore tunables in secure mode

I think that is the sort of conclusion upstream is coming to in https://inbox.sourceware.org/libc-alpha/20231003201151.1406279-1-siddh...@sourceware.org/T/#e9123bc53d892ab6552e05109ce939d531d741092 too. In any case, the upstream bug tracker / mailing list is probably the place to start with this.

Bug#1080244: Memory corruption with ancient i386 binaries using stdio

Would you be able to file an upstream report for this?