From: ludo@gnu.org (Ludovic Courtès)
To: "Björn Höfling" <bjoern.hoefling@bjoernhoefling.de>
Cc: guix-devel@gnu.org
Subject: Re: hg-fetch with subrepos
Date: Sun, 02 Dec 2018 14:58:52 +0100 [thread overview]
Message-ID: <87mupoowrn.fsf@gnu.org> (raw)
In-Reply-To: <20181202115355.51c943b5@alma-ubu> ("Björn Höfling"'s message of "Sun, 2 Dec 2018 11:53:55 +0100")
Hello,
Björn Höfling <bjoern.hoefling@bjoernhoefling.de> skribis:
> And I stumbled upon that problem too. Ludovic explained me on IRC: The
> problem is the metadata directory ".hg": It contains metadata that is
> not fixed. For normal hg-repositories, it will be stripped away, but
> not recursively for those with sub-repos.
>
> I have a patch that works. I just wasn't sure if it goes to master or
> to staging, as it could affect the java-packages as well.
Such a patch can go to ‘master’: it won’t trigger any rebuild because,
by definition, the content hash of an ‘origin’ is known in advance
(these are “fixed-output derivations.”)
However, we should audit current uses of ‘hg-fetch’ with recursive
sub-repos because there hashes are most likely wrong already.
> I'm attaching what I have here, will prepare an official patch tonight
> or tomorrow.
Awesome. FWIW this patch already LGTM. :-)
Thanks,
Ludo’.
next prev parent reply other threads:[~2018-12-02 13:58 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-12-01 19:10 hg-fetch with subrepos John Soo
2018-12-02 10:53 ` Björn Höfling
2018-12-02 13:58 ` Ludovic Courtès [this message]
2018-12-02 18:38 ` John Soo
2018-12-03 12:03 ` Björn Höfling
2018-12-12 2:08 ` bug#33712: Some Mercurial checkouts probably have incorrect hashes [was Re: hg-fetch with subrepos] Leo Famulari
2020-03-22 20:59 ` bug#33712: Some Mercurial checkouts probably have incorrect hashes Leo Famulari
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=87mupoowrn.fsf@gnu.org \
--to=ludo@gnu.org \
--cc=bjoern.hoefling@bjoernhoefling.de \
--cc=guix-devel@gnu.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 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.