From: "Björn Höfling" <bjoern.hoefling@bjoernhoefling.de>
To: brettg@posteo.net, Leo Famulari <leo@famulari.name>,
33235-done@debbugs.gnu.org
Subject: bug#33235: Bzip hash error
Date: Fri, 2 Nov 2018 22:02:39 +0100 [thread overview]
Message-ID: <20181102220239.3852ba36@alma-ubu> (raw)
In-Reply-To: <8b7a6f86f5707339261376a1cf5f6fbe@posteo.net>
[-- Attachment #1: Type: text/plain, Size: 904 bytes --]
Hi brettg,
On Fri, 02 Nov 2018 21:01:05 +0100
brettg@posteo.net wrote:
> Hi bjorn.
>
> Thank you your steps did help in getting it to build with the
> appropairiate hash sums.
>
> However, how do I get the guix system init process to
> Use that version of the build we just made? It is still
> Wanting to use the incorrect substitute.
I don't understand this.
When it is already in the store it will be used by Guix (independently
of its source, substitutes or self-compiled).
But it could be that there are two different versions of it, i.e. with
two different store-hashes. For example, one of its dependencies is
different.
Can you post the output of "guix describe" and the log of "guix system
init"?
To get the logs, you can either copy it on USB stick or get it with
ssh/scp, if you started the ssh daemon as described in the installation
manual.
Björn
[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 181 bytes --]
next prev parent reply other threads:[~2018-11-02 21:03 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-11-02 2:05 bug#33235: Bzip hash error brettg
2018-11-02 2:17 ` Leo Famulari
[not found] ` <d0d03b79be6d28b6302de4a7696b5134@posteo.net>
2018-11-02 3:09 ` Leo Famulari
2018-11-02 3:33 ` brettg
2018-11-02 5:02 ` Leo Famulari
2018-11-02 11:07 ` Björn Höfling
2018-11-02 20:12 ` brettg
[not found] ` <8b7a6f86f5707339261376a1cf5f6fbe@posteo.net>
2018-11-02 21:02 ` Björn Höfling [this message]
2018-11-02 13:40 ` swedebugia
2018-11-05 16:21 ` swedebugia
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=20181102220239.3852ba36@alma-ubu \
--to=bjoern.hoefling@bjoernhoefling.de \
--cc=33235-done@debbugs.gnu.org \
--cc=brettg@posteo.net \
--cc=leo@famulari.name \
/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.