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 11, 2015 at 08:26:15AM +0200, Martin Jansa wrote:
> On Sat, May 09, 2015 at 09:36:01AM +0100, Richard Purdie wrote:
> > On Fri, 2015-05-08 at 17:09 -0400, Denys Dmytriyenko wrote:
> > > weston-init RDEPENDS on weston and kbd.
> > > 
> > > $ bitbake-diffsigs 1.0-r0.do_package_write_ipk.sigdata.eb3921bfc9623056f7ffaef4be8549ab 1.0-r0.do_package_write_ipk.sigdata.90c2978497847912cd64f66039927f7d 
> > > Hash for dependent task waylandweston_1.6.0.bb.do_packagedata changed from 551b3b5ac7b3c41bfced58b88db2d824 to f3eb9cd1861c186382e47f90e82e3295
> > > Hash for dependent task kbdkbd_2.0.1.bb.do_packagedata changed from 53a5dc88b80dc5ab559fbecd14277650 to 950fbc7fe3c33564e781743f2c260670
> > > 
> > > Then, comparing signatures for weston, for exaple, gives all the changes 
> > > caused by different DEFAULTTUNEs, TUNE_FEATURES and ARMPKGARCH - obviously, 
> > > since one machine is cortexa8, while another is cortexa9.
> > > 
> > > But why would an allarch package even care about machine tunes in dependant 
> > > packages, when it only RDEPENDS on them?
> > 
> > If A DEPENDS on B and B changes, the package name may change (thanks to
> > debian.bbclass) so A has to repackage. Very very annoying but
> > technically correct :/.
> > 
> > > And how should I fix this? Thanks.
> > 
> > See SIGGEN_EXCLUDERECIPES_ABISAFE in layer.conf of OE-Core. You probably
> > need to add weston-init to the list.
> 
> IIRC this won't help, he would need to add weston and kbd to
> SIGGEN_EXCLUDERECIPES_ABISAFE which will exclude it from signature of
> all other recipes as well.
> 
> Maybe you meant SIGGEN_EXCLUDE_SAFE_RECIPE_DEPS.
> 
> SIGGEN_EXCLUDE_SAFE_RECIPE_DEPS += "\
>   weston-init->weston \
>   weston-init->kbd \
> "

Thanks, Martin & Richard,

I can confirm that SIGGEN_EXCLUDE_SAFE_RECIPE_DEPS seems to work in my local 
tests, while SIGGEN_EXCLUDERECIPES_ABISAFE doesn't.

-- 
Denys