From: Mike Looijmans <mike.looijmans@topic.nl>
To: Patches and discussions about the oe-core layer
<openembedded-core@lists.openembedded.org>
Subject: Re: tslib keeps failing on checksum
Date: Wed, 20 Nov 2013 13:02:27 +0100 [thread overview]
Message-ID: <528CA4D3.6020109@topic.nl> (raw)
In-Reply-To: <528CA4B0.3060907@topic.nl>
On 11/20/2013 12:09 PM, Mike Looijmans wrote:
> On 11/20/2013 11:38 AM, Martin Jansa wrote:
>> On Wed, Nov 20, 2013 at 11:01:36AM +0100, Mike Looijmans wrote:
>>> I get this error every time I try t build the current oe-core master:
>>>
>>> ERROR: Checksum failure fetching
>>> https://github.com/kergoth/tslib/releases/download/1.1/tslib-1.1.tar.xz;downloadfilename=tslib-1.1.tar.xz
>>>
>>> ERROR: Function failed: Fetcher failure for URL:
>>> 'https://github.com/kergoth/tslib/releases/download/1.1/tslib-1.1.tar.xz;downloadfilename=tslib-1.1.tar.xz'.
>>>
>>> Checksum mismatch!
>>> File: '/home/mike/zynq-next/build/downloads/tslib-1.1.tar.xz' has md5 checksum
>>> d41d8cd98f00b204e9800998ecf8427e when 14771f8607b341bb4b297819d37e837d was
>>> expected
>>>
>>> Now the weird thing is, that when I fetch the thing using wget, I get ablob
>>> with the right checksum:
>>>
>>> # wget https://github.com/kergoth/tslib/releases/download/1.1/tslib-1.1.tar.xz
>>> # md5sum tslib-1.1.tar.xz
>>> 14771f8607b341bb4b297819d37e837d tslib-1.1.tar.xz
>>>
>>> Is oe-core using some other flavour of wget or what else could cause this kind
>>> of fetch error?
>>
>> Have you tried to unpack both tarballs and compare content in them?
>
> Nope, I just assumed they're two somewhat different copies of the same
> software (e.g. one of them has a "downloaded from here" remark or so).
> Anything in particular I should look for?
After upgrading I tried again. The file as downloaded by bitbake is completely
empty. Nothing in it. The md5 sum of this empty file is
d41d8cd98f00b204e9800998ecf8427e indeed.
I'm now using bitbake 1.21.0 (current master) and OE rev
0eb947454e1c92467283e6f1adeca67c7c57698b to build with, with the above results
still.
(I know I can just move my own file into the download directory and get on
with it, but i'd rather actually solve this problem).
There's a direct connection to the internet, no proxy (just a router) that
might have been caching things.
Any suggestions?
Mike.
Met vriendelijke groet / kind regards,
Mike Looijmans
TOPIC Embedded Systems
Eindhovenseweg 32-C, NL-5683 KH Best
Postbus 440, NL-5680 AK Best
Telefoon: (+31) – (0)499 - 33.69.79
Telefax: (+31) - (0)499 - 33.69.70
E-mail: mike.looijmans@topic.nl
Website: www.topic.nl
Dit e-mail bericht en de eventueel daarbij behorende bijlagen zijn uitsluitend bestemd voor de geadresseerde, zoals die blijkt uit het e-mail bericht en/of de bijlagen. Er kunnen gegevens met betrekking tot een derde instaan. Indien u als niet-geadresseerde dit bericht en de bijlagen ontvangt, terwijl u niet bevoegd of gemachtigd bent om dit bericht namens de geadresseerde te ontvangen, wordt u verzocht de afzender hierover direct te informeren en het e-mail bericht met de bijlagen te vernietigen. Ieder gebruik van de inhoud van het e-mail bericht, waaronder de daarbij behorende bijlagen, door een ander dan de geadresseerde is onrechtmatig jegens ons dan wel de eventueel in het e-mail bericht of de bijlagen voorkomende andere personen. TOPIC Embedded Systems is niet aansprakelijk voor enigerlei schade voortvloeiend uit het gebruik en/of acceptatie van dit e-mail bericht of de daarbij behorende bijlagen.
The contents of this message, as well as any enclosures, are addressed personally to, and thus solely intended for the addressee. They may contain information regarding a third party. A recipient who is neither the addressee, nor empowered to receive this message on behalf of the addressee, is kindly requested to immediately inform the sender of receipt, and to destroy the message and the enclosures. Any use of the contents of this message and/or the enclosures by any other person than the addressee or person who is empowered to receive this message, is illegal towards the sender and/or the aforementioned third party. TOPIC Embedded Systems is not liable for any damage as a result of the use and/or acceptance of this message and as well as any enclosures.
next parent reply other threads:[~2013-11-20 12:02 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <528CA4B0.3060907@topic.nl>
2013-11-20 12:02 ` Mike Looijmans [this message]
2013-11-20 12:29 ` tslib keeps failing on checksum Martin Jansa
2013-11-20 12:45 ` Mike Looijmans
2013-11-20 13:24 ` Martin Jansa
2013-11-20 13:43 ` Richard Purdie
2013-11-20 15:18 ` Martin Jansa
2013-11-20 15:38 ` Richard Purdie
2013-11-20 12:59 ` Richard Purdie
2013-11-20 10:01 Mike Looijmans
2013-11-20 10:38 ` Martin Jansa
2013-11-20 11:09 ` Mike Looijmans
2013-11-20 11:05 ` Gary Thomas
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=528CA4D3.6020109@topic.nl \
--to=mike.looijmans@topic.nl \
--cc=openembedded-core@lists.openembedded.org \
/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