From: HiPhish <hiphish@posteo.de>
To: 49145@debbugs.gnu.org
Subject: bug#49145: Cannot build Guix (Texinfo failure)
Date: Fri, 25 Jun 2021 22:26:51 +0000 [thread overview]
Message-ID: <4350643.LvFx2qVVIh@titan> (raw)
In-Reply-To: <4629869.GXAFRqVoOG@titan>
I actually looked into the offending files and I found that they are only half-
translated. Part of them is in German, but some parts are in English, and the
English parts are referencing English node names, which obviously do not exist
in the German manual.
I do not need the German manual, is there a way to skip it? A quick glance
shows the same problem in the Spanish manual as well, and other manuals are
probably affected as well. I don't know why `make` only choked up on the German
manual though. Maybe because that's the first one in alphabetical order and
`make` did not bother trying the rest? Or could it be because my machine is in
Germany? The output of the `locale` command is:
$ locale
LANG=en_GB.UTF-8
LC_CTYPE="en_GB.UTF-8"
LC_NUMERIC="en_GB.UTF-8"
LC_TIME="en_GB.UTF-8"
LC_COLLATE=C
LC_MONETARY="en_GB.UTF-8"
LC_MESSAGES="en_GB.UTF-8"
LC_PAPER="en_GB.UTF-8"
LC_NAME="en_GB.UTF-8"
LC_ADDRESS="en_GB.UTF-8"
LC_TELEPHONE="en_GB.UTF-8"
LC_MEASUREMENT="en_GB.UTF-8"
LC_IDENTIFICATION="en_GB.UTF-8"
LC_ALL=
And when inside a pure Guix environment:
$ locale
LANG=
LC_CTYPE="POSIX"
LC_NUMERIC="POSIX"
LC_TIME="POSIX"
LC_COLLATE="POSIX"
LC_MONETARY="POSIX"
LC_MESSAGES="POSIX"
LC_PAPER="POSIX"
LC_NAME="POSIX"
LC_ADDRESS="POSIX"
LC_TELEPHONE="POSIX"
LC_MEASUREMENT="POSIX"
LC_IDENTIFICATION="POSIX"
LC_ALL=
next prev parent reply other threads:[~2021-06-25 22:28 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-06-20 21:37 bug#49145: Cannot build Guix (Texinfo failure) HiPhish
2021-06-22 12:06 ` Julien Lepiller
2021-06-22 17:18 ` HiPhish
2021-06-25 22:26 ` HiPhish [this message]
2021-06-26 10:58 ` Julien Lepiller
2021-06-28 21:27 ` HiPhish
2021-07-09 16:21 ` HiPhish
2021-11-10 21:33 ` bug#49145: Solved, I guess HiPhish
2021-11-11 15:59 ` Maxim Cournoyer
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=4350643.LvFx2qVVIh@titan \
--to=hiphish@posteo.de \
--cc=49145@debbugs.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.