From: Maxime Devos <maximedevos@telenet.be>
To: Brendan Tildesley <mail@brendan.scot>,
"53204@debbugs.gnu.org" <53204@debbugs.gnu.org>
Subject: bug#53204: [patch] font-cns11643: ... unzip error
Date: Mon, 31 Jan 2022 13:35:00 +0100 [thread overview]
Message-ID: <4e25e509335d3794271767594ba2988f9ab82cab.camel@telenet.be> (raw)
In-Reply-To: <1070829080.156978.1643628182234@office.mailbox.org>
[-- Attachment #1: Type: text/plain, Size: 728 bytes --]
Brendan Tildesley schreef op ma 31-01-2022 om 12:23 [+0100]:
> I just noticed there is also this:
>
> starting phase `install-locale'
> warning: failed to install 'en_US.utf8' locale: Invalid argument
>
>
> It occurs for other font-build-system fonts too. Adding glibc-utf8-locales or glibc-locales didn't fix it.
> I don't understand it because its just based off gnu-build-system which doesn't have that issue.
>
> It doesn't GUIX_LOCPATH either
Perhaps the cause is that font-build-system doesn't have glibc among
its (implicit) native-inputs, and hence there's no GUIX_LOCPATH search
path (see <https://issues.guix.gnu.org/22138>)?
Adding glibc to the native-inputs might work.
Greetings,
Maxime.
[-- Attachment #2: This is a digitally signed message part --]
[-- Type: application/pgp-signature, Size: 260 bytes --]
next prev parent reply other threads:[~2022-01-31 14:28 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-01-12 8:54 bug#53204: [patch] font-cns11643: Open_Data hash changed Dr. Arne Babenhauserheide
2022-01-12 10:45 ` Maxime Devos
2022-01-12 11:13 ` Maxime Devos
2022-01-12 11:41 ` Dr. Arne Babenhauserheide
2022-01-12 12:18 ` Maxime Devos
2022-01-31 1:59 ` bug#53204: [patch] font-cns11643: ... unzip error Brendan Tildesley
2022-01-31 9:18 ` Maxime Devos
2022-01-31 11:23 ` Brendan Tildesley
2022-01-31 12:35 ` Maxime Devos [this message]
2022-02-01 1:23 ` Brendan Tildesley
2022-10-09 6:38 ` bug#53204: [patch] font-cns11643: Open_Data hash changed Brendan Tildesley
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=4e25e509335d3794271767594ba2988f9ab82cab.camel@telenet.be \
--to=maximedevos@telenet.be \
--cc=53204@debbugs.gnu.org \
--cc=mail@brendan.scot \
/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).