From: Pjotr Prins <pjotr.public12@thebird.nl>
To: "Ludovic Courtès" <ludo@gnu.org>
Cc: guix-devel <guix-devel@gnu.org>
Subject: Guix build output insufficient
Date: Tue, 11 Sep 2018 10:26:53 +0200 [thread overview]
Message-ID: <20180911082653.27gmposcatilbsuq@thebird.nl> (raw)
On latest
./pre-inst guix package -i something
The new color scheme is nice for output. But I miss the old build
logs. How do I get them back? Trying different verbosity levels does
not help.
Also when I got the hash wrong I did not display the new hash value.
And -K does not show the tmp location. E.g.
./pre-inst-env guix package -p ~/opt/gdc -i gdc --substitute-urls="https://berlin.guixsd.org https://mirror.hydra.gnu.org" -K
(...)
Build failed: /gnu/store/85salmra99rwz6ifpmswvd9kc5cl69gv-gdc-7a5dbd1.drv - 1 r:sha256 hash mismatch for output path `/gnu/store/wk3sm5krg5srrdivfsjvsz5snd2nqipg-gdc-7a5dbd1'
expected: 0i0yrcpqrbghq1ddp2zbqq4anl3z5l9fp9b7kblf40642pbdg49d
actual:
-guix package: error: build failed: build of `/gnu/store/wp5wr8f4xnc69amc1g8mfb7ypipx5gz0-gdc-v2.082.0-rc.1.drv' failed
Note both points. Am I doing something wrong?
Pj.
next reply other threads:[~2018-09-11 8:27 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-09-11 8:26 Pjotr Prins [this message]
2018-09-11 9:04 ` Guix build output insufficient Pjotr Prins
2018-09-11 9:55 ` Danny Milosavljevic
2018-09-11 10:41 ` Pierre Neidhardt
2018-09-11 11:59 ` Devan Carpenter
2018-09-11 11:52 ` Ricardo Wurmus
2018-09-11 14:23 ` Danny Milosavljevic
2018-09-12 6:52 ` Ricardo Wurmus
2018-09-12 15:25 ` Pjotr Prins
2018-09-13 6:45 ` Pjotr Prins
2018-09-13 7:23 ` Ricardo Wurmus
2018-09-12 17:09 ` Ludovic Courtès
2018-09-12 17:25 ` Ricardo Wurmus
2018-09-12 17:34 ` Tobias Geerinckx-Rice
2018-09-12 17:42 ` Tobias Geerinckx-Rice
2018-09-12 17:52 ` Ricardo Wurmus
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=20180911082653.27gmposcatilbsuq@thebird.nl \
--to=pjotr.public12@thebird.nl \
--cc=guix-devel@gnu.org \
--cc=ludo@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).