From: "Wiktor Żelazny" <wz@freeshell.de>
To: Ricardo Wurmus <rekado@elephly.net>
Cc: help-guix@gnu.org
Subject: Re: ./pre-inst-env guix build dangerous inside an environment?
Date: Wed, 11 Sep 2019 18:18:00 +0200 [thread overview]
Message-ID: <20190911161800.g6lzpfmfttsxgxmf@wz.localdomain> (raw)
In-Reply-To: <87a7bcqkts.fsf@elephly.net>
[-- Attachment #1: Type: text/plain, Size: 1010 bytes --]
On Tue, Sep 10, 2019 at 04:37:03PM +0200, Ricardo Wurmus wrote:
> This sounds like perhaps you ran “./configure” without
> “--localstatedir=/var”, so that Guix would be using a different
> location for its database and thus consider existing stuff in /gnu to
> be invalid.
Thank you for your prompt reply, Ricardo.
Yeah, that’s precisely what happened. I missed (or just lazily,
hastily ignored) the “Make sure to pass --localstatedir=directory”
sentence. I’m glad there exists at least an explanation for that
disaster.
Don’t you think it would be reasonable to follow that sentence with
something like: *Otherwise, you risk that the default store in `/gnu`
becomes damaged*?
> This is not a problem with using an environment.
Still, it seems to me unclear from the manual (at least as far as
14.2 is concerned) whether anything is gained by doing test builds in
an environment, and thus whether this is the recommended way, and if
so—for which steps.
WŻ
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 963 bytes --]
next prev parent reply other threads:[~2019-09-11 16:18 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-09-10 13:58 ./pre-inst-env guix build dangerous inside an environment? Wiktor Żelazny
2019-09-10 14:37 ` Ricardo Wurmus
2019-09-11 16:18 ` Wiktor Żelazny [this message]
2019-09-11 19:40 ` Ricardo Wurmus
2019-09-12 15:45 ` Wiktor Żelazny
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=20190911161800.g6lzpfmfttsxgxmf@wz.localdomain \
--to=wz@freeshell.de \
--cc=help-guix@gnu.org \
--cc=rekado@elephly.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.
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).