Description of problem: I find several differences in behaviour of --installroot between yum and dnf. But it does not make sense to me to report the unless there is clear documentation of this option and what behaviour is correct. First: documentation in dnf is very short: --installroot=<path> set install root which I find as regression from yum documentation: --installroot=root Specifies an alternative installroot, relative to which all packages will be installed. Think of this like doing "chroot <root> yum" except using --installroot allows yum to work before the chroot is created. Note: You may also want to use the option --releasever=/ when creating the installroot as otherwise the $releasever value is taken from the rpmdb within the installroot (and thus. will be empty, before creation). Configuration Option: installroot But even the yum expanded documentation does not state, how installroot relate to yum.repos.d/* files. Are they taken from host of from installroot? Log files are placed to host /var/log or to installroot? Version-Release number of selected component (if applicable): dnf-0.6.2-1.fc21.noarch
thanks for the report, it can be better documented.
This bug appears to have been reported against 'rawhide' during the Fedora 22 development cycle. Changing version to '22'. More information and reason for this action is here: https://fedoraproject.org/wiki/Fedora_Program_Management/HouseKeeping/Fedora22
Ping. Any progress here?
No progress yet, sorry.
This bug appears to have been reported against 'rawhide' during the Fedora 23 development cycle. Changing version to '23'. (As we did not run this process for some time, it could affect also pre-Fedora 23 development cycle bugs. We are very sorry. It will help us with cleanup during Fedora 23 End Of Life. Thank you.) More information and reason for this action is here: https://fedoraproject.org/wiki/BugZappers/HouseKeeping/Fedora23
This bug will be fixed by pullrequest: https://github.com/rpm-software-management/dnf/pull/428
This bug was accidentally moved from POST to MODIFIED via an error in automation, please see mmccune with any questions
Fixed as part of DNF 2.0 release.