Hide Forgot
Description of problem: Dnf won't synchronize cache when using --installroot Version-Release number of selected component (if applicable): dnf-2.0.0_1-76g9aae056.fc24.noarch How reproducible: always Steps to Reproduce: 1. dnf --installroot=/home/mhatina/tmp install dnf -v Actual results: Error: Failed to synchronize cache for repo 'fedora' Expected results: dnf is installed in installroot
Created attachment 1245760 [details] std-out
Created attachment 1245761 [details] std-err
Created attachment 1245762 [details] fedora-updates.repo
*** Bug 1417541 has been marked as a duplicate of this bug. ***
librepo.log?
Created attachment 1245775 [details] librepo.log
09:30:08 check_transfer_statuses: Transfer finished: https://mirrors.fedoraproject.org/metalink?repo=fedora-$releasever&arch=x86_64 (Effective url: https://mirrors.fedoraproject.org/metalink?repo=fedora-$releasever&arch=x86_64) Seems like $releasever is not expanded...
Created attachment 1245803 [details] fedora.repo
Fixed by https://github.com/rpm-software-management/dnf/pull/722
dnf-2.1.1-1.fc26 libdnf-0.8.0-1.fc26 has been submitted as an update to Fedora 26. https://bodhi.fedoraproject.org/updates/FEDORA-2017-65586fa42b
dnf-2.1.1-1.1.fc26, libdnf-0.8.0-1.fc26 has been pushed to the Fedora 26 testing repository. If problems still persist, please make note of it in this bug report. See https://fedoraproject.org/wiki/QA:Updates_Testing for instructions on how to install test updates. You can provide feedback for this update here: https://bodhi.fedoraproject.org/updates/FEDORA-2017-65586fa42b
dnf-2.2.0-1.fc26, libdnf-0.8.0-1.fc26 has been pushed to the Fedora 26 testing repository. If problems still persist, please make note of it in this bug report. See https://fedoraproject.org/wiki/QA:Updates_Testing for instructions on how to install test updates. You can provide feedback for this update here: https://bodhi.fedoraproject.org/updates/FEDORA-2017-65586fa42b
dnf-2.2.0-1.fc26, libdnf-0.8.0-1.fc26 has been pushed to the Fedora 26 stable repository. If problems still persist, please make note of it in this bug report.