[OE-core] checksums linux-libc-headers

[Richard Purdie]

On Tue, 2012-09-04 at 11:45 +0200, Andreas Müller wrote:
> On Tue, Sep 4, 2012 at 11:35 AM, Andreas Müller
> <schnitzeltony at googlemail.com> wrote:
> > Hi,
> >
> > checksums changed upstream?
> >
> > | File: '/home/andreas/data/Downloads/packets/dl/linux-3.4.3.tar.bz2'
> > has md5 checksum 635c7c2376b9eda4c0ccc67d34205e73 when
> > 3aefa02db55715d627ed23a01667057d was expected
> > | File: '/home/andreas/data/Downloads/packets/dl/linux-3.4.3.tar.bz2'
> > has sha256 checksum
> > 2fbce991cae0c9f1f363ad1386e35c2095c6cce1b43e74ed5a96186578074ae0 when
> > 17f1256daa289dde1a0a587c9753556d37a52770f7c4efcf2666fd4796a6eacc was
> > expected
> > | Your checksums:
> > | SRC_URI[md5sum] = "635c7c2376b9eda4c0ccc67d34205e73"
> > | SRC_URI[sha256sum] =
> > "2fbce991cae0c9f1f363ad1386e35c2095c6cce1b43e74ed5a96186578074ae0"
> >
> > Andreas
> 
> Sorry for noise - I tried twice before sending out this email. Seems
> my network is causing this I get every time different checksums and
> unpacking fails.

At least it validates that they *are* useful :)

[I get complaints about them being a pain when upgrading recipes but
this illustrates they do help in some cases]

Cheers,

Richard