unofficial mirror of bug-guix@gnu.org 
 help / color / mirror / code / Atom feed
From: Josselin Poiret via Bug reports for GNU Guix <bug-guix@gnu.org>
To: Andrew Tropin <andrew@trop.in>,
	Vagrant Cascadian <vagrant@reproducible-builds.org>,
	69284@debbugs.gnu.org
Subject: bug#69284: guix pull is not reproducible
Date: Sun, 10 Mar 2024 11:13:46 +0100	[thread overview]
Message-ID: <87h6hemm1x.fsf@jpoiret.xyz> (raw)
In-Reply-To: <87r0gjre60.fsf@trop.in>

[-- Attachment #1: Type: text/plain, Size: 1055 bytes --]

Hi Andrew,

Andrew Tropin via Bug reports for GNU Guix <bug-guix@gnu.org> writes:

> I don't think that hash of the profile depends on the building process
> itself.  And it seems on the same system it returns the same result on
> consequent rebuilds.  It seems something leaks from the environment.

Yes, it's rather that the .drv themselves are not reproducible
apparently.  Can you compare the derivations building the guixes in the
different profiles?  You can look at them using first `guix gc
--derivers` on the profile and then analyzing the .drv manually.  I
remember seeing the same thing, but I don't really remember anything
conclusive.

One thing I can say is that Guix generates the .drv dynamically by
looking at the check-out.  If the checkout is somehow tainted (as it has
often happened, maybe because of libgit2?), the .drv can end up being
different.  If you retry by first resetting the Guix checkouts in
~/.cache/guix/checkouts/ to a pristine state, do you still get a
discrepancy?

Best,
-- 
Josselin Poiret

[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 682 bytes --]

  reply	other threads:[~2024-03-10 10:14 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-02-20 10:51 bug#69284: guix pull is not reproducible Andrew Tropin via Bug reports for GNU Guix
2024-03-07 20:45 ` Vagrant Cascadian
2024-03-07 20:53   ` Vagrant Cascadian
2024-03-09  8:40   ` Andrew Tropin via Bug reports for GNU Guix
2024-03-10 10:13     ` Josselin Poiret via Bug reports for GNU Guix [this message]
2024-04-08 12:49       ` Andrew Tropin via Bug reports for GNU Guix
2024-04-08 13:55         ` Simon Tournier

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=87h6hemm1x.fsf@jpoiret.xyz \
    --to=bug-guix@gnu.org \
    --cc=69284@debbugs.gnu.org \
    --cc=andrew@trop.in \
    --cc=dev@jpoiret.xyz \
    --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).