Openembedded Core Discussions
 help / color / mirror / Atom feed
From: Martin Jansa <martin.jansa@gmail.com>
To: Mike Looijmans <mike.looijmans@topic.nl>
Cc: 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:29:45 +0100	[thread overview]
Message-ID: <20131120122945.GN3708@jama> (raw)
In-Reply-To: <528CA4D3.6020109@topic.nl>

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

On Wed, Nov 20, 2013 at 01:02:27PM +0100, Mike Looijmans wrote:
> 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?

Any difference is important, sometimes you can find there HTML code from some
proxy or server which generates HTML page instead of 404 or someone
trying to sell you domain of long dead project etc

> 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.

OK, I was asking mostly because newer bitbake (1.19+ is new enough)
renames file with bad checksum, moving corrupted download aside so it
doesn't stand in way for new one.

> (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?

Check log.do_fetch in WORKDIR/temp, I'm not sure if the error shows only
the original URL or also possible (PRE)MIRROR url from which it could
download that empty file.

You should see the exact URL in log.do_fetch.

You can also check for (PRE)MIRROR usage in bitbake -e tslib output
-- 
Martin 'JaMa' Jansa     jabber: Martin.Jansa@gmail.com

[-- Attachment #2: Digital signature --]
[-- Type: application/pgp-signature, Size: 205 bytes --]

  reply	other threads:[~2013-11-20 12:29 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 ` tslib keeps failing on checksum Mike Looijmans
2013-11-20 12:29   ` Martin Jansa [this message]
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=20131120122945.GN3708@jama \
    --to=martin.jansa@gmail.com \
    --cc=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