Openembedded Core Discussions
 help / color / mirror / Atom feed
From: Martin Jansa <martin.jansa@gmail.com>
To: "Andreas Müller" <schnitzeltony@googlemail.com>
Cc: Patches and discussions about the oe-core layer
	<openembedded-core@lists.openembedded.org>
Subject: Re: Fetcher broken?
Date: Mon, 22 Feb 2016 22:17:40 +0100	[thread overview]
Message-ID: <20160222211740.GG6329@jama> (raw)
In-Reply-To: <CALbNGRTeReXBitXWMQJ=ZbY-C2wayOaJJdDA4KSxQcRv8Kpnkw@mail.gmail.com>

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

On Mon, Feb 22, 2016 at 10:06:10PM +0100, Andreas Müller wrote:
> Hi,
> 
> after all these scary changes in master oe-core I wanted to see what's
> left over working since jethro for my images.
> 
> On thing noticed immediately: I see
> 
> WARNING: flex-native-2.6.0-r0 do_fetch: Checksum failure encountered
> with download of
> http://downloads.sourceforge.net/flex/flex-2.6.0.tar.bz2 - will
> attempt other sources if available
> WARNING: flex-native-2.6.0-r0 do_fetch: Renaming
> /home/superandy/data/download/flex-2.6.0.tar.bz2 to
> /home/superandy/data/download/flex-2.6.0.tar.bz2_bad-checksum_0103b909e19ca9c6497a7ae696c16480
> 
> but flex-native is build happily. Same for freetype-2.6.3. Are the
> messages wrong positives or does oe build sources with wrong
> checksums?

Did the following re-try download it with different (correct)
checksum? Then it would be correct behavior if you had some
e.g. incomplete flex-2.6.0.tar.bz2 tarball laying around in downloads
directory.

-- 
Martin 'JaMa' Jansa     jabber: Martin.Jansa@gmail.com

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

  parent reply	other threads:[~2016-02-22 21:16 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-02-22 21:06 Fetcher broken? Andreas Müller
2016-02-22 21:13 ` Burton, Ross
2016-02-22 21:18   ` Andreas Müller
2016-02-22 21:17 ` Martin Jansa [this message]
2016-02-22 21:19   ` Andreas Müller
2016-02-22 21:35     ` Burton, Ross
2016-02-22 22:12       ` Andreas Müller
2016-02-22 21:25   ` Andreas Müller

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=20160222211740.GG6329@jama \
    --to=martin.jansa@gmail.com \
    --cc=openembedded-core@lists.openembedded.org \
    --cc=schnitzeltony@googlemail.com \
    /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