Hide Forgot
Description of problem: doesn't work dnf command in chroot Version-Release number of selected component (if applicable): How reproducible: On host PC (Linux MyLinux 4.2.0-35-generic #40-Ubuntu SMP Tue Mar 15 22:15:45 UTC 2016 x86_64 x86_64 x86_64 GNU/Linux) execute chroot arm based fedora root file system and execute dnf in chroot Actual results: bash-4.3# dnf install git No handlers could be found for logger "dnf" Expected results: dnf have to working well Additional info:
solve this issue with mounting proc but there is other issue can dnf search but can't dnf install returns below logs bash-4.3# dnf install git -v cachedir: /var/cache/dnf DNF version: 1.1.6 repo: using cache for: rpmfusion-free-updates not found deltainfo for: RPM Fusion for Fedora 22 - Free - Updates not found updateinfo for: RPM Fusion for Fedora 22 - Free - Updates repo: using cache for: fedora not found deltainfo for: Fedora 22 - armhfp not found updateinfo for: Fedora 22 - armhfp repo: using cache for: updates repo: using cache for: rpmfusion-free not found deltainfo for: RPM Fusion for Fedora 22 - Free not found updateinfo for: RPM Fusion for Fedora 22 - Free rpmfusion-free-updates: using metadata from Sat Apr 16 22:37:24 2016. fedora: using metadata from Sat May 23 05:54:23 2015. updates: using metadata from Tue Apr 19 20:27:15 2016. rpmfusion-free: using metadata from Wed Aug 5 08:46:52 2015. Last metadata expiration check performed 0:31:51 ago on Fri Apr 22 03:09:38 2016. No package git available. Error: Unable to find a match.
Fedora 22 changed to end-of-life (EOL) status on 2016-07-19. Fedora 22 is no longer maintained, which means that it will not receive any further security or bug fix updates. As a result we are closing this bug. If you can reproduce this bug against a currently maintained version of Fedora please feel free to reopen this bug against that version. If you are unable to reopen this bug, please file a new report against the current release. If you experience problems, please add a comment to this bug. Thank you for reporting this bug and we are sorry it could not be fixed.