8968 2016-01-21 10:46:56 +0000 Issue with RPM4 and do_rootfs 2016-03-22 12:42:07 +0000 1 1 7 Build System, Metadata & Runtime OE-Core devtools / tool chain 2.0.2 x86 arm RESOLVED OBSOLETE Medium normal 2.2 1 fabien.proriol joshuagloe meta.mr.watcher meta.watcher --- --- Don't know oldest_to_newest 58049 0 fabien.proriol 2016-01-21 10:46:56 +0000 Hello, If I try to build a Jethro filesystem with RPM4 (using comments RPM4 in local.conf), do_rrotfs failed because for each rpm, RPM say that operating system is not the good one. I fixed for me this issue by add rpm.RPMPROB_FILTER_IGNOREOS in smart-rpm4-fixes.patch : ...... + probfilter |= rpm.RPMPROB_FILTER_IGNOREARCH + probfilter |= rpm.RPMPROB_FILTER_IGNOREOS + if force or reinstall: ...... For information, my architecture is cortexa9-vfp-neon and rpm file extention is .cortexa9_vfp_neon.rpm I don't know if this issue is due to a miss configuration on my side, or, a real bug in Yocto. If someone have the same issue, I can propose the fix on the mailing list. 58184 1 joshuagloe 2016-01-25 14:34:35 +0000 I can't reproduce this using stock OE Core master. Can you share which DISTRO and MACHINE you're using, as well as anything else you think might help me to reproduce. 58187 2 fabien.proriol 2016-01-25 14:51:19 +0000 I use own distro and a machine based on zynq CPU... My machine conf file contains: require conf/machine/include/tune-zynq.inc MACHINE_FEATURES += " zynq " The distro is neer poky distro config file, but I added RPM4 option to avoid it in local.conf: PREFERRED_VERSION_rpm = "4.11.2" PREFERRED_VERSION_rpm-native = "4.11.2" RPMROOTFSDEPENDS_remove = "rpmresolve-native:do_populate_sysroot" If I have more time this week, I will try to understand why it's different that your test... 58405 3 sjolley.yp.pm 2016-02-01 22:56:50 +0000 It appears the NEEDINFO has been answered. 60284 4 joshuagloe 2016-03-22 12:41:42 +0000 As RPM4 was incomplete, buggy and unmaintained we decided to remove it from OE-Core. We'll be happy to add it back should someone provide a fully functioning solution, but as we don't currently have the manpower to develop and maintain that solution its removal was deemed to be the best option. 60285 5 joshuagloe 2016-03-22 12:42:07 +0000 Should be obsolete, not invalid.