From: Jookia <166291@gmail.com>
To: help-guix@gnu.org
Subject: Re: Updating Guix requires full rebuild?
Date: Sun, 31 Jan 2016 20:37:23 +1100 [thread overview]
Message-ID: <20160131093723.GA21358@novena-choice-citizen.lan> (raw)
In-Reply-To: <20160130100642.GA31612@novena-choice-citizen.lan>
On Sat, Jan 30, 2016 at 09:06:42PM +1100, Jookia wrote:
> Hey there,
>
> I've been compiling and installing Guix without any substitutes, however I've
> hit a problem. I've managed to compile Guix, then compile Guix using Guix. But
> when I try to do anything using the Guix managed by Guix, it wants to rebuild
> everything on my system. I've uploaded some raw data,[1] comparing the outputs
> of the old and new Guix binaries and accompanying binaries as well as with and
> without the --bootstrap flag. The package being inspected is 'tar'.
>
> It would seem like this is a major problem considering both Guix packages are
> identical aside from the host code having the Guix package derivation updated
> to use the same Git version as the host version of Guix. The tar packages aren't
> modified in any way and neither is any thing I would expect to be used to build
> a derivation, such as a builder script.
>
> Cheers,
> Jookia.
>
> [1]: uhoh.tar.bz2: https://infotomb.com/2dp3c
Following up: davexunit looked at this issue with me on IRC and showed me it's
to do with the Guix built from Git in Debian using /usr/local/var/guix while the
Guix installed using Guix used /var/guix - moving the files fixed everything.
Cheers,
Jookia.
next prev parent reply other threads:[~2016-01-31 9:40 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-01-30 10:06 Updating Guix requires full rebuild? Jookia
2016-01-31 9:37 ` Jookia [this message]
2016-02-01 13:45 ` Ludovic Courtès
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=20160131093723.GA21358@novena-choice-citizen.lan \
--to=166291@gmail.com \
--cc=help-guix@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.
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).