Description of problem: Looks like the move to flake8-3.0.4 in f26 has broken this package. This is mitigated by a patch already in upstream [1], but the package then breaks during the test run in a different way. An issue has been filed upstream [2]. Version-Release number of selected component (if applicable): * python-osrf-pycommon-0.1.2-2.fc26 * python-flake8-3.0.4-1.fc26 How reproducible:100% Additional info: [1] https://github.com/osrf/osrf_pycommon/commit/a317efbb9e28f72881b81a9bf782be30f2cc7fbb [2] https://github.com/osrf/osrf_pycommon/issues/28 Thanks, --scott
I found the root cause of the error (improper exclude path) and reported it in the upstream bug. I also found the cause of the second error - the python3 flake8 binary needs to be run on python 3 code. I added a call to the versioned flake8 binary in the fedora patch, but I'm not sure if its upstream-able as I"m not sure other distributions follow the same naming guidelines for parallel python installations.
This bug appears to have been reported against 'rawhide' during the Fedora 26 development cycle. Changing version to '26'.
This message is a reminder that Fedora 26 is nearing its end of life. Approximately 4 (four) weeks from now Fedora will stop maintaining and issuing updates for Fedora 26. It is Fedora's policy to close all bug reports from releases that are no longer maintained. At that time this bug will be closed as EOL if it remains open with a Fedora 'version' of '26'. Package Maintainer: If you wish for this bug to remain open because you plan to fix it in a currently maintained version, simply change the 'version' to a later Fedora version. Thank you for reporting this issue and we are sorry that we were not able to fix it before Fedora 26 is end of life. If you would still like to see this bug fixed and are able to reproduce it against a later version of Fedora, you are encouraged change the 'version' to a later Fedora version prior this bug is closed as described in the policy above. Although we aim to fix as many bugs as possible during every release's lifetime, sometimes those efforts are overtaken by events. Often a more recent Fedora release includes newer upstream software that fixes bugs or makes them obsolete.
python-osrf-pycommon-0.1.4-1.fc28 has been submitted as an update to Fedora 28. https://bodhi.fedoraproject.org/updates/FEDORA-2018-5452c388c9
python-osrf-pycommon-0.1.4-1.fc27 has been submitted as an update to Fedora 27. https://bodhi.fedoraproject.org/updates/FEDORA-2018-97857d1946
python-osrf-pycommon-0.1.4-1.fc27 has been pushed to the Fedora 27 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-2018-97857d1946
python-osrf-pycommon-0.1.4-1.fc28 has been pushed to the Fedora 28 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-2018-5452c388c9
Fedora 26 changed to end-of-life (EOL) status on 2018-05-29. Fedora 26 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.
python-osrf-pycommon-0.1.4-1.fc27 has been pushed to the Fedora 27 stable repository. If problems still persist, please make note of it in this bug report.
python-osrf-pycommon-0.1.4-1.fc28 has been pushed to the Fedora 28 stable repository. If problems still persist, please make note of it in this bug report.