From: Nils Gillmann <niasterisk@grrlz.net>
To: Leo Famulari <leo@famulari.name>
Cc: help-guix@gnu.org
Subject: Re: developing for guix with git
Date: Wed, 03 Feb 2016 01:51:49 +0100 [thread overview]
Message-ID: <87lh72haze.fsf@grrlz.net> (raw)
In-Reply-To: <20160202235642.GA25435@jasmine> (Leo Famulari's message of "Tue, 2 Feb 2016 18:56:42 -0500")
Leo Famulari <leo@famulari.name> writes:
> On Tue, Feb 02, 2016 at 10:28:25PM +0100, Nils Gillmann wrote:
>> Ricardo Wurmus <rekado@elephly.net> writes:
>>
>> > Nils Gillmann <niasterisk@grrlz.net> writes:
>> >
>> >> Do you happen to know why guix in the situation I described,
>> >> being on an up to date branch following master refuses to build,
>> >> but once I switch to master branch, make clean, make clean-go (or
>> >> go-clean?) and run make (and the other commands) again it builds
>> >> successfully? This was my initial confusion.
>> >
>> > It’s hard to say without being able to take a look at the state of the
>> > branch. It is possible that a change you introduced in your branch
>> > broke things. Maybe you could share error messages?
>>
>> I'll inline all the things here now:
>
> [...]
>
>> ;;; ERROR: Unbound variable: git-fetch
>
> Did you import (guix git-download)?
I am not sure.
Adding to the Email I just wrote to this thread, how would I do this?
Isn't 'guix environment guix git' taking care of that already?
Or is this git-fetch message entirely related to the file (lisp.scm) I am
working on where I might have forgotten to add (guix git-download)?
I'll investigate further tomorrow.
Thanks,
--
ng/ni*
vcard: http://krosos.sdf.org
next prev parent reply other threads:[~2016-02-03 0:51 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-01-28 11:31 developing for guix with git Ni* Gillmann
2016-01-28 20:29 ` Efraim Flashner
2016-01-31 16:56 ` Nils Gillmann
2016-01-31 23:49 ` Ricardo Wurmus
2016-02-02 21:28 ` Nils Gillmann
2016-02-02 23:56 ` Leo Famulari
2016-02-03 0:51 ` Nils Gillmann [this message]
2016-02-03 6:58 ` Ricardo Wurmus
2016-02-03 11:24 ` Nils Gillmann
2016-02-03 12:00 ` Nils Gillmann
2016-02-03 0:46 ` Nils Gillmann
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=87lh72haze.fsf@grrlz.net \
--to=niasterisk@grrlz.net \
--cc=help-guix@gnu.org \
--cc=leo@famulari.name \
/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.
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).