From: swedebugia <swedebugia@riseup.net>
To: Fredrik Salomonsson <plattfot@gmail.com>
Cc: help-guix <help-guix@gnu.org>
Subject: Re: sha256 hash mismatch
Date: Wed, 21 Nov 2018 17:06:29 +0100 [thread overview]
Message-ID: <99bc1728-8a95-b3ac-1595-f2a0f77b6236@riseup.net> (raw)
In-Reply-To: <87tvkaga1b.fsf@gmail.com>
On 2018-11-21 08:33, Fredrik Salomonsson wrote:
> swedebugia <swedebugia@riseup.net> writes:
snip
>
> Put berlin first in the --substitute-urls and did a guix pull to one
> commit that had the most packages built. Using
> http://berlin.guixsd.org/jobset/guix-master to pick out the commit.
>
> The install took less than 20min on my x220. Thanks for all the help!
:D Great that you got past the init state.
>
> Though I needed to manually hack the grub.cfg to be able to
> boot. Otherwise it wouldn't find the kernel.
>
> Now it get stuck when trying to mount the filesystem. Backtrace shows
> it's failing in ./gnu/build/file-system.scm 613:6
>
> Might have something misconfigured in my config file. Anyways that's not
> what this thread is about. If I cannot figure it out I'll send another
> email.
>
> Thanks again for the help!
>
Installing a simpler config.scm and going incrementally forward with
small changes might be worth considering.
Especially given that our guix/guile error messages can sometimes be
quite cryptic if you dont know exactly what change caused the error.
--
Cheers Swedebugia
next prev parent reply other threads:[~2018-11-21 16:15 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-11-19 5:10 sha256 hash mismatch Fredrik Salomonsson
2018-11-19 6:03 ` Jovany Leandro G.C
2018-11-19 18:53 ` swedebugia
2018-11-20 3:49 ` Fredrik Salomonsson
2018-11-20 16:21 ` swedebugia
2018-11-21 7:33 ` Fredrik Salomonsson
2018-11-21 16:06 ` swedebugia [this message]
2018-11-21 18:23 ` Fredrik Salomonsson
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=99bc1728-8a95-b3ac-1595-f2a0f77b6236@riseup.net \
--to=swedebugia@riseup.net \
--cc=help-guix@gnu.org \
--cc=plattfot@gmail.com \
/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).