Currently, python3-jenkins-job-builder only provides /usr/bin/jenkins-jobs-3.4. This is inconvenient, since the name changes when there is new minor Python 3 version in Fedora. At the very least, this package should contain /usr/bin/jenkins-jobs-3. IMO there is even a better solution to this. There should be 3 subpackages: jenkins-job-builder python-jenkins-job-builder python3-jenkins-job-builder /usr/bin/jenkins-jobs-3 and /usr/bin/jenkins-jobs-3.4 would live in python3-jenkins-jobs (and they'd have their -2* counterparts in the python-jenkins-jobs package). /usr/bin/jenkins-jobs would live in jenkins-job-builder and be a symlink to /usr/bin/jenkins-jobs-3.X. jenkins-job-builder package would depend on python3-jenkins-job-builder. This is how several other packages solve this situation, e.g. dnf, and I think it's a proper solution here as well. Thanks for considering doing this.
This sounds like a great thing for the Python SIG to establish in the Python packaging guidelines. Is there any thing like that going on?
I've already opened ticket at fpc to address this: https://fedorahosted.org/fpc/ticket/558 Meanwhile I suggest to follow dnf as an example for applications with bindings as Slavek described above.
This bug appears to have been reported against 'rawhide' during the Fedora 24 development cycle. Changing version to '24'. More information and reason for this action is here: https://fedoraproject.org/wiki/Fedora_Program_Management/HouseKeeping/Fedora24#Rawhide_Rebase
This message is a reminder that Fedora 24 is nearing its end of life. Approximately 2 (two) weeks from now Fedora will stop maintaining and issuing updates for Fedora 24. 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 '24'. 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 24 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.
Fedora 24 changed to end-of-life (EOL) status on 2017-08-08. Fedora 24 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.