unofficial mirror of guix-devel@gnu.org 
 help / color / mirror / code / Atom feed
From: "Ludovic Courtès" <ludo@gnu.org>
To: Maxime Devos <maximedevos@telenet.be>
Cc: guix-devel@gnu.org
Subject: Re: Rust reprodubility -- .rmeta and shadow-rs
Date: Thu, 30 Jun 2022 13:35:15 +0200	[thread overview]
Message-ID: <87h7428jv0.fsf@gnu.org> (raw)
In-Reply-To: <60c35901007af0f3bf02f23814d49973e0c13772.camel@telenet.be> (Maxime Devos's message of "Sun, 26 Jun 2022 09:54:29 +0200")

Hello!

Maxime Devos <maximedevos@telenet.be> skribis:

> There was some mail about irreproducibility in Rust, but I couldn't
> find it anymore.  Anyway, I found a potential cause: rust-shadow-rs
> embeds timestamps (even though it nominally respects
> SOURCE_DATE_EPOCH???) and the ordering of definitions it generates is
> based on a hash map (and hence, irreproducible).

I found these:

  https://issues.guix.gnu.org/50015
  https://issues.guix.gnu.org/55928

> The crate id is based on a hash over the source code, so this
> irreproducibility can cause build failures if substitutes are used.
>
> By removing the time stamp and sorting the definitions, 'nushell'
> successfully built on ci.guix.gnu.org whereas it previously failed to
> build on ci.guix.gnu.org but built successfully locally (with
> antioxidant), and IIRC the (antioxidated) 'rust-nu-command' is now
> reproducible:
>
> Anyway, here the patch I used:
>
>     ("rust-shadow-rs"
>      ,#~((add-after 'unpack 'fixup-source-date-epoch
> 	   (lambda _
> 	     ;; TODO: it nominally supports SOURCE_DATE_EPOCH, yet something things go wrong,
> 	     ;; as the shadow.rs still contains the unnormalised time stamp ...
> 	     ;; For now, do a work-around.
> 	     (substitute* '("src/lib.rs" "src/env.rs")
> 	       (("BuildTime::Local\\(Local::now\\(\\)\\)\\.human_format\\(\\)")
> 		(object->string "[timestamp expunged for reproducibility]"))
> 	       (("time\\.human_format\\(\\)")
> 		"\"[timestamp expunged for reproducibility]\".to_string()")
> 	       (("time\\.to_rfc3339_opts\\(SecondsFormat::Secs, true)")
> 		"\"[timestamp expunged for reproducibility]\".to_string()")
> 	       (("time\\.to_rfc2822\\(\\)")
> 		"\"[timestamp expunged for reproducibility]\".to_string()"))))
> 	 (add-after 'unpack 'more-reproducibility ;; by default, it uses a hashmap, leading to an irreproducible ordering in shadow.rs and hence an irreproducible .rmeta (TODO: upstream?)
> 	   (lambda _
> 	     (substitute* "src/lib.rs" ; sort
> 	       (("\\(k, v\\) in self\\.map\\.clone\\(\\)")
> 		"(k, v) in std::collections::BTreeMap::from_iter(self.map.clone().iter())")
> 	       (("self\\.write_const\\(k, v\\)") "self.write_const(k, v.clone())")
> 	       (("self\\.map\\.keys\\(\\)") "std::collections::BTreeSet::from_iter(self.map.keys())"))))))
>
> Maybe that was the cause?

You mean this issue you identified could have been the cause of
reproducibility issues found in other Rust packages?

Anyway, it looks like the snippet above should be applied to
‘rust-shadow-rs’ in current ‘master’, no?

Thanks,
Ludo’.


  reply	other threads:[~2022-06-30 12:26 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 [this message]
2022-06-30 11:45   ` Maxime Devos

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=87h7428jv0.fsf@gnu.org \
    --to=ludo@gnu.org \
    --cc=guix-devel@gnu.org \
    --cc=maximedevos@telenet.be \
    /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).