From: Joshua Lock <josh@linux.intel.com>
To: openembedded-core@lists.openembedded.org
Subject: Re: [PATCH 0/1] Make missing checksums an error
Date: Mon, 05 Dec 2011 18:13:40 -0800 [thread overview]
Message-ID: <4EDD7A54.5070707@linux.intel.com> (raw)
In-Reply-To: <4EDD4BD2.7010703@linux.intel.com>
On 05/12/11 14:55, Joshua Lock wrote:
> On 05/12/11 14:50, Richard Purdie wrote:
>> On Fri, 2011-12-02 at 11:20 -0800, Joshua Lock wrote:
>>> NOTE: this requires a patch I sent to the BitBake list[1] to error cleanly,
>>> otherwise you'll see a Python backtrace and the build fail...
>>>
>>> Per some discussion on the list recently this patch sets BB_STRICT_CHECKSUM
>>> in the default-distrovars.inc so that missing checksums in recipes raises an
>>> error.
>>>
>>> Cheers,
>>> Joshua
>>
>> What's the state of master? If I merge this, how badly do things
>> explode?
>
> Let me run a universe fetchall and get back to you...
Two recipes in oe-core require checksums adding, puzzles and
omap3-sgx-modules - a v2 of this request with those patches is incoming.
Joshua
--
Joshua Lock
Yocto Project "Johannes factotum"
Intel Open Source Technology Centre
next prev parent reply other threads:[~2011-12-06 2:20 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-12-02 19:20 [PATCH 0/1] Make missing checksums an error Joshua Lock
2011-12-02 19:20 ` [PATCH 1/1] default-distrovars: missing checksums should raise " Joshua Lock
2011-12-05 21:50 ` [PATCH 0/1] Make missing checksums " Joshua Lock
2011-12-05 22:50 ` Richard Purdie
2011-12-05 22:55 ` Joshua Lock
2011-12-06 2:13 ` Joshua Lock [this message]
2011-12-06 7:18 ` Koen Kooi
2011-12-06 10:33 ` Paul Eggleton
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=4EDD7A54.5070707@linux.intel.com \
--to=josh@linux.intel.com \
--cc=openembedded-core@lists.openembedded.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