From: Danny Milosavljevic <dannym@scratchpost.org>
To: "Ludovic Courtès" <ludo@gnu.org>
Cc: guix-devel@gnu.org
Subject: Re: security-updates merged
Date: Mon, 28 Mar 2016 10:16:10 +0200 [thread overview]
Message-ID: <20160328101610.6d13eb19@scratchpost.org> (raw)
In-Reply-To: <874mbry6ck.fsf@gnu.org>
Hi Ludo,
> Danny: could you check with either --container or --pure? It could be
> that some other settings from the outside environment were interfering.
I tried
$ guix environment guix --container
$ ./configure --localstatedir=/var
That works.
Same for
$ guix environment guix --container --pure
$ ./configure --localstatedir=/var
That works.
But
$ guix environment guix
$ ./configure --localstatedir=/var
works now too.
Hmm, I've rebooted since. Sorry for the noise.
This time when it didn't work, I did
$ make clean
beforehand so it's not because of obsolete compiled files this time.
Note that in-between (after it didn't work but before your E-Mail) I did
$ guix environment guix sqlite
$ ./configure --localstatedir=/var
And that worked, too. If that left some permanent state, it would also be clear why it works now.
Also, I did guix system reconfigure since then - with the same config (because I wanted my modified cups-service to take effect). (That eventually broke with 503 on texlive).
In any case, I'd suggest to test an eventual GuixSD release by booting it and:
$ git clone ...guix
$ guix environment guix
$ ./configure --localstatedir=/var
and see whether it fails. If it works, good.
prev parent reply other threads:[~2016-03-28 8:16 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-03-21 23:21 security-updates merged Ludovic Courtès
2016-03-26 8:51 ` Danny Milosavljevic
2016-03-26 14:33 ` Ludovic Courtès
2016-03-26 17:22 ` Mark H Weaver
2016-03-27 21:10 ` Ludovic Courtès
2016-03-28 8:16 ` Danny Milosavljevic [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=20160328101610.6d13eb19@scratchpost.org \
--to=dannym@scratchpost.org \
--cc=guix-devel@gnu.org \
--cc=ludo@gnu.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).