From: SeerLite <seerlite@nixnet.email>
To: guix-devel@gnu.org
Subject: Re: How to handle package udev rules?
Date: Tue, 4 Jan 2022 19:38:58 -0300 [thread overview]
Message-ID: <992b9edd-eab6-7c56-8c71-cf0b77b6c039@nixnet.email> (raw)
In-Reply-To: <874k7c997j.fsf@member.fsf.org>
On 12/13/21 04:48, Γυψ wrote:
> Dear Danny,
>
> thanks! That lead me on the right track. In fact it's just
>
>> sudo -E guix ...
Hi!
I recommend avoiding the use of sudo -E, as it will make guix system use
your non-root user's $HOME/.cache to write its compiled files, which
might become a problem in the future. I myself had an issue because of
this where all of ~/.cache/guile was owned by root, meaning my user was
unable to write to it.
Just to make sure, try running
find ~ -user root
to see if you've got any root-owned files in your $HOME.
I think the right command in your case is
sudo --preserve-env=GUIX_PACKAGE_PATH guix system reconfigure
/etc/config.scm
Replying bit late, but I hope it's useful. I see sudo -E recommended a
lot yet it always causes issues on my end, so I'm against it.
SeerLite
prev parent reply other threads:[~2022-01-05 20:24 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
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 [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=992b9edd-eab6-7c56-8c71-cf0b77b6c039@nixnet.email \
--to=seerlite@nixnet.email \
--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).