Re: [PATCH 1/1] tune-core2.inc: PACKAGE_EXTRA_ARCHS causes wrong packages install into image

[Richard Purdie <richard.purdie@linuxfoundation.org>]

On Tue, 2012-05-22 at 12:30 +0200, Koen Kooi wrote:
> Op 22 mei 2012, om 12:15 heeft Robert Yang het volgende geschreven:
> 
> > There is a bug if we:
> > 1) bitbake diffutils with MACHINE=crownbay
> > 2) bitbake diffutils with MACHINE=qemux86
> > 3) bitbake core-image-sato with MACHINE=crownbay
> > 
> > Then the diffutils.i586 would be installed to the crownbay's image, this
> > is because diffutils.i586 is newer than diffutils.core2, both of
> > deploy/rpm/i586 and deploy/rpm/core2 are in the dbpath, so rpm will
> > select the newer one (diffutils.i586). This caused by:
> > 
> > PACKAGE_EXTRA_ARCHS_tune-core2 = "${PACKAGE_EXTRA_ARCHS_tune-x86} i386 i486 i586 i686 core2"
> > 
> > The PACKAGE_EXTRA_ARCHS will cause the deploy/rpm/i586 in the crownbay's
> > dbpath, so any pkg which is needed by the image of both crownbay and
> > qemux86, if the i586 one is newer than the core2, it would be installed
> > into crownbay's image.
> 
> This is a bug in RPM not respecting the arch priorities. Changing PACKAGE_EXTRA_ARCHS is the wrong way to 'fix' that.

Agreed, the core2 package should have higher priority compared to the
i586 package and be the one that "wins" and gets installed. This is a
bug in the rpm package/rootfs backend that needs to get fixed.

Cheers,

Richard