From: ludo@gnu.org (Ludovic Courtès)
To: Nikita Karetnikov <nikita@karetnikov.org>
Cc: bug-guix@gnu.org
Subject: Re: Daemon: nix-connection-error
Date: Sun, 23 Jun 2013 22:20:12 +0200 [thread overview]
Message-ID: <87vc547f5v.fsf@gnu.org> (raw)
In-Reply-To: <878v203geo.fsf@karetnikov.org> (Nikita Karetnikov's message of "Sun, 23 Jun 2013 21:06:55 +0400")
Nikita Karetnikov <nikita@karetnikov.org> skribis:
>> Handle what?
>
> Handle this situation. But I guess it's not needed because noone should
> normally have '/homeless-shelter'.
>
> I was testing a package from its build directory and forgot to unset
> some variables ($HOME, for instance).
Ah, so this was not the log of a chroot build, right? (There’s no
/homeless-shelter directory in the chroot.)
>> What was the error message exactly?
>
> guix build: error: build failed: directory `/homeless-shelter' exists;
> please remove it
Perfect, then. :-)
>> unless running as root.
>
> Well, my understanding is that it shouldn't be harmful (under normal
> circumstances) for the main system. But it's not smart because you
> could affect the chroot itself, which is not desirable anyway. So, I'm
> going to use '--userspec' from now on.
Not sure what --userspec is.
Anyway, in general, it’s a bad idea to do “normal things” as root,
because it’s easy to inadvertently break the system one way or another.
Thanks,
Ludo’.
next prev parent reply other threads:[~2013-06-23 20:25 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-06-22 2:28 Daemon: nix-connection-error Nikita Karetnikov
2013-06-22 15:01 ` Ludovic Courtès
2013-06-22 16:22 ` Nikita Karetnikov
2013-06-22 20:01 ` Ludovic Courtès
2013-06-22 23:45 ` Nikita Karetnikov
2013-06-23 9:39 ` Ludovic Courtès
2013-06-23 17:06 ` Nikita Karetnikov
2013-06-23 20:20 ` Ludovic Courtès [this message]
2013-06-23 21:46 ` Nikita Karetnikov
2013-06-23 23:05 ` Ludovic Courtès
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=87vc547f5v.fsf@gnu.org \
--to=ludo@gnu.org \
--cc=bug-guix@gnu.org \
--cc=nikita@karetnikov.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).