From: Danny Milosavljevic <dannym@scratchpost.org>
To: gyps@member.fsf.org
Cc: guix-devel@gnu.org
Subject: Re: How to handle package udev rules?
Date: Sun, 12 Dec 2021 23:37:06 +0100 [thread overview]
Message-ID: <20211212233706.11f6a57a@scratchpost.org> (raw)
In-Reply-To: <87sfux353z.fsf@h-brs.de>
[-- Attachment #1: Type: text/plain, Size: 853 bytes --]
Hi,
On Sun, 12 Dec 2021 21:58:14 +0100
gyps@member.fsf.org wrote:
> If I change my operating-system config to inlcude udev-rules from
> package "projecteur" everything works fine - at least if I do it as a
> regular user. As soon as I sudo the guix system reconfigure command the
> package is known but it's code is not. Error message is:
>
> > $ sudo guix system reconfigure ~/etc/config.scm
> > ice-9/boot-9.scm:3329:6: In procedure resolve-interface:
> > no code for module (projecteur)
>
> Could it be the case that sudo'ed the variable GUIX_PACKAGE_PATH is not
> known or not interpreted correctly? Does the package need to reside
> somewhere else than in GUIX_PACKAGE_PATH?
Yeah, sudo is very paranoid. You need to pass -E GUIX_PACKAGE_PATH to it:
sudo -E GUIX_PACKAGE_PATH guix system reconfigure ~/etc/config.scm
[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 488 bytes --]
next prev parent reply other threads:[~2021-12-12 22:37 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-12-12 12:12 How to handle package udev rules? Alexander Asteroth
2021-12-12 13:57 ` Γυψ
2021-12-12 16:24 ` Tobias Geerinckx-Rice
2021-12-12 18:17 ` Danny Milosavljevic
2021-12-12 20:58 ` gyps
2021-12-12 22:37 ` Danny Milosavljevic [this message]
2021-12-13 8:48 ` Γυψ
2021-12-17 8:20 ` Alexander Asteroth
2021-12-17 9:08 ` Josselin Poiret via Development of GNU Guix and the GNU System distribution.
2022-01-04 22:38 ` SeerLite
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=20211212233706.11f6a57a@scratchpost.org \
--to=dannym@scratchpost.org \
--cc=guix-devel@gnu.org \
--cc=gyps@member.fsf.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).