avDescription of problem:
Version-Release number of selected component (if applicable):
Steps to Reproduce:
Err, sorry for that:
Upstream, this software supports Python 3. 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
It's ok to do this in Rawhide only, however, it would be greatly
appreciated if you could push it to Fedora 24 as well.
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!
Do you need any help adding Python 3 support to the RPM?
If you need more instructions, a [guide] for porting Python-based RPMs is available.
This bug appears to have been reported against 'rawhide' during the Fedora 25 development cycle.
Changing version to '25'.
This package has changed ownership in the Fedora Package Database. Reassigning to the new owner of this component.
This message is a reminder that Fedora 25 is nearing its end of life.
Approximately 4 (four) weeks from now Fedora will stop maintaining
and issuing updates for Fedora 25. 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'
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 25 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.
So - while the plugins have technically _compiled_ with Python3 for awhile, it wasn't until very recent releases that they actually functioned.
Anyhow, that work is now done -- should we take the plunge and fixup the packaging too?
Changing the version of this issue to rawhide to keep it active. Python 3 packaging will be addressed when the current HTCondor development version (8.7.x) is stabilized (version 8.8.0). (May 2018)
This bug appears to have been reported against 'rawhide' during the Fedora 28 development cycle.
Changing version to '28'.
Changing the version to 'rawhide', since we'll want to land this in F30. Tim, when we get closer, we should submit a Change proposal for completeness sake.
This bug appears to have been reported against 'rawhide' during the Fedora 30 development cycle.
Changing version to '30'.
I'll be uploading HTCondor 8.8.1 this week. This version will be able to build working Python3 bindings with 1 small patch.
Since this bug was filed, python2 was deprecated in Fedora. If you can, please switch to Python 3, rather than supporting both.
FEDORA-2019-f0f74bf64a has been submitted as an update to Fedora 29. https://bodhi.fedoraproject.org/updates/FEDORA-2019-f0f74bf64a
condor-8.8.4-1.fc29 has been pushed to the Fedora 29 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-2019-f0f74bf64a
condor-8.8.4-1.fc29 has been pushed to the Fedora 29 stable repository. If problems still persist, please make note of it in this bug report.