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 Ubuntu fairly soon and I
> want
> > to make
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 Ubuntu fairly soon and I want
> to make sure we adapt to an upstream way in a way that is aligned with any
>
* Michael Hudson-Doyle:
> (but then, dpkg is not
> impacted by the symbolic link issue as far as I know).
>
> Is this problem written up somewhere? I only subscribed to libc-alpha
> a few weeks ago.
I've written about it in various places.
As far as I know, it's specific to how RPM performs
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] for Ubuntu (only for testing so far)
* 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] for Ubuntu (only for testing so far) is to
> install libc to /lib/$multiarch/libc.so.6, the dynamic
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
6 matches
Mail list logo
