From: Richard Purdie <richard.purdie@linuxfoundation.org>
To: Philip Balister <philip@balister.org>
Cc: openembedded-core <openembedded-core@lists.openembedded.org>
Subject: Re: Recipes with SRC_URI in .inc file and checksum in bb file
Date: Mon, 07 Jan 2013 13:25:50 +0000 [thread overview]
Message-ID: <1357565150.25855.11.camel@ted> (raw)
In-Reply-To: <50E70BBE.1000607@balister.org>
On Fri, 2013-01-04 at 12:05 -0500, Philip Balister wrote:
> On 01/04/2013 11:59 AM, Marko Lindqvist wrote:
> > On 4 January 2013 18:45, Philip Balister <philip@balister.org> wrote:
> >>
> >> I am on the process of updating the fftw recipes to the most recent
> >> version. Along the way I noticed it looks like the checksum test is
> >> being ignored. The only way I can get it to fail is to remove all the
> >> checksum entries from the bb files.
> >
> > I've got this kind of problems when I have made several iterations of
> > the recipe update. In my case the explanation has always been that
> > first test already downloaded the file, so no matter what I do to
> > checksums after that, there's no download + checksum check on later
> > tests.
> > Remove file and <file>.done from download, + 'bitbake <recipe> -c clean'
>
> I uderstand that, but the other problem is even with a new download, the
> checksum check is ignored if there are checksum entries in more than one
> bb file.
Multiple checksums in different .bb files for the same filename?
Cheers,
Richard
prev parent reply other threads:[~2013-01-07 13:41 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-01-04 16:45 Recipes with SRC_URI in .inc file and checksum in bb file Philip Balister
2013-01-04 16:59 ` Marko Lindqvist
2013-01-04 17:05 ` Philip Balister
2013-01-07 13:25 ` 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=1357565150.25855.11.camel@ted \
--to=richard.purdie@linuxfoundation.org \
--cc=openembedded-core@lists.openembedded.org \
--cc=philip@balister.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox