From: Fredrik Salomonsson <plattfot@gmail.com>
To: swedebugia <swedebugia@riseup.net>
Cc: help-guix <help-guix@gnu.org>
Subject: Re: sha256 hash mismatch
Date: Mon, 19 Nov 2018 19:49:46 -0800 [thread overview]
Message-ID: <CABZcOARObj8N4ZgCiSit5P7tnGL=gQP7d1c0mr2CULNo11o-1w@mail.gmail.com> (raw)
In-Reply-To: <c861aaa3-9b41-54b2-aba8-fceba0c064b5@riseup.net>
[-- Attachment #1: Type: text/plain, Size: 3244 bytes --]
Den mån 19 nov. 2018 10:53 skrev swedebugia <swedebugia@riseup.net>:
Welcome to guix :)
Thanks!
Sorry about the rough start. Guix-land is a real adventure sometimes!
No worries. Not my first time venturing into guix-land. I'm a little bit
more prepared this time. Got a wifi-card that linux-libre supports. And I'm
more familiar with the guile language.
Thanks for specifying the command and config.scm.
Did you follow the manual?
Yes. I only authorised berlin. As I assume hydra is already authorised. Is
that assumption correct?
I suspect you did not as guix was trying to build stuff (normally we
have substitutes for almost everything if you either run init without
pulling first (=guix 0.15) or pull to a commit a week ago or so.
Getting substitutes to work is crucial if you are not very patient. The
hash mismatches are a plague brought by changes upstream which are NOT
retroactively fixed.
You can check the availability of substitutes with "guix weather".
With substitutes working and available init should not take more that 10
min on a recent machine. It would probably be a good idea to state this
in the manual.
Thanks for pointing out "guix weather". I've seen it mentioned from time to
time in the mailing list. But didn't know what it was used for. Any good
workflow to find a commit that have good substitute coverage? As from what
I understand, reading the manual. It will only check the guix version
you're running.
If you want to hack on guix you will have to update guix above 0.15.
That's my end goal. Just need to be able to install it. :)
Will try to do a guix pull, to see if that works.
Den mån 19 nov. 2018 10:53 skrev swedebugia <swedebugia@riseup.net>:
> Welcome to guix :)
>
> On 2018-11-19 06:10, Fredrik Salomonsson wrote:
> > Hi,
> >
> > Trying to install guix-0.15 to see if I can get dual booting with btrfs
> > working on my laptop. But didn't get that far. Encounter an error when
> > running guix system init. Ran it twice, same error. Any idea what could
> > be wrong? Took about 4-6h to run it the first time.
>
> Sorry about the rough start. Guix-land is a real adventure sometimes!
>
> >
> > Here's the command:
> > guix system init /mnt/etc/config.scm /mnt/
> > --substitute-urls="https://hydra.gnu.org https://berlin.guixsd.org"
> Thanks for specifying the command and config.scm.
> Did you follow the manual? (e.g. authorize the keys for both servers
> above?)
>
> I suspect you did not as guix was trying to build stuff (normally we
> have substitutes for almost everything if you either run init without
> pulling first (=guix 0.15) or pull to a commit a week ago or so.
>
> Getting substitutes to work is crucial if you are not very patient. The
> hash mismatches are a plague brought by changes upstream which are NOT
> retroactively fixed.
>
> You can check the availability of substitutes with "guix weather".
>
> With substitutes working and available init should not take more that 10
> min on a recent machine. It would probably be a good idea to state this
> in the manual.
>
> If you want to hack on guix you will have to update guix above 0.15.
>
> --
> Cheers
> Swedebugia
>
[-- Attachment #2: Type: text/html, Size: 5092 bytes --]
next prev parent reply other threads:[~2018-11-20 3:50 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 [this message]
2018-11-20 16:21 ` swedebugia
2018-11-21 7:33 ` Fredrik Salomonsson
2018-11-21 16:06 ` swedebugia
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='CABZcOARObj8N4ZgCiSit5P7tnGL=gQP7d1c0mr2CULNo11o-1w@mail.gmail.com' \
--to=plattfot@gmail.com \
--cc=help-guix@gnu.org \
--cc=swedebugia@riseup.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).