[oe] what to do with wrong checksum

Koen Kooi k.kooi at student.utwente.nl
Sat Nov 7 14:42:16 UTC 2009


On 07-11-09 14:23, Mike Westerhof wrote:
> Frans Meulenbroeks wrote:
> ...
>>
>> Reluctantly updated checksums.ini
>>
>> Frans
>
> But of course there's no magic that will remove the old cached tarball
> out of one's downloads directory when this sort of thing happens.
> (Busybox has been known to do this, too)
>
> What do folks think we should do about that when it occurs?
> a) support two entries (old and new) in checksums.ini
> b) do nothing (leave as is)
> c) add some sort of support so that the user gets additional information
>     with the new checksum match failure explaining that the checksum was
>     updated and they need to manually remove the old (bad) tarball

d) rename the tarball slighty and mirror in on a known good server (e.g. 
angstrom sourcemirror) and have OE use that.

regards,

Koen





More information about the Openembedded-devel mailing list