From: Koen Kooi <k.kooi@student.utwente.nl>
To: openembedded-devel@openembedded.org
Subject: Re: RFC: Making it mandantory to have a checksums.ini entry
Date: Wed, 15 Oct 2008 19:51:36 +0200 [thread overview]
Message-ID: <gd5aj9$h8u$1@ger.gmane.org> (raw)
In-Reply-To: <200810151934.46076.zecke@selfish.org>
On 15-10-2008 19:34, Holger Freyther wrote:
> On Wednesday 01 October 2008 04:47:41 Holger Freyther wrote:
>
> I have added the relevant checksums we had at Openmoko and made it mandatory
> to have a checksum. See the previous mail on how to disable it.
Instead of having people disabling the checks here's how you can help:
Step 1)
go to TMPDIR and locate the checksums.ini there
Step 2)
sort the checksums.ini:
python
/OE/org.openembedded.dev/contrib/source-checker/oe-checksums-sorter.py
checksums.ini > new
Step 3) combine the checksums.ini from OE and yours:
cat /OE/org.openembedded.dev/conf/checksums.ini checksums.ini >
combined-sums
Step 4)
sort the result and apply it to OE
python
/OE/org.openembedded.dev/contrib/source-checker/oe-checksums-sorter.py
combined-sums > /OE/org.openembedded.dev/conf/checksums.ini
Step 5) go to your OE dir and inspect the results:
cd /OE/org.openembedded.dev
git diff conf/checksums.ini
The diff should only contain additions (removals and replacements are a
sign of corruption somewhere).
If you see no spurious changes, commit it and wait for people to bitch
if you added a corrupted checksum ;)
regards,
Koen
next prev parent reply other threads:[~2008-10-15 17:56 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-10-01 2:47 RFC: Making it mandantory to have a checksums.ini entry Holger Freyther
2008-10-01 2:58 ` Otavio Salvador
2008-10-01 7:06 ` Koen Kooi
2008-10-15 17:34 ` Holger Freyther
2008-10-15 17:51 ` Koen Kooi [this message]
2008-10-15 18:17 ` Marcin Juszkiewicz
2008-10-16 12:20 ` Sledz, Steffen
2008-10-16 12:39 ` Thomas Kunze
2008-10-16 12:44 ` Sledz, Steffen
2008-10-16 12:52 ` Thomas Kunze
2008-10-16 13:12 ` Sledz, Steffen
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='gd5aj9$h8u$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 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.