Bug 1229442

Summary: dnf has issues with --enablerepo AND --installroot
Product: [Fedora] Fedora Reporter: Ali Akcaagac <aliakc>
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: 22CC: jsilhan, mluscon, packaging-team-maint, pnemade, rholy, tim.lauridsen, vmukhame
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-07-24 12:08:57 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 Ali Akcaagac 2015-06-08 18:45:24 UTC
dnf has issues with --enablerepo AND --installroot.

Behaviour yum:

yum install --enablerepo=myrepo.repo \
            --installroot=/chrootdir

yum searches for the name repo.repo in /chrootdir/etc/var/yum.reops.d which is the correct behaviour because the myrepo.repo is a temporarely created file that should be valid just for the chrootdir. it is created automatically and then after its process finished remove again.

dnf install --enablerepo=myrepo.repo \
            --installroot=/chrootdir

searches in /etc/yum.repos.d for that file. though all operations should be done in /chrootdir and the host should not be touched at all. yum behaves correctly while dnf does not.

NOTE: please take my apologizes here but i'm just a small step away from becoming totally pissed off because the transition from yum to dnf (valued from the amount of work and changes we have been through so far) is a total PITA. i am also a small step away from bringing this mess up on the devel list.

Comment 1 Radek Holy 2015-07-24 12:08:57 UTC

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