unofficial mirror of bug-guix@gnu.org 
 help / color / mirror / code / Atom feed
From: Maxim Cournoyer <maxim.cournoyer@gmail.com>
To: Vagrant Cascadian <vagrant@reproducible-builds.org>
Cc: 68748@debbugs.gnu.org
Subject: bug#68748: cuirass is not reproducible
Date: Sat, 09 Mar 2024 13:06:47 -0500	[thread overview]
Message-ID: <8734szffew.fsf@gmail.com> (raw)
In-Reply-To: <87edclojd6.fsf@wireframe> (Vagrant Cascadian's message of "Thu,  07 Mar 2024 12:52:05 -0800")

Hi Vagrant,

Vagrant Cascadian <vagrant@reproducible-builds.org> writes:

> On 2024-01-26, Maxim Cournoyer wrote:
>> Maxim Cournoyer <maxim.cournoyer@gmail.com> writes:
>>> Building cuirass with 'guix build --no-grafts --check -K cuirass' shows
>>> it has differences.  Then running
>>
>> I think this is not particular to cuirass but more to any Guile package.
>> I've found similar issues with guile-git and mumi.  It seems Guile
>> has either regressed or never supported byte compiling reproducibly?
>
> This looks very much like:
>
>   https://tests.reproducible-builds.org/debian/issues/unstable/nondeterministic_ordering_in_guile_binaries_issue.html
>
> Which links to several relevent issues in debian, nix, guix, and
> opensuse:
>
>   https://bugs.debian.org/995092
>   https://github.com/NixOS/nixpkgs/pull/78778
>   https://issues.guix.gnu.org/issue/20272
>   https://build.opensuse.org/request/show/732638

Indeed, thank you.  It seems the issue is a long standing one for Guile,
as you linked above with #20272 (9 years old!).

-- 
Thanks,
Maxim




      reply	other threads:[~2024-03-09 18:08 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-01-27  3:29 bug#68748: cuirass is not reproducible Maxim Cournoyer
2024-01-27  4:07 ` Maxim Cournoyer
2024-03-07 20:52   ` Vagrant Cascadian
2024-03-09 18:06     ` 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=8734szffew.fsf@gmail.com \
    --to=maxim.cournoyer@gmail.com \
    --cc=68748@debbugs.gnu.org \
    --cc=vagrant@reproducible-builds.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).