From: Arun Isaac <arunisaac@systemreboot.net>
To: Ricardo Wurmus <rekado@elephly.net>
Cc: 36415@debbugs.gnu.org
Subject: [bug#36415] [PATCH] gnu: Add qlogo.
Date: Thu, 04 Jul 2019 22:41:10 +0530 [thread overview]
Message-ID: <cu7h881209d.fsf@systemreboot.net> (raw)
In-Reply-To: <878stgvmze.fsf@elephly.net>
[-- Attachment #1: Type: text/plain, Size: 1277 bytes --]
>> I don't know. I have never understood how reproducibility checking works
>> in Guix. Shouldn't --rounds=2 cause `guix build' to error out if there
>> is some non-determinism?
>
> Yes.
>
> This might be a regression.
>
> Build being reported as “in progress” is a feature. It’s used to
> indicate remaining builds when more than one thing is being built.
>
> In this case, though, it seems like a bug.
Ok.
> To test for reproducibility in this case you may want to use “--check”
> after building the thing once.
With `guix build --no-grafts --check qlogo', I get no error. I assume
that means qlogo is reproducible.
Without '--no-grafts', I just see a graft happening, qlogo is not
rebuilt. Output without '--no-grafts' follows.
The following graft will be made:
/gnu/store/vamlyscnwndzmq66whrd71ww31jnrz7v-qlogo-0.92.drv
applying 2 grafts for /gnu/store/vamlyscnwndzmq66whrd71ww31jnrz7v-qlogo-0.92.drv...
grafting '/gnu/store/hmnchnawfv8ngl4wh15ni3ychr5ccb9w-qlogo-0.92' -> '/gnu/store/85lialf1aich7b51a77afj187qk32n7h-qlogo-0.92'...
successfully built /gnu/store/vamlyscnwndzmq66whrd71ww31jnrz7v-qlogo-0.92.drv
/gnu/store/85lialf1aich7b51a77afj187qk32n7h-qlogo-0.92
If there's nothing else, may I push qlogo to master?
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 487 bytes --]
next prev parent reply other threads:[~2019-07-04 17:12 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-06-28 8:03 [bug#36415] [PATCH] gnu: Add qlogo Arun Isaac
2019-06-28 16:35 ` swedebugia
2019-07-02 8:36 ` Arun Isaac
2019-07-02 8:50 ` Ricardo Wurmus
2019-07-04 17:11 ` Arun Isaac [this message]
2019-07-04 19:30 ` Ricardo Wurmus
2019-07-05 7:59 ` bug#36415: " Arun Isaac
2019-07-02 7:21 ` [bug#36415] " Efraim Flashner
2019-07-04 16:40 ` Arun Isaac
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=cu7h881209d.fsf@systemreboot.net \
--to=arunisaac@systemreboot.net \
--cc=36415@debbugs.gnu.org \
--cc=rekado@elephly.net \
/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).