From: Catonano <catonano@gmail.com>
To: Ricardo Wurmus <rekado@elephly.net>
Cc: help-guix <help-guix@gnu.org>
Subject: Re: downloading a tarball
Date: Fri, 24 Mar 2017 14:16:46 +0100 [thread overview]
Message-ID: <CAJ98PDzGkUJ1wqXFLxPj40jBL4K0QgiAz-oQxwmgS55mVW7aBA@mail.gmail.com> (raw)
In-Reply-To: <87o9wqbzz7.fsf@elephly.net>
[-- Attachment #1: Type: text/plain, Size: 2375 bytes --]
2017-03-24 13:50 GMT+01:00 Ricardo Wurmus <rekado@elephly.net>:
>
> Catonano <catonano@gmail.com> writes:
>
> > This
> > https://sourceforge.net/projects/libxls/files/
> >
> > I attempted to build the package several times but every time the hash
> > results to be wrong.
> >
> > I correct it and then it's wrong again
> >
> > For example, I get
> >
> > @ build-failed
> > /gnu/store/dcaqrf007jxyi0jzlsakr3j7faxm122f-libxsl-1.4.0.tar.gz.drv - 1
> > output path
> > `/gnu/store/v6i85v3myb09nbsacq9ghx6yd0spcr67-libxsl-1.4.0.tar.gz' should
> > have sha256 hash `1574bcyagix5fkbs0yi2npi59y1zck23y2aia52vdv6ra3i5raid',
> > instead has `1zmsb0w6qh4vx7n7r3yijc5p4fwljyk5apzi1hwmrr5rkawmqmks'
> >
> > so I change it to
> > 1zmsb0w6qh4vx7n7r3yijc5p4fwljyk5apzi1hwmrr5rkawmqmks
> >
> > and then I get
> >
> > @ build-failed
> > /gnu/store/vsl7yz0nyklv0705jb5py015jkz3r6dg-libxsl-1.4.0.tar.gz.drv - 1
> > output path
> > `/gnu/store/wjyja461cr7kvvryp6v21q3iagf5rd8m-libxsl-1.4.0.tar.gz' should
> > have sha256 hash `1zmsb0w6qh4vx7n7r3yijc5p4fwljyk5apzi1hwmrr5rkawmqmks',
> > instead has `0fyd8h4i46qw3xii3pfa12k9k9ndmj59b552pmkpwcq7psyrbf32'
> >
> > So now it's not 1zmsb0w6qh4vx7n7r3yijc5p4fwljyk5apzi1hwmrr5rkawmqmks
> > anymore. It's
> > 0fyd8h4i46qw3xii3pfa12k9k9ndmj59b552pmkpwcq7psyrbf32
> >
> > I'm doing this with a master checkout.
> >
> > What am I missing ?
>
> Have you confirmed that the file you get is actually a tarball?
> Sometimes you might get an HTML page and Guix reports the hash for that.
>
You nailed it
I catted
/gnu/store/w1wf5d44awk0almrdrbhs8442cnzmw2b-libxsl-1.4.0.zip
which is the downloaded tarball and it contains html !
How can this be ? I'm using
(uri (string-append "mirror://sourceforge/libxsl/libxsl-"
version ".zip"))
The url used by icecat is
https://netassist.dl.sourceforge.net/project/libxls/libxls-1.4.0.zip
and the result is a sound tarball
How does it happen that the mirror based url leads to an html page ?
>
> In general it is better to download the tarball manually and then use
> “guix hash” on the result after confirming that the tarball is in fact
> okay (e.g. by validating signatures or inspecting it).
>
I did ! This was my first step, I inspected it ! And I hashed it
But then this whirl of hashes began
Thanks
[-- Attachment #2: Type: text/html, Size: 3702 bytes --]
prev parent reply other threads:[~2017-03-24 13:16 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-03-24 12:06 downloading a tarball Catonano
2017-03-24 12:26 ` Ben Woodcroft
2017-03-24 13:14 ` Tobias Geerinckx-Rice
2017-03-24 14:33 ` Hartmut Goebel
2017-03-24 22:10 ` Ludovic Courtès
2017-03-25 16:43 ` Hartmut Goebel
2017-03-25 8:47 ` Catonano
2017-03-25 10:30 ` Ben Woodcroft
2017-03-24 12:50 ` Ricardo Wurmus
2017-03-24 13:16 ` Catonano [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
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=CAJ98PDzGkUJ1wqXFLxPj40jBL4K0QgiAz-oQxwmgS55mVW7aBA@mail.gmail.com \
--to=catonano@gmail.com \
--cc=help-guix@gnu.org \
--cc=rekado@elephly.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).