Note: This is a public test instance of Red Hat Bugzilla. The data contained within is a snapshot of the live data so any changes you make will not be reflected in the production Bugzilla. Email is disabled so feel free to test any aspect of the site that you want. File any problems you find or give feedback at bugzilla.redhat.com.

Bug 1188186

Summary: dnf ignores base.conf.cachedir when set after calling read_all_repos()
Product: [Fedora] Fedora Reporter: Jakub Filak <jfilak>
Component: dnfAssignee: Packaging Maintenance Team <packaging-team-maint>
Status: CLOSED DUPLICATE QA Contact: Fedora Extras Quality Assurance <extras-qa>
Severity: unspecified Docs Contact:
Priority: unspecified    
Version: 21CC: akozumpl, jberan, jsilhan, mluscon, packaging-team-maint, pnemade, rholy, tla
Target Milestone: ---   
Target Release: ---   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard:
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2015-02-13 10:38:36 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 Jakub Filak 2015-02-02 09:53:15 UTC
Description of problem:
I've been playing with dnf and found out I have to set dnf.Base.conf.cachedir to a desired value before I call dnf.Base.read_all_repos() otherwise my script dies with an exception. See Bug 1184943 comment 2 for more details.

Version-Release number of selected component (if applicable):
dnf-0.6.3-2.fc21.noarch

How reproducible:
always

Steps to Reproduce:
1.
2.
3.

Actual results:
dnf uses the system directory for its cache

Expected results:
dnf uses the provided directory for its cache or dnf documentation reflects this fact (or you can switch from dnf.Base.conf.cachedir variable to dnf.Base.conf.cachedir() function and spit a warning).

Comment 1 Michal Luscon 2015-02-13 10:38:36 UTC

*** This bug has been marked as a duplicate of bug 1184943 ***