From: Alex J Lennon <ajlennon@dynamicdevices.co.uk>
To: 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 20:39:31 +0100 [thread overview]
Message-ID: <4F7368F3.9050705@dynamicdevices.co.uk> (raw)
In-Reply-To: <CACW_hTZ1Bu7X12=BLq+dfX-xHQzy829_w-fjwDX0VEeSTuBw7Q@mail.gmail.com>
Frans,
>Guess we might want to mirror a version and pull from the mirror.
I don't mind putting a mirrow up at the Dynamic Devices wbesite with a
SRC_URI link to it there.
That''s a bit of a patchy solution though isn't it? Ideally (imho) as I
suggested the
other day there would be an official OE mirror that the standard OE
framework
fell back to when it couldn't find the primary source material, but then
somebody
has to pay for that of course :)
>PS: thinking of it: we might be able to resolve the latter issue by
I'm not sure if that would help us though, as (presumably) the point of
the MD5
is to notify us that "something" is wrong with the file that has been
pulled down,
whether because it is incomplete or the developers are being naughty.
Cheers,
Alex
On 28/03/2012 09:34, Frans Meulenbroeks wrote:
> 2012/3/28<ajlennon@dynamicdevices.co.uk>:
>> From: Alex J Lennon<ajlennon@gmail.com>
>>
>> Signed-off-by: Alex J Lennon<ajlennon@gmail.com>
>> ---
>> recipes/libpng/libpng_1.2.48.bb | 4 ++--
>> 1 files changed, 2 insertions(+), 2 deletions(-)
>>
>> diff --git a/recipes/libpng/libpng_1.2.48.bb b/recipes/libpng/libpng_1.2.48.bb
>> index 50a3c03..534962d 100644
>> --- a/recipes/libpng/libpng_1.2.48.bb
>> +++ b/recipes/libpng/libpng_1.2.48.bb
>> @@ -2,5 +2,5 @@ require libpng.inc
>>
>> PR = "${INC_PR}.0"
>>
>> -SRC_URI[libpng.md5sum] = "7612af5660cd4b5e8c433ce53bea01a7"
>> -SRC_URI[libpng.sha256sum] = "f6db51aff81b6920203678b29e8c68a5e3703cf5b39ae5e9e56370d17f31b1c4"
>> +SRC_URI[libpng.md5sum] = "74c8c261bdf9a75274e22875183fda07"
>> +SRC_URI[libpng.sha256sum] = "b4c92df11eadf3e81705a58253dbffc4b95169186899e28abdfc8aada8a20fcc"
>> --
>> 1.7.5.4
>>
> You mean upstream changed their source tarball (or whatever) without
> updating the version number.
> Yuk.
>
> Guess we might want to mirror a version and pull from the mirror.
> (changing the checksum alone creates issues because other people might
> already have the version with the old checksum in their downloads.
>
> Frans
>
> PS: thinking of it: we might be able to resolve the latter issue by
> forcing the removal of a file from downloads (and trigger a refetch)
> if the .md5 does not match the md5 in the recipe.
>
> _______________________________________________
> Openembedded-devel mailing list
> Openembedded-devel@lists.openembedded.org
> http://lists.linuxtogo.org/cgi-bin/mailman/listinfo/openembedded-devel
next prev parent reply other threads:[~2012-03-28 19:49 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 [this message]
2012-03-28 19:45 ` Paul Eggleton
2012-03-28 19:50 ` Alex J Lennon
2012-03-28 20:32 ` Paul Eggleton
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=4F7368F3.9050705@dynamicdevices.co.uk \
--to=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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.