unofficial mirror of bug-guix@gnu.org 
 help / color / mirror / code / Atom feed
From: Maxim Cournoyer <maxim.cournoyer@gmail.com>
To: zimoun <zimon.toutoune@gmail.com>
Cc: 21803-done@debbugs.gnu.org
Subject: bug#21803: Guitarix builds non-deterministically
Date: Fri, 11 Sep 2020 12:48:55 -0400	[thread overview]
Message-ID: <87wo106yyw.fsf@gmail.com> (raw)
In-Reply-To: <877dt0h0we.fsf@gmail.com> (zimoun's message of "Fri, 11 Sep 2020 15:57:05 +0200")

Hello,

[...]

> Guitarix has been updated to 0.41.0 by commit
> bf592ef506e1db0340dc11faa0514fe80793e6d6.
>
> I have tried "guix build guitarix --no-grafts --check -K" at least 10
> times without noticing an unreproducible behaviour.
>
> Could someone confirm this and then close this almost 5 years old bug?

Confirmed!

>> It would be nice to see why this happens, and whether this affects all
>> Waf-based packages.
>
> I propose to open another bug report to track the waf-based packages issues.

This sounds reasonable, given this is 5 years old and perhaps not
relevant anymore.

Closing, thank you!

Maxim




      reply	other threads:[~2020-09-11 16:49 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
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 [this message]

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=87wo106yyw.fsf@gmail.com \
    --to=maxim.cournoyer@gmail.com \
    --cc=21803-done@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).