Ludovic Courtès writes:
> Hi!
>
> Chris Marusich skribis:
>
>> As an aside, when do we remove old versions of glibc?
>
> Good question. I’d say it’s enough to keep 3 versions in total.
> Currently the main (only?) use case for these is when computing locale
> data via the ‘locale-libcs’ field o
Hi!
Chris Marusich skribis:
> As an aside, when do we remove old versions of glibc?
Good question. I’d say it’s enough to keep 3 versions in total.
Currently the main (only?) use case for these is when computing locale
data via the ‘locale-libcs’ field of operating system definitions.
Thought
Chris Marusich writes:
> On core-updates, the glibc-2.31 patch no longer apply cleanly.
Looks like the other old glibc versions explicitly declare their
patches, like this:
--8<---cut here---start->8---
(define-public glibc-2.30
(package
(inherit glibc
Hi,
On core-updates, the glibc-2.31 patch no longer apply cleanly. This
causes glibc-2.31 to fail to build. This causes downstream problems;
for example, building a Guix System from bare-bones.tmpl fails because
%default-locale-libcs still contains glibc-2.31.
Example:
--8<---cut h
