Bug 1415709
Summary: | DNF-makecache.timer still runs on rpm-ostree setup | ||
---|---|---|---|
Product: | [Fedora] Fedora | Reporter: | Patrick Uiterwijk <puiterwijk> |
Component: | rpm-ostree | Assignee: | Colin Walters <walters> |
Status: | CLOSED UPSTREAM | QA Contact: | Fedora Extras Quality Assurance <extras-qa> |
Severity: | unspecified | Docs Contact: | |
Priority: | unspecified | ||
Version: | 26 | CC: | jlebon, ngompa13, packaging-team-maint, rpm-software-management, vmukhame, walters |
Target Milestone: | --- | ||
Target Release: | --- | ||
Hardware: | Unspecified | ||
OS: | Unspecified | ||
Whiteboard: | |||
Fixed In Version: | Doc Type: | If docs needed, set a value | |
Doc Text: | Story Points: | --- | |
Clone Of: | Environment: | ||
Last Closed: | 2017-03-06 19:46:52 UTC | Type: | Bug |
Regression: | --- | Mount Type: | --- |
Documentation: | --- | CRM: | |
Verified Versions: | Category: | --- | |
oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | |
Cloudforms Team: | --- | Target Upstream Version: | |
Embargoed: |
Description
Patrick Uiterwijk
2017-01-23 13:46:42 UTC
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... (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'. |