all messages for Guix-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: swedebugia <swedebugia@riseup.net>
To: 33235@debbugs.gnu.org, leo@famulari.name, brettg@posteo.net
Subject: bug#33235: Bzip hash error
Date: Mon, 5 Nov 2018 17:21:57 +0100	[thread overview]
Message-ID: <8e013510-41a7-4809-70a4-b6698733bbf2@riseup.net> (raw)
In-Reply-To: <893aa3e7-8539-c515-bdd0-8c92da9a5e20@riseup.net>


On 2018-11-02 14:40, swedebugia wrote:
> Hi
>
> On 2018-11-02 04:09, Leo Famulari wrote:
>> No, I recommend against doing `guix pull` before initializing. We test
>> that the installer works, but if you update Guix before initialization,
>> then you void the warranty
> I suggest we state this VERY clearly in the manual.

Actually guix very loudly warns the user that running guix system init 
before guix pull will downgrade guix.

I solved this by pulling the 0.15 commit and then init.

I suggest we tell binary install users to do this in the manual.

What do you think?

-- 
Cheers
Swedebugia

      reply	other threads:[~2018-11-05 16:23 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
2018-11-02 13:40       ` swedebugia
2018-11-05 16:21         ` swedebugia [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

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=8e013510-41a7-4809-70a4-b6698733bbf2@riseup.net \
    --to=swedebugia@riseup.net \
    --cc=33235@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.