all messages for Guix-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: Maxime Devos <maximedevos@telenet.be>
To: Brendan Tildesley <mail@brendan.scot>,
	"53204@debbugs.gnu.org" <53204@debbugs.gnu.org>,
	Arne Babenhauserheide <arne_bab@web.de>
Subject: bug#53204: [patch] font-cns11643: ... unzip error
Date: Mon, 31 Jan 2022 10:18:55 +0100	[thread overview]
Message-ID: <417f2792a426652273e9558f31b13cb64b937183.camel@telenet.be> (raw)
In-Reply-To: <605642958.119824.1643594369280@office.mailbox.org>

[-- Attachment #1: Type: text/plain, Size: 443 bytes --]

Brendan Tildesley schreef op ma 31-01-2022 om 02:59 [+0100]:
> I tried updating it but came across an unzip error, maybe unicode related. I've also noticed in my Icecat there are all these icons that are showing as random korean characters, so I wonder if my configuration is wrong somehow??:

Maybe add glibc-utf8-locales to the native-inputs of the package
definition, such that an UTF-8 locale can be installed?

Greetings,
Maxime.

[-- Attachment #2: This is a digitally signed message part --]
[-- Type: application/pgp-signature, Size: 260 bytes --]

  reply	other threads:[~2022-01-31  9:27 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 [this message]
2022-01-31 11:23     ` Brendan Tildesley
2022-01-31 12:35       ` Maxime Devos
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

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

  git send-email \
    --in-reply-to=417f2792a426652273e9558f31b13cb64b937183.camel@telenet.be \
    --to=maximedevos@telenet.be \
    --cc=53204@debbugs.gnu.org \
    --cc=arne_bab@web.de \
    --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 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.