This looks like a problem I saw while bitbaking the kernel, too. I don't remember if it was the same tarball, but one of them was known to fail the untar process for my OS/processor. I downloaded an alternate tarball, but naturally it failed the checksum comparison. So all I did was find the relevant recipe and change the expected value. Deleting the tarball and md5 files and refetching them is a good approach, but if it continues to fail, you might have to change the recipe file's expected values.

On Wed, Jan 19, 2011 at 7:32 PM, ScottEllis <> wrote:

Sorry, should have read your error better...

OE is complaining about checksums.

Look in the recipe for sgml-common-native on your machine


You'll see a
SRC_URI[md5sum] = "103c9828f24820df86e55e7862e28974"
SRC_URI[sha256sum] =

Those need to match the downloaded file.


Run the check yourself and you should get that same value.

md5sum $OVEROTOP/sources/sgml-common-0.6.3.tgz

If you don't match, then either someone changed the source and didn't update
the recipe or you pulled down a corrupt source file.

You can delete the sources/sgml-common-0.6.3.tgz and the md5 and run the
build of sgml-common-native again and that will download it again.

View this message in context:
Sent from the Gumstix mailing list archive at

Protect Your Site and Customers from Malware Attacks
Learn about various malware tactics and how to avoid them. Understand
malware threats, the impact they can have on your business, and how you
can protect your company and customers by using code signing.
gumstix-users mailing list