unofficial mirror of bug-guix@gnu.org 
 help / color / mirror / code / Atom feed
From: Leo Famulari <leo@famulari.name>
To: brettg@posteo.net
Cc: 33235-done@debbugs.gnu.org
Subject: bug#33235: Bzip hash error
Date: Fri, 2 Nov 2018 01:02:39 -0400	[thread overview]
Message-ID: <20181102050239.GC19599@jasmine.lan> (raw)
In-Reply-To: <951ed60730677d567e26ddbdba2e031a@posteo.net>

[-- Attachment #1: Type: text/plain, Size: 727 bytes --]

On Fri, Nov 02, 2018 at 04:33:10AM +0100, brettg@posteo.net wrote:
> Hi Leo,
> 
> Are you perhaps mistaken? the URL for bzip2 is bzip.org not bzip2.org

I mentioned the wrong "short" URLs in my message, but the full URL of
the source code on archive.org was correct.

bzip.org is offline and the source is available on archive.org.

> Regardless, even when pulling from the archive I am still being given an
> incorrect hash.

Can you take a photo of your screen and email it with your mobile?

If so, please show the command you run and the failing part of the
output.

Also, do 
`guix download https://web.archive.org/web/20180624184835/http://www.bzip.org/1.0.6/bzip2-1.0.6.tar.gz`
and show the result.

[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 833 bytes --]

  reply	other threads:[~2018-11-02  5: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 [this message]
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=20181102050239.GC19599@jasmine.lan \
    --to=leo@famulari.name \
    --cc=33235-done@debbugs.gnu.org \
    --cc=brettg@posteo.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.
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).