GNU bug report logs - #52879
[installer] Can we remove locale-2.31 from locale-libcs in the upcoming release?

Previous Next

To add a comment to this bug, you must first unarchive it, by sending
a message to control AT debbugs.gnu.org, with unarchive 52879 in the body.
You can then email your comments to 52879 AT debbugs.gnu.org in the normal way.

Toggle the display of automated, internal messages from the tracker.

Message #5 received at submit <at> debbugs.gnu.org (full text, mbox):

From: Leo Famulari <leo <at> famulari.name>
To: bug-guix <at> gnu.org
Subject: [installer] Can we remove locale-2.31 from locale-libcs in the
 upcoming release?
Date: Wed, 29 Dec 2021 13:41:49 -0500

I noticed that the installer built from current master includes locales
from glibc 2.31 and 2.33, because they are both in
%default-locale-libcs.

Will we still need this workaround for the upcoming release? Presumably,
new installations will not include anything that uses glibc 2.31.

Message #10 received at 52879-done <at> debbugs.gnu.org (full text, mbox):

From: Mathieu Othacehe <othacehe <at> gnu.org>
To: Leo Famulari <leo <at> famulari.name>
Cc: 52879-done <at> debbugs.gnu.org
Subject: Re: bug#52879: [installer] Can we remove locale-2.31 from
 locale-libcs in the upcoming release?
Date: Mon, 03 Jan 2022 14:48:29 +0100

Hello,

> I noticed that the installer built from current master includes locales
> from glibc 2.31 and 2.33, because they are both in
> %default-locale-libcs.
>
> Will we still need this workaround for the upcoming release? Presumably,
> new installations will not include anything that uses glibc 2.31.

Done with 52c94de76795a7e7151bf5f5d6a5a6b9d3240a18.

Thanks,

Mathieu

Previous Next

GNU bug tracking system
Copyright (C) 1999 Darren O. Benham, 1997,2003 nCipher Corporation Ltd, 1994-97 Ian Jackson.