From: raingloom <raingloom@riseup.net>
To: Leo Famulari <leo@famulari.name>
Cc: help-guix <help-guix@gnu.org>
Subject: Re: guix build gives `/homeless-shelter' exists; please remove it
Date: Sat, 22 Jan 2022 05:50:45 +0100 [thread overview]
Message-ID: <20220122055042.5fd0337f@riseup.net> (raw)
In-Reply-To: <YeswLtPzM47kNJU/@jasmine.lan>
On Fri, 21 Jan 2022 17:14:06 -0500
Leo Famulari <leo@famulari.name> wrote:
> On Fri, Jan 21, 2022 at 09:56:39PM +0000, Phil wrote:
> > I'm almost certain that option wasn't used - I know it, and it's
> > risky so wouldn't be inclined to run the daemon like that, but I
> > can't categorically rule out that I gave it a quick try. I have
> > root access to the server so wouldn't need to use it.
>
> Okay, since you know what it's about, I agree it's unlikely you used
> it.
>
> > I had previously played around with adding a single directory to the
> > chroot (--chroot-directory=dir) as a means of getting test XML
> > results out of builds of my own custom packages, but this was
> > months ago - apart from that I always use default settings for the
> > daemon.
>
> Hm... I suppose this is a likely candidate for explaining what
> happened here.
>
> > It is likely to remain a mystery alas....
>
> Agreed, the details will be hard to uncover. Hopefully it was a
> one-off mistake and not a bug in Guix...
>
Could it be a bug in package that stored the value of $HOME at build
time? Maybe it tried to mkdir -p its config directory and created
/homeless-shelter. You could perhaps try grepping for
"homeless-shelter" in your store or in that specific package.
prev parent reply other threads:[~2022-01-22 6:03 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-01-21 18:50 guix build gives `/homeless-shelter' exists; please remove it Phil Beadling
2022-01-21 20:43 ` Leo Famulari
2022-01-21 21:31 ` Phil
2022-01-21 21:36 ` Leo Famulari
2022-01-21 21:56 ` Phil
2022-01-21 22:14 ` Leo Famulari
2022-01-22 4:50 ` raingloom [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=20220122055042.5fd0337f@riseup.net \
--to=raingloom@riseup.net \
--cc=help-guix@gnu.org \
--cc=leo@famulari.name \
/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).