From: Paul Eggleton <paul.eggleton@linux.intel.com>
To: Alex J Lennon <ajlennon@dynamicdevices.co.uk>
Cc: openembedded-devel@lists.openembedded.org
Subject: Re: [PATCH] Modified fetch() checksums to be correct for libpng 1.4.28 released 15/3/12 (current) instead of previous 8/3/12 release
Date: Wed, 28 Mar 2012 21:32:21 +0100 [thread overview]
Message-ID: <5366685.RG9uTzE68W@helios> (raw)
In-Reply-To: <4F736B9F.9050304@dynamicdevices.co.uk>
On Wednesday 28 March 2012 20:50:55 Alex J Lennon wrote:
> Paul,
>
> >FYI, I'm pretty sure that fetch2 from the version of bitbake we use with
> >OE-
> I thought it might. Does it still do that if the checksum fails though?
Yes, I believe (without having tested it recently) that a SRC_URI checksum
failure is considered in the same way as if the download failed.
> >Of course that's assuming there is a mirror available.
>
> I'm happy to host a 2nd copy and mod the .bb to add another source if
> that helps (the
> libpng repo seems to have a history of deleting versions from what I saw
> of the patch
> history so it might be a good idea?). Is that ok for everybody?
No harm in it, however I believe it may be better to get it on
sources.openembedded.org - I think the usual procedure is to ping Tom King
(ka6sox on IRC) and then send get the files to him so he can upload them there.
Cheers,
Paul
--
Paul Eggleton
Intel Open Source Technology Centre
next prev parent reply other threads:[~2012-03-28 20:41 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-03-27 22:47 [PATCH] Modified fetch() checksums to be correct for libpng 1.4.28 released 15/3/12 (current) instead of previous 8/3/12 release ajlennon
2012-03-28 8:34 ` Frans Meulenbroeks
2012-03-28 10:16 ` Alex J Lennon
2012-03-28 19:39 ` Alex J Lennon
2012-03-28 19:45 ` Paul Eggleton
2012-03-28 19:50 ` Alex J Lennon
2012-03-28 20:32 ` Paul Eggleton [this message]
2012-03-28 20:38 ` Frans Meulenbroeks
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=5366685.RG9uTzE68W@helios \
--to=paul.eggleton@linux.intel.com \
--cc=ajlennon@dynamicdevices.co.uk \
--cc=openembedded-devel@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