unofficial mirror of help-guix@gnu.org 
 help / color / mirror / Atom feed
From: Leo Famulari <leo@famulari.name>
To: Phil <phil@beadling.co.uk>
Cc: help-guix <help-guix@gnu.org>
Subject: Re: guix build gives `/homeless-shelter' exists; please remove it
Date: Fri, 21 Jan 2022 16:36:33 -0500	[thread overview]
Message-ID: <YesnYQejk1qthtHp@jasmine.lan> (raw)
In-Reply-To: <87ee50g4he.fsf@beadling.co.uk>

On Fri, Jan 21, 2022 at 09:31:57PM +0000, Phil wrote:
> Thanks Leo - indeed it was so suprising that I thought it was referring
> to the root of the chroot used to build rather than just the root of
> Ubuntu.
> 
> This was a bad assumption on my behalf  as /homeless-shelter really did
> exist at my filesystem root (containing a single .config directory with
> 2 yamls in it related to the python dask package).
> 
> I moved the directory and everything is back to normal.
> 
> Even stranger the datestamp on the homeless shelter was from November
> 2021, so why it decided to start fail yesterday I have no idea.
> 
> Thanks again and sorry for the daft question - if I'd literally followed
> the advice in the error message I'd have resolved it myself!  Way too
> much overthinking on my behalf!

It's not daft! The situation is really surprising. The only good
explanation I can think of is that guix-daemon was used the the
"--disable-chroot" option. Do you remember if you used that option?


  reply	other threads:[~2022-01-21 21:37 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 [this message]
2022-01-21 21:56       ` Phil
2022-01-21 22:14         ` Leo Famulari
2022-01-22  4:50           ` raingloom

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=YesnYQejk1qthtHp@jasmine.lan \
    --to=leo@famulari.name \
    --cc=help-guix@gnu.org \
    --cc=phil@beadling.co.uk \
    /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).