unofficial mirror of bug-guix@gnu.org 
 help / color / mirror / code / Atom feed
From: Janneke Nieuwenhuizen <janneke@gnu.org>
To: "Ludovic Courtès" <ludo@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, 14 Oct 2023 22:22:15 +0200	[thread overview]
Message-ID: <871qdxj6o8.fsf@gnu.org> (raw)
In-Reply-To: <87o7h1cda6.fsf@gnu.org> ("Ludovic Courtès"'s message of "Sat, 14 Oct 2023 19:41:21 +0200")

Ludovic Courtès writes:

> Hi,
>
> Janneke Nieuwenhuizen <janneke@gnu.org> skribis:
>
>>> starting phase `remove-tests'
>>> error: in phase 'remove-tests': uncaught exception:
>>> decoding-error "decode-char" "input decoding error" 1073741930
>>> #<input: tests/misc/ls-misc.pl 15>
>
> [...]
>
>> Hmm.  I've briefly looked at this but failed to reproduce it.  I've
>> tried building coreutils, and coreutils-final in a childhurd created
>> from "a recent" hurd-team branch.
>>
>> root@guixydevel ~/src/guix/hurd-team [env]# ./pre-inst-env guix
>> build --keep-failed -e '(@@ (gnu packages commencement)
>> coreutils-final)' --without-tests=coreutils
>> [..]
>> environment variable `GUIX_LOCPATH' set to
>> `/gnu/store/sq6w1nfi59askjfq6b1nqq6z8ld5zh1l-glibc-utf8-locales-2.35/lib/locale'
>> [..]
>> phase `unpack' succeeded after 10.4 seconds
>> starting phase `remove-tests'
>> phase `remove-tests' succeeded after 0.5 seconds
>
> Maybe something differs on ‘hurd-team’?

Well, yeah.  I've been building in a childhurd created from
gnu/system/examples/devel-hurd.tmpl, which currently has

    (locale-libcs (if (system-hurd?)
                      (list glibc/hurd)
                      %default-locale-libcs))

> For me it’s 100% reproducible
> on ‘master’, even though my childhurd has
> /run/current-system/locale/2.37 (I thought this could interfere but
> luckily it doesn’t.)
>
> 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?

Greetings,
Janneke

-- 
Janneke Nieuwenhuizen <janneke@gnu.org>  | GNU LilyPond https://LilyPond.org
Freelance IT https://www.JoyOfSource.com | Avatar® https://AvatarAcademy.com




  reply	other threads:[~2023-10-14 20:23 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 [this message]
2023-10-21 14:34       ` Ludovic Courtès
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

  List information: https://guix.gnu.org/

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=871qdxj6o8.fsf@gnu.org \
    --to=janneke@gnu.org \
    --cc=66472@debbugs.gnu.org \
    --cc=dev@jpoiret.xyz \
    --cc=ludo@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 public inbox

	https://git.savannah.gnu.org/cgit/guix.git

This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).