all messages for Guix-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: Arun Isaac <arunisaac@systemreboot.net>
To: swedebugia <swedebugia@riseup.net>, 36415@debbugs.gnu.org
Subject: [bug#36415] [PATCH] gnu: Add qlogo.
Date: Tue, 02 Jul 2019 14:06:01 +0530	[thread overview]
Message-ID: <cu7tvc425qm.fsf@systemreboot.net> (raw)
In-Reply-To: <faf7e83c-aee5-1ce6-0c7e-84aded7449ea@riseup.net>

[-- Attachment #1: Type: text/plain, Size: 1021 bytes --]


> I got this when running rounds=2:
> The following builds are still in progress:
>    /gnu/store/yv7gjrplyym3arqi6qqiiqy3l4wzszp3-qlogo-0.92.drv
>    /gnu/store/ivln0c98vr9n8j25alx1dg1gbzpja11k-qtbase-5.11.3.drv
>    /gnu/store/ysv72wwn0gfjiqx2y4rxbf0gnhiv94yp-cups-2.2.11.drv
>    /gnu/store/mimhpwdwik9madwir21a2d0z6i1in7j0-cups-filters-1.23.0.drv
>    /gnu/store/syc8fwdl3mz2kxncd1k2mkqq4mslvxyv-qlogo-0.92.drv

I get a similar message too.

> I'm interpreting this as qlogo is not reproducible, no?

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? In the above case, `guix build' is not erroring
out. It is merely saying that "the following builds are still in
progress". I don't know how to interpret that.

Any pointers about how to proceed with debugging this further would be
very helpful. I've tried reading the relevant sections in the manual,
but I didn't find any insight. :-(

Thanks!

[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 487 bytes --]

  reply	other threads:[~2019-07-02  8:37 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 [this message]
2019-07-02  8:50     ` Ricardo Wurmus
2019-07-04 17:11       ` Arun Isaac
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

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=cu7tvc425qm.fsf@systemreboot.net \
    --to=arunisaac@systemreboot.net \
    --cc=36415@debbugs.gnu.org \
    --cc=swedebugia@riseup.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 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.