From: Richard Purdie <richard.purdie@linuxfoundation.org>
To: "Andreas Müller" <schnitzeltony@googlemail.com>
Cc: openembedded-core@lists.openembedded.org
Subject: Re: checksums linux-libc-headers
Date: Tue, 04 Sep 2012 11:21:49 +0100 [thread overview]
Message-ID: <1346754109.30964.21.camel@ted> (raw)
In-Reply-To: <CALbNGRRvPK7HZN08-QnyEoC61jyjQ_JRcXrk1+aFacy4RsinZg@mail.gmail.com>
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@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
prev parent reply other threads:[~2012-09-04 10:34 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-09-04 9:35 checksums linux-libc-headers Andreas Müller
2012-09-04 9:45 ` Andreas Müller
2012-09-04 10:21 ` Richard Purdie [this message]
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=1346754109.30964.21.camel@ted \
--to=richard.purdie@linuxfoundation.org \
--cc=openembedded-core@lists.openembedded.org \
--cc=schnitzeltony@googlemail.com \
/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.