From: Koen Kooi <k.kooi@student.utwente.nl>
To: openembedded-devel@openembedded.org
Subject: checksums...
Date: Wed, 21 Jan 2009 19:55:24 +0100 [thread overview]
Message-ID: <gl7r2t$sge$1@ger.gmane.org> (raw)
Hi,
Could people adding new recipe and people git-am'ing patches adding new
recipes please add the corresponding checksums to checksums.ini?
It's not hard:
1) bitbake <recipe>
2) watch it fail
3) cd $TMPDIR ; cat /OE/org.openembedded.dev/conf/checksums.ini >>
checksums.ini ; python
/OE/org.openembedded.dev/contrib/source-checker/oe-checksums-sorter.py
checksums.ini > /OE/org.openembedded.dev/conf/checksums.ini
4) git commit --amend /OE/org.openembedded.dev/conf/checksums.ini
regards,
Koen
next reply other threads:[~2009-01-21 19:02 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-01-21 18:55 Koen Kooi [this message]
2009-01-21 19:15 ` checksums Philip Balister
2009-01-21 19:34 ` [RFC] Add option for strict checksumming, was: checksums Koen Kooi
2009-01-21 22:41 ` Tom Rini
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='gl7r2t$sge$1@ger.gmane.org' \
--to=k.kooi@student.utwente.nl \
--cc=openembedded-devel@lists.openembedded.org \
--cc=openembedded-devel@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