From: "Ludovic Courtès" <ludo@gnu.org>
To: 66472@debbugs.gnu.org
Cc: Janneke Nieuwenhuizen <janneke@gnu.org>,
Josselin Poiret <dev@jpoiret.xyz>
Subject: bug#66472: Wrong ‘glibc-utf8-locales’ package used on GNU/Hurd
Date: Wed, 11 Oct 2023 23:42:53 +0200 [thread overview]
Message-ID: <87wmvsq1ia.fsf@inria.fr> (raw)
Hi!
We discussed it briefly on IRC the other day: our packages get built on
i586-gnu with the wrong ‘glibc-utf8-locales’ package (2.35 instead of
2.37), which causes Coreutils among others to fail to build:
--8<---------------cut here---------------start------------->8---
environment variable `GUIX_LOCPATH' set to `/gnu/store/sq6w1nfi59askjfq6b1nqq6z8ld5zh1l-glibc-utf8-locales-2.35/lib/locale'
phase `set-paths' succeeded after 0.0 seconds
starting phase `install-locale'
warning: failed to install 'en_US.utf8' locale: Invalid argument
phase `install-locale' succeeded after 0.0 seconds
[…]
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>
phase `remove-tests' failed after 0.1 seconds
[…]
builder for `/gnu/store/vvp0yxvyxsrwmmzli7dsxinr6p9ba3mj-coreutils-9.1.drv' failed with exit code 1
--8<---------------cut here---------------end--------------->8---
(This is from <https://ci.guix.gnu.org/build/2062597/details>, made with
commit cdbd81ce144f17644ceebd3d08723aa244696a05.)
So we need a better fix than the local workaround in
21deb89e287b5821975544118bf137562a91d4e1.
Thoughts? Perhaps you’ve looked into it already?
Ludo’.
next reply other threads:[~2023-10-11 21:43 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-10-11 21:42 Ludovic Courtès [this message]
2023-10-12 14:12 ` bug#66472: Wrong ‘glibc-utf8-locales’ package used on GNU/Hurd 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
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=87wmvsq1ia.fsf@inria.fr \
--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.