Quantcast

bluez reporting checksum mismatch during omap3 build

classic Classic list List threaded Threaded
4 messages Options
Reply | Threaded
Open this post in threaded view
|  
Report Content as Inappropriate

bluez reporting checksum mismatch during omap3 build

FatalError
Noob:
Development environment:
  Windows 7 64bit
  Oracle VirtualBox 64 bit V4.1.6 r74713
  Hosting Ubuntu 10.04 LTS- Lucid Lynx (32-bit)  
  Bitbake  1.12.0
  DISTRO_VERSION    "2011.03"

NOTE: Learned you cannot use Ubuntu 11.10, cost me ~5 days

1st Tested the development environment using: bitbake helloworld-image  
Built without errors.

Per "Using the Open Embedded Build System for Overo Series": http://www.gumstix.org/software-development/open-embedded/61-using-the-open-embedded-build-system.html 
2nd Tested using:  bitbake omap3-console-image

I ended up with the following errors:
NOTE: Running task 2012 of 5154 (ID: 742, /home/fatal_error/oe/oe-dev/recipes/bluez/bluez4_4.89.bb, do_fetch)
NOTE: package bluez4-4.89-r8.0: task do_fetch: Started
ERROR: The checksums for "/home/fatal_error/oe/sources/bluez-4.89.tar.gz" did not match.
  MD5: expected "67fd9ad2852ce01f01b16ddd2336d1ea", got "bb0a5864b16c911993d2bceb839edb3c"
  SHA256: expected "922e1a9c894c8667fc92f536c26553e8f094a676e96fb409bc384dd70f5ddde7", got "b493530e0cf6798e578a6ce322f513d2ab9a9c1d1987e93acb96974e86b52f1e"

NOTE: package bluez4-4.89-r8.0: task Fetch failed: http://www.kernel.org/pub/linux/bluetooth/bluez-4.89.tar.gz checksum mismatch.: Failed
ERROR: Function 'Fetch failed: http://www.kernel.org/pub/linux/bluetooth/bluez-4.89.tar.gz checksum mismatch.' failed
ERROR: Task 742 (/home/fatal_error/oe/oe-dev/recipes/bluez/bluez4_4.89.bb, do_fetch) failed with exit code '1'
ERROR: '/home/fatal_error/oe/oe-dev/recipes/bluez/bluez4_4.89.bb' failed

Build Configuration:
BB_VERSION        = "1.12.0"
METADATA_BRANCH   = "overo-2011.03"
METADATA_REVISION = "d042ac9"
TARGET_ARCH       = "arm"
TARGET_OS         = "linux-gnueabi"
MACHINE           = "overo"
DISTRO            = "angstrom"
DISTRO_VERSION    = "2011.03"
TARGET_FPU        = "hard"

Have checked  OE, bluez and bluez-utils, all report at newest versions.

Before the error message it is reported: NOTE: Angstrom DOES NOT support bluez-libs because bluez-libs 3.x has been replaced by bluez4.

Anyone else have this or similar issue.



Thanks
Reply | Threaded
Open this post in threaded view
|  
Report Content as Inappropriate

Re: bluez reporting checksum mismatch during omap3 build

FatalError
Found this;
Dealing with checksum mismatch

It happens that incorrect checksums are being committed or that upstream changes tarballs without changing the filename. In both cases, OE will bail out and complain about a mismatch in checksums (unless OE_ALLOW_INSECURE_DOWNLOADS is enabled). Here are the steps a developer should take to resolve the issue safely.

    Look through "mtn --diffs --no-merges log conf/checksums.ini| less" and find the person who committed the current md5sum.
    Contact them and ask them to md5sum their copy again. Compare results if they still have the original tar file against which the original checksum was generated.

Then we have three possible scenarios.

    the original committer does not have the original file anymore or is unsure about its integrity. In that case, please write to openembedded-devel@lists.linuxtogo.org. Don't do anything further.
    the original committer generates the same md5sum as you, indicating an error in the original commit. In this case we can safely commit the update. Indicate in your commit message that yours and the other person's md5sum matched
    the numbers don't match. Then we need to consult upstream and ask if they changed the tarball. Sadly this is something that commonly happens. After confirmation from upstream we can update checksums.ini.

Currently don't know how to Look through "mtn --diffs --no-merges log conf/checksums.ini| less" and find the person who committed the current md5sum. Will figure it out if need to, but does anyone know how and can share with me how?

Thanks
Reply | Threaded
Open this post in threaded view
|  
Report Content as Inappropriate

Re: bluez reporting checksum mismatch during omap3 build

k7gada
In reply to this post by FatalError
Have you tried downloading the correct checksum file???

If you havn't then heres how to do it

download the correct checksum file  by googling the checksum

you can get the bluez-4.89.tar.gz with the correct checksum here.....
http://pkgs.fedoraproject.org/repo/pkgs/bluez/bluez-4.89.tar.gz/67fd9ad2852ce01f01b16ddd2336d1ea/

and place it in /home/fatal_error/oe/sources/

and bitbake again...it should work...

Reply | Threaded
Open this post in threaded view
|  
Report Content as Inappropriate

Re: bluez reporting checksum mismatch during omap3 build

FatalError
Huh google the chksum, didn't know it worked that way.
Thanks

Past that issue and now on to the next one.
Loading...