From: Julien Lepiller <julien@lepiller.eu>
To: Josselin Poiret <dev@jpoiret.xyz>
Cc: 60816-close@debbugs.gnu.org
Subject: bug#60816: guix pull ("computing Guix derivation") is not reproducible
Date: Sun, 15 Jan 2023 14:29:55 +0100 [thread overview]
Message-ID: <20230115142955.23248bda@sybil.lepiller.eu> (raw)
In-Reply-To: <875yd857y2.fsf@jpoiret.xyz>
Le Sun, 15 Jan 2023 12:54:45 +0100,
Josselin Poiret <dev@jpoiret.xyz> a écrit :
> Hi Julien,
>
> Julien Lepiller <julien@lepiller.eu> writes:
>
> > So, apart from the output filename which obviously changes, it seems
> > that the differences are:
> >
> > - order of dependencies,
> > - source output,
> > - builder (only because it references the source output)
> >
> > Here's the result of diffoscope on the source outputs (ignore
> > modification date, I used touch to make them all the same, not to
> > make them sensible ;)):
> >
> > [...]
> >
> > Could it be that removed files are somehow kept in cache?
>
> Does this still happen if you run `git clean -df` in both of your
> local checkouts?
>
> Best,
Haha!
it seems that on one machine, my .cache/guix/checkouts got polluted by
uncommited files. I have no idea why they're there, but cleaning them
should solve my issue, thanks!
next prev parent reply other threads:[~2023-01-15 13:31 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-01-14 18:02 bug#60816: guix pull ("computing Guix derivation") is not reproducible Julien Lepiller
2023-01-15 11:54 ` Josselin Poiret via Bug reports for GNU Guix
2023-01-15 13:29 ` Julien Lepiller [this message]
2023-01-15 14:35 ` Josselin Poiret via Bug reports for GNU Guix
2023-01-16 1:25 ` bokr
2023-01-16 11:48 ` 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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20230115142955.23248bda@sybil.lepiller.eu \
--to=julien@lepiller.eu \
--cc=60816-close@debbugs.gnu.org \
--cc=dev@jpoiret.xyz \
/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 external index
https://git.savannah.gnu.org/cgit/guix.git
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.