unofficial mirror of bug-guix@gnu.org 
 help / color / mirror / code / Atom feed
From: "Ludovic Courtès" <ludo@gnu.org>
To: zimoun <zimon.toutoune@gmail.com>
Cc: 21803@debbugs.gnu.org
Subject: bug#21803: Bug #21803 Hunting: status?
Date: Wed, 13 Nov 2019 14:42:13 +0100	[thread overview]
Message-ID: <87sgmropu2.fsf@gnu.org> (raw)
In-Reply-To: <CAJ3okZ35r-9X-CwM4OBP8bSkuf4zdbKWkWB8hCpy0R0idjrT9Q@mail.gmail.com> (zimoun's message of "Tue, 12 Nov 2019 21:44:18 +0100")

Hello,

zimoun <zimon.toutoune@gmail.com> skribis:

> From my test with Guix d258d9c7d222e6b64531c14293f41bd8d62ea4f7,
> "guix challenge guitarix" and "guix build --rounds=3" do not report
> issues about reproducibility.
>
> And from my knowledge, the waf-based packages are not affected.
>
> Do you agree to close this bug since it is not relevant anymore?

If you’ve checked that a local build gives the same result several times
in a row (make sure it actually rebuilt things; “guix build --rounds=3
foo” does nothing if “foo” is already in the store), then you can
definitely close it!

Thanks,
Ludo’.

  reply	other threads:[~2019-11-13 13:43 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-11-01 10:30 bug#21803: Guitarix builds non-deterministically Ludovic Courtès
2019-11-12 20:44 ` bug#21803: Bug #21803 Hunting: status? zimoun
2019-11-13 13:42   ` Ludovic Courtès [this message]
2019-11-13 18:14     ` zimoun
2019-11-14 21:09       ` Ludovic Courtès
2019-11-15 11:53         ` zimoun
2019-11-15 15:35           ` bug#21803: other waf non reproducible: mpv and ardour zimoun
2019-11-15 19:46           ` bug#21803: guitarix non-reproducible hard to reproduce zimoun
2019-11-16 16:12             ` Ludovic Courtès
2019-11-18 18:18               ` zimoun
2019-11-18 20:29                 ` Ludovic Courtès
2020-09-11 13:57 ` bug#21803: Guitarix builds non-deterministically zimoun
2020-09-11 16:48   ` Maxim Cournoyer

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=87sgmropu2.fsf@gnu.org \
    --to=ludo@gnu.org \
    --cc=21803@debbugs.gnu.org \
    --cc=zimon.toutoune@gmail.com \
    /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).