From: Myles English <mylesenglish@gmail.com>
To: help-guix <help-guix@gnu.org>
Subject: Re: fetching git submodule using (uri (recursive? #t))
Date: Tue, 4 Jun 2019 14:40:15 +0100 [thread overview]
Message-ID: <CAO=Do-y7U7_wUi74L7w1aqcGa5-AeU-zX5Fk0EmyMBk7UX2PYQ@mail.gmail.com> (raw)
In-Reply-To: <87d0jus3nw.fsf@gmail.com>
And thanks to Ludo' too. I didn't see your mail because the thread view
doesn't seam to be able to span from one month to the next, and also I
think I got unsubscribed after getting messages saying "Your membership in
the mailing list Help-Guix has been disabled due to excessive bounces".
Myles
On Mon, 3 Jun 2019 at 23:30, Myles English <mylesenglish@gmail.com> wrote:
> on [2019-05-28] at 14:18 I wrote:
>
> > I am trying to build this package that uses git submodules but the
> > (recursive? #t) doesn't seem to have any effect.
>
> Thanks to bavier and reepca on IRC #guix who figured out this happens
> when the package definition is changed (by e.g., adding "(recursive?
> #t)") but the hash is not updated. This causes guix to think,
> reasonably, that it already has the source in /gnu/store/the_hash-etc
> because the_hash hasn't changed since the last time it was fetched.
>
> To fix, just remove the source from the store before trying again:
>
> $ guix gc -d /gnu/store/the_hash-etc
>
> (N.B. the "-d" above might have changed to "-D")
>
> Additionally, when developing a package, reepca suggested making a
> random change to the hash just so guix knows it needs to get the source
> again, and it will suggested the real hash to put in the package
> definition.
>
> Myles
>
prev parent reply other threads:[~2019-06-04 13:40 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-05-28 13:18 fetching git submodule using (uri (recursive? #t)) Myles English
2019-06-01 14:09 ` Ludovic Courtès
2019-06-03 22:30 ` Myles English
2019-06-04 13:40 ` Myles English [this message]
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='CAO=Do-y7U7_wUi74L7w1aqcGa5-AeU-zX5Fk0EmyMBk7UX2PYQ@mail.gmail.com' \
--to=mylesenglish@gmail.com \
--cc=help-guix@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.