From: "Ludovic Courtès" <ludo@gnu.org>
To: Janneke Nieuwenhuizen <janneke@gnu.org>
Cc: 66472@debbugs.gnu.org, Josselin Poiret <dev@jpoiret.xyz>
Subject: bug#66472: Wrong ‘glibc-utf8-locales’ package used on GNU/Hurd
Date: Sat, 21 Oct 2023 16:34:23 +0200 [thread overview]
Message-ID: <87r0looxhs.fsf@gnu.org> (raw)
In-Reply-To: <871qdxj6o8.fsf@gnu.org> (Janneke Nieuwenhuizen's message of "Sat, 14 Oct 2023 22:22:15 +0200")
Hi,
Janneke Nieuwenhuizen <janneke@gnu.org> skribis:
> Ludovic Courtès writes:
[...]
>> Anyway, in both cases the core issue remains: we’re building packages
>> with the wrong locale data.
>>
>> The mismatch comes from the fact that ‘glibc-utf8-locales’ is a
>> system-independent package: you get 2.35 regardless of the system you’re
>> targeting.
>
> Right. Is that easy, difficult, or impossible to change?
We could define ‘glibc-utf8-locales’ with ‘define/system-dependent’, as
we’ve done in commencement.scm. However, I don’t think that’s feasible
because then every place that does:
(module-ref (resolve-interface '(gnu packages base))
'glibc-utf8-locales)
will suddenly be broken, and that’s not acceptable.
So I’m not sure what to do. Again I feel that maintaining two libc
variants is too costly. Time to upgrade in ‘core-updates’?
Ludo’.
next prev parent reply other threads:[~2023-10-21 14:35 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-10-11 21:42 bug#66472: Wrong ‘glibc-utf8-locales’ package used on GNU/Hurd Ludovic Courtès
2023-10-12 14:12 ` Janneke Nieuwenhuizen
2023-10-14 17:41 ` Ludovic Courtès
2023-10-14 20:22 ` Janneke Nieuwenhuizen
2023-10-21 14:34 ` Ludovic Courtès [this message]
2023-10-22 12:26 ` Janneke Nieuwenhuizen
2023-11-25 16:51 ` Ludovic Courtès
2023-11-27 17:12 ` Janneke Nieuwenhuizen
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=87r0looxhs.fsf@gnu.org \
--to=ludo@gnu.org \
--cc=66472@debbugs.gnu.org \
--cc=dev@jpoiret.xyz \
--cc=janneke@gnu.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
Code repositories for project(s) associated with this external index
https://git.savannah.gnu.org/cgit/guix.git
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.