Re: [PATCH 1/1] autoconf-archive: inherit allarch and fix package splitting

["André Draszik" <git@andred.net>]

On Tue, 2017-11-14 at 11:41 +0000, Burton, Ross wrote:
> On 14 November 2017 at 11:34, Burton, Ross <ross.burton@intel.com> wrote:
> 
> > But don't we remove the old version from the feeds, or does that only
> > happen if the arch matches?
> > 
> 
> Well the feed pruning is working correctly:

Not for me. I created a dummy package foo_0.1.bb, with PACKAGE_ARCH =
"${MACHINE_ARCH}"

after bitbake foo:
$ build.pyro > find tmp/deploy/ipk/ -name foo*ipk
tmp/deploy/ipk/tgm_r3/f/foo/foo-dbg_0.1-r0_tgm_r3.ipk
tmp/deploy/ipk/tgm_r3/f/foo/foo-dev_0.1-r0_tgm_r3.ipk
tmp/deploy/ipk/tgm_r3/f/foo/foo_0.1-r0_tgm_r3.ipk

Removing the PACKAGE_ARCH line from that recipe and rebuilding foo gives me:

$ build.pyro > find tmp/deploy/ipk/ -name foo*ipk
tmp/deploy/ipk/mips32r2el-24kec-nf/f/foo/foo-dbg_0.1-r0_mips32r2el-24kec-
nf.ipk
tmp/deploy/ipk/mips32r2el-24kec-nf/f/foo/foo-dev_0.1-r0_mips32r2el-24kec-
nf.ipk
tmp/deploy/ipk/mips32r2el-24kec-nf/f/foo/foo_0.1-r0_mips32r2el-24kec-nf.ipk
tmp/deploy/ipk/tgm_r3/f/foo/foo-dbg_0.1-r0_tgm_r3.ipk
tmp/deploy/ipk/tgm_r3/f/foo/foo-dev_0.1-r0_tgm_r3.ipk
tmp/deploy/ipk/tgm_r3/f/foo/foo_0.1-r0_tgm_r3.ipk


If I bump the version, I am still left with the MACHINE_ARCH packages
(doesn't matter if I bump the version before or after the change to
PACKAGE_ARCH):
$ build.pyro > find tmp/deploy/ipk/ -name foo*ipk
tmp/deploy/ipk/mips32r2el-24kec-nf/f/foo/foo-dbg_0.2-r0_mips32r2el-24kec-
nf.ipk
tmp/deploy/ipk/mips32r2el-24kec-nf/f/foo/foo-dev_0.2-r0_mips32r2el-24kec-
nf.ipk
tmp/deploy/ipk/mips32r2el-24kec-nf/f/foo/foo_0.2-r0_mips32r2el-24kec-nf.ipk
tmp/deploy/ipk/tgm_r3/f/foo/foo-dbg_0.1-r0_tgm_r3.ipk
tmp/deploy/ipk/tgm_r3/f/foo/foo-dev_0.1-r0_tgm_r3.ipk
tmp/deploy/ipk/tgm_r3/f/foo/foo_0.1-r0_tgm_r3.ipk

So of course do_rootfs will pick the outdated version.

Is that an ipk / OPKG issue? Should something be removing the old packages
from deploy?


Cheers,
Andre'