From: Philip Balister <philip@balister.org>
To: openembedded-devel@lists.openembedded.org
Subject: Re: checksums...
Date: Wed, 21 Jan 2009 12:15:04 -0700 [thread overview]
Message-ID: <49777438.8070108@balister.org> (raw)
In-Reply-To: <gl7r2t$sge$1@ger.gmane.org>
[-- Attachment #1: Type: text/plain, Size: 834 bytes --]
Koen Kooi wrote:
> 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
I screwed this up once (and committed a recipe without the checksum)
when I left ALLOW_INSECURE_DOWNLOADS set in my local.conf. Now I have it
commented out and am really careful only to use it only when hacking.
I also need to look up what "git commit --amend" does.
Philip
[-- Attachment #2: S/MIME Cryptographic Signature --]
[-- Type: application/x-pkcs7-signature, Size: 3303 bytes --]
next prev parent reply other threads:[~2009-01-21 19:22 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-01-21 18:55 checksums Koen Kooi
2009-01-21 19:15 ` Philip Balister [this message]
2009-01-21 19:34 ` [RFC] Add option for strict checksumming, was: checksums Koen Kooi
2009-01-21 22:41 ` Tom Rini
-- strict thread matches above, loose matches on Subject: below --
2013-05-14 9:14 checksums folkert
2013-05-14 13:18 ` checksums Theodore Ts'o
2013-05-14 14:40 ` checksums folkert
2013-05-14 18:09 ` checksums Darrick J. Wong
2013-05-14 18:57 ` checksums folkert
2013-05-14 19:21 ` checksums Darrick J. Wong
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=49777438.8070108@balister.org \
--to=philip@balister.org \
--cc=openembedded-devel@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 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.