From: Vagrant Cascadian <vagrant@debian.org>
To: guix-devel@gnu.org
Subject: "make dist" fails ... en@boldquote: warning: PO file headder missing or invalid
Date: Fri, 07 Jan 2022 14:43:31 -0800 [thread overview]
Message-ID: <87zgo7w4j0.fsf@ponder> (raw)
[-- Attachment #1: Type: text/plain, Size: 1504 bytes --]
Trying to run "make dist" from Debian running guix... but it fails.
nckx confirmed to have similar issues.
$ guix shell --container --pure --development guix guix git imagemagick perl less glibc glibc-locales
...
$ export LC_ALL=en_US.UTF-8 LANG=en_US.UTF-8 # ensure UTF-8 locale available in guix
$ git clean -dfx # remove any potential cruft
...
$ ./bootstrap && ./configure --localstatedir=/var && make -j1 dist
...
rm -f en@boldquot.gmo &&
/gnu/store/z2y9851y1w2r8j8ipkvk0nhhczw8qgci-profile/bin/msgfmt -c
--statistics --verbose -o en@boldquot.gmo en@boldquot.po
/gnu/store/z2y9851y1w2r8j8ipkvk0nhhczw8qgci-profile/bin/msgfmt:
en@boldquot.po: warning: PO file header missing or invalid
warning:
charset
conversion
will
not
work
/gnu/store/z2y9851y1w2r8j8ipkvk0nhhczw8qgci-profile/bin/msgfmt: found 1
fatal error
I've also in the past implored to set up a ci job for "make dist" to
make it at least easier to figure out which commits trigger these
issues... how can I help move that forward? :)
live well,
vagrant
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 227 bytes --]
next reply other threads:[~2022-01-07 22:44 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-01-07 22:43 Vagrant Cascadian [this message]
2022-01-08 0:40 ` "make dist" fails ... en@boldquote: warning: PO file headder missing or invalid Vagrant Cascadian
2022-01-08 2:22 ` "make dist" fails Vagrant Cascadian
2022-01-10 13:39 ` "make dist" fails ... en@boldquote: warning: PO file headder missing or invalid zimoun
2022-01-10 15:22 ` Mathieu Othacehe
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=87zgo7w4j0.fsf@ponder \
--to=vagrant@debian.org \
--cc=guix-devel@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).