[oe] what to do with wrong checksum
Holger Hans Peter Freyther
holger+oe at freyther.de
Sat Nov 7 13:50:30 UTC 2009
On Saturday 07 November 2009 14:23:01 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
Good question... currently we only check the checksum after download, a first
start would be to do it before unpack... this would create an error and we
could implement c) later... (e.g. by creating a old_checksums.ini)
z.
More information about the Openembedded-devel
mailing list