| Summary: | Mixing systemd and non-systemd builds for different MACHINEs confuses dnf | ||
|---|---|---|---|
| Product: | [Build System, Metadata & Runtime] OE-Core | Reporter: | Richard Purdie <richard.purdie> |
| Component: | devtools / tool chain | Assignee: | Richard Purdie <richard.purdie> |
| Status: | RESOLVED FIXED | QA Contact: | |
| Severity: | normal | ||
| Priority: | Medium+ | CC: | meta.mr.watcher, meta.watcher |
| Version: | 2.2 | ||
| Target Milestone: | 4.99 | ||
| Hardware: | x86 | ||
| OS: | Multiple | ||
| Whiteboard: | |||
| OS type for building Yocto: | --- | Type of Regression: | --- |
| Verified: | Documentation change: | No (bug/feature does not impact docs) | |
|
Description
Richard Purdie
2017-09-01 07:29:24 UTC
After a lot of digging into dnf, libdnf and libsolv, here's the report I submitted to the upstream: https://bugzilla.redhat.com/show_bug.cgi?id=1497188 Let's see what the maintainers think. I got a comment out of upstream: "But in this particular case we don't have a decision yet. LIBDNF is now under reconstruction and we don't know if new design changes will go in favor of that bug report." https://github.com/rpm-software-management/libdnf/pull/312#issuecomment-347641033 So let's see how their refactoring goes. As it doesn't seem we'll get a fix from upstream for this soon, and RP has a patch in progress that sidesteps the issue by limiting the set of RPMs visible to dnf only to those actually needed, I guess the bug can be reassigned. The rpm filtering code at least resolves this issue so it doesn't concern us any more, even if there are seemingly problematic issues in libdnf. |