From: Joshua Lock <josh@linux.intel.com>
To: openembedded-core@lists.openembedded.org
Subject: [PATCH 0/1] Make missing checksums an error
Date: Fri, 2 Dec 2011 11:20:14 -0800 [thread overview]
Message-ID: <cover.1322853315.git.josh@linux.intel.com> (raw)
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
1. lists.linuxtogo.org/pipermail/bitbake-devel/2011-December/thread.html
The following changes since commit 044324465bd54d53ae768f3c1e7468ae0e0c6200:
dpkg-native: Fix perl path (2011-12-02 15:31:03 +0000)
are available in the git repository at:
git://git.openembedded.org/openembedded-core-contrib josh/checksums
http://cgit.openembedded.org/cgit.cgi/openembedded-core-contrib/log/?h=josh/checksums
Joshua Lock (1):
default-distrovars: missing checksums should raise an error
meta/conf/distro/include/default-distrovars.inc | 3 +++
1 files changed, 3 insertions(+), 0 deletions(-)
--
1.7.7.3
next reply other threads:[~2011-12-02 19:27 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-12-02 19:20 Joshua Lock [this message]
2011-12-02 19:20 ` [PATCH 1/1] default-distrovars: missing checksums should raise an error 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
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=cover.1322853315.git.josh@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