From: Maxime Devos <maximedevos@telenet.be>
To: "Ludovic Courtès" <ludo@gnu.org>
Cc: guix-devel@gnu.org
Subject: Re: Rust reprodubility -- .rmeta and shadow-rs
Date: Thu, 30 Jun 2022 13:45:28 +0200 [thread overview]
Message-ID: <6eb03470c647b4fa0d556b901af984ecf97d49b7.camel@telenet.be> (raw)
In-Reply-To: <87h7428jv0.fsf@gnu.org>
[-- Attachment #1: Type: text/plain, Size: 1218 bytes --]
> https://issues.guix.gnu.org/50015
I don't think that shadow-rs changes Cargo.toml, so I think that one is
a separate issue ...
> https://issues.guix.gnu.org/55928
Maybe related, though .rmeta isn't mentioned there so maybe not.
Seems debugging information related, so maybe the report at (and fix
at)
https://github.com/rust-lang/rust/issues/34902#issuecomment-565557076
is important there.
Ludovic Courtès schreef op do 30-06-2022 om 13:35 [+0200]:
> > Anyway, here the patch I used:
> >
> > [...]
> >
> > Maybe that was the cause?
>
> You mean this issue you identified could have been the cause of
> reproducibility issues found in other Rust packages?
I don't know if it applies to leaf packages or only to dependencies,
but perhaps!
> Anyway, it looks like the snippet above should be applied to
> ‘rust-shadow-rs’ in current ‘master’, no?
Yes -- also, upstream has a patch now!
<https://github.com/baoyachi/shadow-rs/pull/97>
That's only for the ordering, not the timestamps, though.
The timestamp issue might be caused due to how antioxidant replaces
some inputs and fiddles with ‘features’ so I haven't reported that yet
....
Greetings,
Maxime.
[-- Attachment #2: This is a digitally signed message part --]
[-- Type: application/pgp-signature, Size: 260 bytes --]
prev parent reply other threads:[~2022-06-30 11:59 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-06-26 7:54 Rust reprodubility -- .rmeta and shadow-rs Maxime Devos
2022-06-30 11:35 ` Ludovic Courtès
2022-06-30 11:45 ` Maxime Devos [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=6eb03470c647b4fa0d556b901af984ecf97d49b7.camel@telenet.be \
--to=maximedevos@telenet.be \
--cc=guix-devel@gnu.org \
--cc=ludo@gnu.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).