| Summary: | Issue with RPM4 and do_rootfs | ||
|---|---|---|---|
| Product: | [Build System, Metadata & Runtime] OE-Core | Reporter: | condo4 <fabien.proriol> |
| Component: | devtools / tool chain | Assignee: | Joshua Lock <joshuagloe> |
| Status: | RESOLVED OBSOLETE | QA Contact: | |
| Severity: | normal | ||
| Priority: | Medium | CC: | meta.mr.watcher, meta.watcher |
| Version: | 2.0.2 | ||
| Target Milestone: | 2.2 | ||
| Hardware: | x86 | ||
| OS: | arm | ||
| Whiteboard: | |||
| OS type for building Yocto: | --- | Type of Regression: | --- |
| Verified: | Documentation change: | Don't know | |
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. 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... It appears the NEEDINFO has been answered. 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. Should be obsolete, not invalid. |
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.