From: brettg@posteo.net
To: Leo Famulari <leo@famulari.name>
Cc: 33235-done@debbugs.gnu.org
Subject: bug#33235: Bzip hash error
Date: Fri, 02 Nov 2018 04:33:10 +0100 [thread overview]
Message-ID: <951ed60730677d567e26ddbdba2e031a@posteo.net> (raw)
In-Reply-To: <20181102030929.GA25826@jasmine.lan>
Hi Leo,
Are you perhaps mistaken? the URL for bzip2 is bzip.org not bzip2.org
Regardless, even when pulling from the archive I am still being given an
incorrect hash.
On 02.11.2018 04:09, Leo Famulari wrote:
> On Fri, Nov 02, 2018 at 03:29:50AM +0100, brettg@posteo.net wrote:
>> Hi Leo,
>>
>> I’m coming from an installation using guix init, and am typing from
>> mobile.
>> I am using the berlin substitutes. I guess my option is to guix pull
>> the
>> live iso?
>
> 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 ;)
>
> The bzip2.org site is offline; the domain registration expired and the
> site is gone:
>
> https://git.savannah.gnu.org/cgit/guix.git/commit/?id=7598b678fad2112ea87a85acf755908a59dd4676
>
> I recommend downloading the missing source code from the archives,
> using
> `guix download`. For your reference, here is the full URL:
>
> https://web.archive.org/web/20180624184835/http://www.bzip.org/1.0.6/bzip2-1.0.6.tar.gz
next prev parent reply other threads:[~2018-11-02 3:34 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 [this message]
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
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=951ed60730677d567e26ddbdba2e031a@posteo.net \
--to=brettg@posteo.net \
--cc=33235-done@debbugs.gnu.org \
--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 public inbox
https://git.savannah.gnu.org/cgit/guix.git
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).