Difference between revisions of "Mini2440 MD5 checksum problems"
From Kenneth Noyens
(Nieuwe pagina aangemaakt met '<h2>In a email from Laurent Verstraeten I got a helpful tip about MD5 problems: </h2> When you use a new source repository for bitbake you have to update a<br> file ca...') |
|||
| Line 6: | Line 6: | ||
<br> | <br> | ||
<br> | <br> | ||
| − | In case bitbake complain of "has no checksum defined, cannot check<br> | + | In case bitbake complain of "has no checksum defined, cannot check archive integrity"<br> |
| − | + | (this can be due when a new mirror has been defined for a package), | |
| − | for a package), it can be solved by :<br> | + | it can be solved by :<br> |
| − | + | <pre> | |
| − | cat tmp/checksums.ini >>~/oe/base/conf/checksums.ini<br> | + | cat tmp/checksums.ini >>~/oe/base/conf/checksums.ini<br> |
| − | python contrib/source-checker/oe-checksums-sorter.py -i conf/checksums.ini<br> | + | python contrib/source-checker/oe-checksums-sorter.py -i conf/checksums.ini<br> |
| − | + | </pre> | |
| − | OE helpfully generates the checksums it expected to see so these can | + | OE helpfully generates the checksums it expected to see so these can be added to the meta data easilly. |
| − | be added to the meta data easilly. The cat just appends the new | + | The cat just appends the new checksum to the end of the file. <br> |
| − | checksum to the end of the file. The next python command then calls | + | The next python command then calls ascript to sort the checksums into the recommended format.<br> |
| − | |||
Latest revision as of 18:22, 21 April 2010
In a email from Laurent Verstraeten I got a helpful tip about MD5 problems:
When you use a new source repository for bitbake you have to update a
file called checksums.ini in base/conf/
Some info about this:
http://blogs.elphel.com/2009/12/openembeddedangstom-new-package-workflow-eyeos/
In case bitbake complain of "has no checksum defined, cannot check archive integrity"
(this can be due when a new mirror has been defined for a package),
it can be solved by :
cat tmp/checksums.ini >>~/oe/base/conf/checksums.ini<br> python contrib/source-checker/oe-checksums-sorter.py -i conf/checksums.ini<br>
OE helpfully generates the checksums it expected to see so these can be added to the meta data easilly.
The cat just appends the new checksum to the end of the file.
The next python command then calls ascript to sort the checksums into the recommended format.
