[oe] [PATCH] checksums.ini: correct wrong checksums

[Philip Balister]

Marcin Juszkiewicz wrote:
> Monday 10 of November 2008 15:13:45 Philip Balister napisał(a):
> 
>> I'd like to see one commit per checksum change with the details in
>> the commit message. This we we can easily find when I package
>> checksum changed. This way we can easily identifu when the source
>> changed but the version number did not.
> 
> I have 1212 new entries for checksums.ini file. Do you want 1212 commits 
> or just one?
> 
> How I got such amount? Simple - account on machine with FastEthernet 
> hooked to the Internet + some hours of shell/bitbake work:
> 
> for recipe in $OEROOT/packages/*/*.bb
> do
>   bitbake -b $recipe -cfetch
> done
> 
> Of course with OE_ALLOW_INSECURE_DOWNLOADS=1 set to not get failures 
> just because some entries are missing.

I suggested one commit per *change* of existing checksum to make sure it 
was easy to find when a source tarball changed, without a version number 
update.

Adding new checksums does not fall into this situation so one commit is 
fine with me.

I'm still hopeful that one commit per checksum change does not become a 
huge problem :)

Philip

PS: I know this is late, no reading email (on this account) at my 
current job.

-------------- next part --------------
A non-text attachment was scrubbed...
Name: smime.p7s
Type: application/x-pkcs7-signature
Size: 3303 bytes
Desc: S/MIME Cryptographic Signature
URL: <http://lists.openembedded.org/pipermail/openembedded-devel/attachments/20081113/c3d3755b/attachment-0002.bin>