From: Vagrant Cascadian <vagrant@debian.org>
To: guix-devel@gnu.org
Subject: "make dist" broken by German cookbook translation
Date: Fri, 06 Mar 2020 11:19:27 -0800 [thread overview]
Message-ID: <87sgilfg00.fsf@yucca> (raw)
[-- Attachment #1: Type: text/plain, Size: 1235 bytes --]
It looks like the commit adding the German translation for the cookbook
f98e83a17fa30587520e858231ec9c61f3624ecd broke "make dist".
in an environment built using:
guix environment --pure guix --ad-hoc git imagemagick
running:
./bootstrap && ./configure --localstatedir=/var && make -j4 && make doc-pot-update && make -j4 dist
Results in:
make[1]: Leaving directory '/home/vagrant/src/guix-tarball'
for f in po/doc/guix-manual.de.po; do
\
lang="`echo "$f" |
/gnu/store/zsq3ficl0hmid7aw50qma1ixmbs0jzq9-profile/bin/sed
-es'|.*/guix-cookb\
ook\.\(.*\)\.po$|\1|g'`"; \
make "doc-po-update-cookbook-$lang";
\
done
make[1]: Entering directory '/home/vagrant/src/guix-tarball'
make[1]: *** No rule to make target
'doc-po-update-cookbook-po/doc/guix-manual.de.po'. Stop.
make[1]: Leaving directory '/home/vagrant/src/guix-tarball'
make: *** [Makefile:5735: doc-po-update] Error 2
I haven't tracked down how to fix it properly, but it looks like maybe
some rules from guix-manual maybe were copied from the cookbook without
sufficiently being adjusted?
Reverting the commit works around the issue and generates a tarball,
though with the obvious downside of the German translation missing.
live well,
vagrant
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 227 bytes --]
next reply other threads:[~2020-03-06 19:19 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-03-06 19:19 Vagrant Cascadian [this message]
2020-03-06 20:57 ` "make dist" broken by German cookbook translation pelzflorian (Florian Pelz)
2020-03-06 23:33 ` Vagrant Cascadian
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=87sgilfg00.fsf@yucca \
--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).