From: John Soo <jsoo1@asu.edu>
To: "Ludovic Courtès" <ludo@gnu.org>
Cc: help-guix <help-guix@gnu.org>
Subject: Re: guix environment with channels?
Date: Tue, 12 Mar 2019 15:26:11 +0000 [thread overview]
Message-ID: <CAKf5CqXyiiEg3e_BUaKbKcAC-eeVLRZC621bapkNRaGyifU71A@mail.gmail.com> (raw)
In-Reply-To: <CAKf5CqV2m1QxV2H0NW0HrEv7DoBVSJaD8nJicy-nXwuHyCqx2Q@mail.gmail.com>
[-- Attachment #1: Type: text/plain, Size: 1102 bytes --]
Wait! I figured it out! I need to use list instead of quote! Oops! Thanks
again!
On Tue, Mar 12, 2019 at 3:23 PM John Soo <jsoo1@asu.edu> wrote:
> Thanks Ludo!
>
> Here's the error, environment file, and guix describe output:
> https://paste.debian.net/1072838/
>
> guix package -s ghc-aeson-1.4.2.0 shows it is indeed a package in the
> system.
>
> Thanks again,
>
> John
>
>
>
> On Mon, Mar 11, 2019 at 4:11 PM Ludovic Courtès <ludo@gnu.org> wrote:
>
>> Hi John,
>>
>> John Soo <jsoo1@asu.edu> skribis:
>>
>> > I was going to do some development recently and wanted to use some
>> > packages from a channel. I have it listed as a channel under
>> > ~/.config/guix/channels.scm so I added some packages from the channel
>> > to a scheme file but guix environment -l my-file.scm told me there was
>> > no code for my channel modules. Is this intended?
>>
>> No. Could it be that you’re running a ‘guix’ command different from the
>> one ‘guix pull’ produced?
>>
>> Does ‘guix describe’ show your additional channel?
>>
>> HTH,
>> Ludo’.
>>
>
[-- Attachment #2: Type: text/html, Size: 1914 bytes --]
prev parent reply other threads:[~2019-03-12 15:26 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-03-05 7:20 guix environment with channels? John Soo
2019-03-05 7:31 ` Pierre-Henry F.
2019-03-05 14:24 ` John Soo
2019-03-11 16:11 ` Ludovic Courtès
2019-03-12 15:23 ` John Soo
2019-03-12 15:26 ` John Soo [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=CAKf5CqXyiiEg3e_BUaKbKcAC-eeVLRZC621bapkNRaGyifU71A@mail.gmail.com \
--to=jsoo1@asu.edu \
--cc=help-guix@gnu.org \
--cc=ludo@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.