If I build an image with ssh-server-openssh in EXTRA_IMAGE_FEATURES, this causes packagegroup-core-ssh-openssh to be built and included in the image. If I build the image with RPM5 and then switch to RPM4, seemingly all of the other packages get rebuilt with rpm 4.x except for this one. Using bitbake-dumpsig I can see that the signature for packagegroup-core-ssh-openssh's do_package_write_rpm task does not include rpm-native.do_populate_sysroot, which accounts for this behaviour. Looking at other do_package_write_rpm signatures it seems that it's just allarch packagegroups that suffer from this - ${MACHINE_ARCH} packagegroups don't, nor do non-packagegroup allarch recipes.
Clearing 2.0 milestone
Whilst rpm4 is gone, it would still be good to understand why the rpm-native dependency goes missing...
diff --git a/meta/lib/oe/sstatesig.py b/meta/lib/oe/sstatesig.py index 4f115e9..5828a9d 100644 --- a/meta/lib/oe/sstatesig.py +++ b/meta/lib/oe/sstatesig.py @@ -40,7 +40,7 @@ def sstate_rundepfilter(siggen, fn, recipename, task, dep, depname, dataCache): # Only target packages beyond here # allarch packagegroups are assumed to have well behaved names which don't change between architecures/tunes - if isPackageGroup(fn) and isAllArch(fn): + if isPackageGroup(fn) and isAllArch(fn) and not isNative(depname): return False # Exclude well defined machine specific configurations which don't change ABI would appear to fix this...
http://git.yoctoproject.org/cgit.cgi/poky/commit/?id=b3e4a31cb4e79c601987570d1f49b03fc9781682