I have a system based on rpm-ostree (Atomic Host), so unless I specifically unlock it, I can't run dnf anyway. That means there's no need for dnf-makecache to actually do anything. It should detect I'm running rpm-ostree and just not refresh at all.
Why not add to your rpm-ostree compose a preset that disables dnf-automatic and dnf-makecache?
yeah, I think it should be done during build of rpm-ostree to set correct preset.
Reassigning...
https://github.com/rpm-software-management/dnf/pull/723
(In reply to Patrick Uiterwijk from comment #0) > I have a system based on rpm-ostree (Atomic Host), so unless I specifically > unlock it, I can't run dnf anyway. > That means there's no need for dnf-makecache to actually do anything. > > It should detect I'm running rpm-ostree and just not refresh at all. That makes sense, though is there a reason to even have dnf at all? Is it for repo queries and such?
This bug appears to have been reported against 'rawhide' during the Fedora 26 development cycle. Changing version to '26'.