unofficial mirror of guix-devel@gnu.org 
 help / color / mirror / code / Atom feed
From: "Ludovic Courtès" <ludovic.courtes@inria.fr>
To: zimoun <zimon.toutoune@gmail.com>
Cc: Guix Devel <guix-devel@gnu.org>
Subject: Re: Unreproducible «When Docker images become fixed-point»?
Date: Mon, 04 Jul 2022 15:37:42 +0200	[thread overview]
Message-ID: <87edz1ati1.fsf@inria.fr> (raw)
In-Reply-To: 875ykzxlwx.fsf@gmail.com

Hello,

zimoun <zimon.toutoune@gmail.com> skribis:

> The pack built by the post is:
>
> /gnu/store/6rga6pz60di21mn37y5v3lvrwxfvzcz9-python-python-numpy-docker-pack.tar.gz
>
> comparing with today, using 9d795fb and the time-machine:
>
> $ guix time-machine -C /tmp/channels.scm \
>        -- pack -f docker --save-provenance -m /tmp/manifest.scm
>
> /gnu/store/ryqvz83s11qb96d9i6ywv08vcshg6k17-python-python-numpy-docker-pack.tar.gz

I have this:

--8<---------------cut here---------------start------------->8---
$ guix time-machine --commit=fb32a38db1d3a6d9bc970e14df5be95e59a8ab02 -- pack -f docker --save-provenance python python-numpy -d
/gnu/store/7kxwhszfvqxcryfid7n9fk4mamaxrwky-python-python-numpy-docker-pack.tar.gz.drv
$ guix time-machine --commit=fb32a38db1d3a6d9bc970e14df5be95e59a8ab02 -- pack -f docker --save-provenance python python-numpy 
/gnu/store/ryqvz83s11qb96d9i6ywv08vcshg6k17-python-python-numpy-docker-pack.tar.gz
$ guix hash $(guix time-machine --commit=fb32a38db1d3a6d9bc970e14df5be95e59a8ab02 -- pack -f docker --save-provenance python python-numpy )
1zn7kx2nj5ly8kcdl6lw0l8v1428ldg88j5zs7wyjxl27qz1kdrx
$ guix describe
Generation 221  Jul 03 2022 23:52:07    (current)
  guix e069de4
    repository URL: https://git.savannah.gnu.org/git/guix.git
    branch: master
    commit: e069de452a2c923868f5137421b4b6349c38d754
--8<---------------cut here---------------end--------------->8---

Do you still have the original tarball mentioned in the post?

A possible reason why we’re building a different derivation than back
then is provenance info: as explained under ‘--save-provenance’ in the
manual, provenance info is not “canonical” and we could end up including
different provenance info.  I don’t have any clear scenario in mind but
that sounds plausible.

Thanks,
Ludo’.


  reply	other threads:[~2022-07-04 14:24 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-06-17 17:03 Unreproducible «When Docker images become fixed-point»? zimoun
2022-07-04 13:37 ` Ludovic Courtès [this message]
2022-07-04 23:12   ` zimoun
2022-07-05  7:44     ` Ludovic Courtès
2022-07-05 10:38       ` zimoun

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=87edz1ati1.fsf@inria.fr \
    --to=ludovic.courtes@inria.fr \
    --cc=guix-devel@gnu.org \
    --cc=zimon.toutoune@gmail.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.
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).