From: Mark H Weaver <mhw@netris.org>
To: Robert Vollmert <rob@vllmrt.net>
Cc: 36443@debbugs.gnu.org
Subject: bug#36443: guix build mixes build dirs?
Date: Sun, 30 Jun 2019 13:18:45 -0400 [thread overview]
Message-ID: <87sgrrj8ju.fsf@netris.org> (raw)
In-Reply-To: <4C8D1EC5-8E39-4595-BFD0-0033C39C6740@vllmrt.net> (Robert Vollmert's message of "Sun, 30 Jun 2019 12:24:16 +0200")
Robert Vollmert <rob@vllmrt.net> writes:
> So this is pretty bizarre, and I haven’t managed to cut it down
> to a smaller example yet, but it seems pretty clear that something
> is broken:
>
> $ guix build -K some-package
> -> error, referencing /tmp/guix-build-puzzledb-frontend-20190625-git.drv-0
> note: keeping build directory `/tmp/guix-build-puzzledb-frontend-20190625-git.drv-0’
> $ guix build -K some-package
> -> same error, again referencing /tmp/guix-build-puzzledb-frontend-20190625-git.drv-0
> note: keeping build directory `/tmp/guix-build-puzzledb-frontend-20190625-git.drv-1’
This is known behavior, and intentional. The build is done within a
container, and the directory name within the container is canonicalized.
Regards,
Mark
next prev parent reply other threads:[~2019-06-30 17:20 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-06-30 10:24 bug#36443: guix build mixes build dirs? Robert Vollmert
2019-06-30 12:13 ` bug#36443: suspicion Robert Vollmert
2019-06-30 17:18 ` Mark H Weaver [this message]
2019-06-30 17:22 ` bug#36443: guix build mixes build dirs? Robert Vollmert
2019-06-30 17:43 ` bug#36443: Canonicalized build directory name in container leads to confusion (was guix build mixes build dirs?) Mark H Weaver
2019-06-30 17:47 ` Robert Vollmert
2019-06-30 17:59 ` Mark H Weaver
2019-07-02 13:37 ` Ludovic Courtès
2019-07-02 13:41 ` Robert Vollmert
2019-07-04 7:59 ` Ludovic Courtès
2019-07-04 8:04 ` Robert Vollmert
2019-07-04 15:12 ` Ludovic Courtès
2019-07-03 3:48 ` Mark H Weaver
2019-06-30 17:30 ` bug#36443: guix build mixes build dirs? Mark H Weaver
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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=87sgrrj8ju.fsf@netris.org \
--to=mhw@netris.org \
--cc=36443@debbugs.gnu.org \
--cc=rob@vllmrt.net \
/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 external index
https://git.savannah.gnu.org/cgit/guix.git
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.