Description of problem: connmanctl is not installed when I installed connman package on fedora22 Version-Release number of selected component (if applicable): connman-1.30 How reproducible: always Steps to Reproduce: 1. dnf install connman 2. connmanctl 3. Actual results: connmanctl -bash: connmanctl: command not found Expected results: sucessfully executed connman Additional info: F23 already fixed the problem. Please update it also f22. http://pkgs.fedoraproject.org/cgit/connman.git/commit/?h=f23&id=5a0f799a37bede373d452fbc82b54337c41d5f36
ping?
connman-1.31-1.fc22 has been submitted as an update to Fedora 22. https://bodhi.fedoraproject.org/updates/FEDORA-2016-006f4f3762
connman-1.31-1.fc23 has been submitted as an update to Fedora 23. https://bodhi.fedoraproject.org/updates/FEDORA-2016-116de3465a
connman-1.31-1.fc22 has been pushed to the Fedora 22 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-2016-006f4f3762
connman-1.31-1.fc23 has been pushed to the Fedora 23 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-2016-116de3465a
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.