unofficial mirror of help-guix@gnu.org 
 help / color / mirror / Atom feed
From: phodina via <help-guix@gnu.org>
To: help-guix <help-guix@gnu.org>
Subject: Non deterministic package
Date: Wed, 04 Aug 2021 19:14:16 +0000	[thread overview]
Message-ID: <YqasBX9uhQoCktxucpydDc2-PC7clf8EiChfWS8C9JGvcr6Ii9nlr_ZMRM5i3_u4IVOdvMvMXgYs2jgkVsVvsc01TU3dqScZwP1uZcsh3aQ=@protonmail.com> (raw)

Hi,

I came across a package in the Guix repository which fails to build. The package in question here is rust-brotli-sys-0.3. So the obvious question comes up. How does this happen?

I just ran =guix build rust-brotli-sys= with the following output:

...
phase `reset-gzip-timestamps' succeeded after 0.0 seconds
starting phase `compress-documentation'
phase `compress-documentation' succeeded after 0.0 seconds
guix build: error: derivation `/gnu/store/kf8kwl7yn8jqpwc9p97bw8vs5g5bvas4-rust-brotli-sys-0.3.2.drv' may not be deterministic: output `/gnu/store/yrrdr6rrc1s4b9lf7wz40c2gnv5kvxff-rust-brotli-sys-0.3.2' differs
Also this is my guix channel:

guix:
repository URL: https://git.savannah.gnu.org/git/guix.git
branch: master
commit: b95fb85f593d377864fc1bfb3c118e54d03783be

I tried to run the build with the flag --check and multiple rounds, but got the same result.
So could it be caused by not running =./pre-inst-env guix build --rounds=2 <PKG>= when submitting the patch?

Or when somebody updates some pkg that this pkg depends on and does not run =./pre-inst-env guix --refresh --list-dependent= and then check the dependent pkgs?

Could also sombody please share what kind of CI pipeline is there implemented on applying the patch on the mainter's side?

Thanks
Petr

PS: Yes, I do have more questions regading how Guix works lately. I tried to search the mailing list but haven't found answers to them

             reply	other threads:[~2021-08-04 19:14 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-08-04 19:14 phodina via [this message]
2021-08-04 19:50 ` Non deterministic package Julien Lepiller
2021-08-05  7:52   ` Efraim Flashner
2021-08-09 15:13     ` phodina

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='YqasBX9uhQoCktxucpydDc2-PC7clf8EiChfWS8C9JGvcr6Ii9nlr_ZMRM5i3_u4IVOdvMvMXgYs2jgkVsVvsc01TU3dqScZwP1uZcsh3aQ=@protonmail.com' \
    --to=help-guix@gnu.org \
    --cc=phodina@protonmail.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. 
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).