From: Kaelyn <kaelyn.alexi@protonmail.com>
To: "B. Wilson" <elaexuotee@wilsonb.com>
Cc: guix-devel@gnu.org
Subject: Re: Error pulling custom channel that includes another third-party channel
Date: Fri, 15 Apr 2022 15:24:03 +0000 [thread overview]
Message-ID: <v08Q-57PINrhiGv4iyMBzCL5YqD8LBXgV7ZEzOVcqoVSt7UxzY6vGP0Ei-g7kp0siXq2hXlYCJrYuQjh2noi3UWDdTq4i9TECgZHapRtgzM=@protonmail.com> (raw)
In-Reply-To: <3FTWY74E0IXDQ.2Q44GE2Y7QQQ5@"@WILSONB.COM>
------- Original Message -------
On Wednesday, April 13th, 2022 at 4:29 PM, B. Wilson <elaexuotee@wilsonb.com> wrote:
> Hey Guix,
>
> In my channels.scm, in addition to the primary guix channel I have my-channel
> and other-channel. This has worked just fine, until I added a commit in
> my-channel which use-modules something from other-channel.
>
> Now guix pull fails when attempting to build my-channel:
>
> (exception misc-error (value #f) (value "no code for module ~S") (value ((other channel module))) (value #f))
>
> What am I missing?
>
> Just to be clear, locally building with `guix build -L path/to/my-channel foo`
> succeeds just fine. Is there somewhere inside my-channel where I need to
> explicitly declare the dependency on other-channel?
>
> Any help appreciated. Cheers,
>
> BW
Hello! I have a local guix channel that depends on another channel. Basically in the top-level folder of your channel's git repo, you need a .guix-channel file declaring the dependency (in a fashion similar to channels.scm). For example, for my-channel:
(channel
(version 0)
(dependencies
(channel
(name other-channel)
(url "http://other-channel")
(branch "master"))))
HTH!
Cheers,
Kaelyn
prev parent reply other threads:[~2022-04-15 15:25 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-04-13 23:29 Error pulling custom channel that includes another third-party channel B. Wilson
2022-04-15 15:24 ` Kaelyn [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
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='v08Q-57PINrhiGv4iyMBzCL5YqD8LBXgV7ZEzOVcqoVSt7UxzY6vGP0Ei-g7kp0siXq2hXlYCJrYuQjh2noi3UWDdTq4i9TECgZHapRtgzM=@protonmail.com' \
--to=kaelyn.alexi@protonmail.com \
--cc=elaexuotee@wilsonb.com \
--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 public inbox
https://git.savannah.gnu.org/cgit/guix.git
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).