Re: opkg_install_pkg: Package <name> md5sum mismatch. Either the opkg or the package index are corrupt.

[Denys Dmytriyenko <denis@denix.org>]

On Mon, May 04, 2015 at 02:50:17PM -0400, Denys Dmytriyenko wrote:
> On Fri, May 01, 2015 at 05:13:05PM -0500, Alejandro del Castillo wrote:
> > 
> > 
> > On 05/01/2015 11:06 AM, Denys Dmytriyenko wrote:
> > > Hi,
> > >
> > > Has anyone ever seen this message during <image>.do_rootfs task?
> > >
> > > Collected errors:
> > >  * opkg_install_pkg: Package <package> md5sum mismatch. Either the opkg or the package index are corrupt. Try 'opkg update'.
> > >  * opkg_install_cmd: Cannot install package <package>.
> > >
> > > We started seeing it on random packages inside the <image> few weeks ago on 
> > > different machines. At the time we had switched to bitbake 1.26. But even 
> > > trying different bitbake versions still occasionally caused the same error, so 
> > > the culprit is still unknwon. Using oe-core/daisy for now.
> > >
> > > Any comments or suggestions to where start looking would be appreciated! 
> > > Thanks.
> 
> > The error is saying that there is a mismatch between the registered package 
> > mds5sum and the actual md5sum of the package. On your log.do_rootfs log file 
> > you should find the opkg-cl command being called, which has an opkg.conf 
> > file as parameter. Inside the conf file, you will see the paths to the local 
> > repos being used to build your image.  Can you confirm that the registered 
> > md5sum for one of the problematic packages on the Package file on the repo 
> > doesn't match the actual package md5sum?
> 
> Yes, md5sum of the package doesn't match the one recorded in the Packages file 
> of the local feed.
> 
> BTW, this seems to only happen to arch-less packages from the "all" feed, 
> mainly packagegroups...

And then I realized that the failing packagegroup shouldn't really be 
arch-less! Apparently, I misplaced PACKAGE_ARCH = "${MACHINE_ARCH}" before 
inheriting packagegroup class. Oops!

-- 
Denys