unofficial mirror of help-guix@gnu.org 
 help / color / mirror / Atom feed
From: Tomas Volf <~@wolfsden.cz>
To: help-guix@gnu.org
Subject: How to use guix-for-channels together with -L without errors?
Date: Thu, 15 Aug 2024 00:24:17 +0200	[thread overview]
Message-ID: <Zr0ukQPSYqR8LBNZ@ws> (raw)

[-- Attachment #1: Type: text/plain, Size: 1070 bytes --]

Hi,

I decided to start using guix-for-channels and run into weird issue.
Reproduction is easy:

1. Make a new directory.

2. Make an empty file with .scm extension, for example:

    $ touch foo.scm

3. Try to build guix-for-channels in that directory with `-L .':

    $ guix build -L . -e '((@ (gnu packages package-management) guix-for-channels) (@ (guix channels) %default-channels))'

4. Observe an error in the output:

    Updating channel 'guix' from Git repository at 'https://git.savannah.gnu.org/git/guix.git'...
    no code for module (foo)

Now, what I do not understand is why this error:

    no code for module (foo)

is there.  I am building guix from %default-channels, why is it even loading
files in the local directory?  And how do I make it stop?  In this case, I could
just drop `-L .', but in real code I need the argument to load modules required
for the system.

Any comments and/or ideas?

Thanks and have a nice day,
Tomas Volf

--
There are only two hard things in Computer Science:
cache invalidation, naming things and off-by-one errors.

[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 833 bytes --]

             reply	other threads:[~2024-08-14 22:25 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-08-14 22:24 Tomas Volf [this message]
2024-08-15 17:14 ` How to use guix-for-channels together with -L without errors? Nils Landt
2024-08-15 19:46   ` Tomas Volf
2024-08-16  4:40     ` Nils Landt

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=Zr0ukQPSYqR8LBNZ@ws \
    --to=~@wolfsden.cz \
    --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.
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).