|Summary:||python-bucky: Provide a Python 3 subpackage|
|Product:||[Fedora] Fedora||Reporter:||Petr Viktorin <pviktori>|
|Component:||python-bucky||Assignee:||Jonathan Steffan <jonathansteffan>|
|Status:||CLOSED RAWHIDE||QA Contact:||Fedora Extras Quality Assurance <extras-qa>|
|Version:||26||CC:||ishcherb, jonathansteffan, mhroncok, piotr1212|
|Fixed In Version:||python-bucky-2.3.0-1.fc29||Doc Type:||If docs needed, set a value|
|Doc Text:||Story Points:||---|
|Last Closed:||2018-05-29 11:48:49 UTC||Type:||Bug|
|oVirt Team:||---||RHEL 7.3 requirements from Atomic Host:|
|Cloudforms Team:||---||Target Upstream Version:|
|Bug Depends On:|
Description Petr Viktorin 2016-08-15 09:06:32 UTC
Upstream, this software supports Python 3 (although they do claim the support is still very young). Please provide a Python 3 package for Fedora. According to the Python packaging guidelines , software must be packaged for Python 3 if upstream supports it. The guidelines give detailed information on how to do this, and even provide an example spec file . The current best practice is to provide subpackages for the two Python versions (called "Common SRPM" in the guidelines). Alternatively, if nothing depends on your Python2 package, you can just switch to Python 3 entirely. It's OK to do this in Rawhide only, however, it would be greatly appreciated if you could push it to Fedora 25 as well. If you need more instructions, a guide for porting Python-based RPMs is available at . If anything is unclear, or if you need any kind of assistance with the porting, you can ask on IRC (#fedora-python on Freenode), or reply here. We'll be happy to help!  https://fedoraproject.org/wiki/Packaging:Python  https://fedoraproject.org/wiki/Packaging:Python#Example_common_spec_file  http://python-rpm-porting.readthedocs.io/
Comment 1 Dominika Krejčí 2016-09-01 09:01:42 UTC
Hello Jonathan, how is it going? Do you need any help?
Comment 2 Fedora End Of Life 2017-02-28 10:06:31 UTC
This bug appears to have been reported against 'rawhide' during the Fedora 26 development cycle. Changing version to '26'.
Comment 3 Iryna Shcherbina 2018-01-09 17:15:19 UTC
I have opened a Pagure PR with update to the latest version (2.3.0) and provided a Python 3 subpackage: https://src.fedoraproject.org/rpms/python-bucky/pull-request/1 Could you please review the changes?
Comment 4 Fedora End Of Life 2018-05-03 08:35:40 UTC
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.
Comment 5 Fedora End Of Life 2018-05-29 11:48:49 UTC
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.
Comment 6 Miro Hrončok 2018-05-29 12:36:27 UTC