Upstream, this software supports Python 3. Please provide a Python 3 package for Fedora. According to the Python packaging guidelines [0], 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 [1]. 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 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! [0] https://fedoraproject.org/wiki/Packaging:Python [1] https://fedoraproject.org/wiki/Packaging:Python#Example_common_spec_file
Upstream supports python 3 but there are no tags in their git repositories. We use pypi for sources and the version there is outdated. I opened a github issue here https://github.com/ASKBOT/django-extra-form-fields/issues/2 asking if they could generate a new pypi release with python 3 support so we won't need to package from a specific commit nor apply patches before building, does it sound reasonable?
This bug appears to have been reported against 'rawhide' during the Fedora 25 development cycle. Changing version to '25'.
Hi Athos! Thank you for taking the initiative. Yes, that absolutely does sound reasonable. However, if they won't respond, I think it would be better to package it from a commit.
Created attachment 1205400 [details] Patch adding python 2 and 3 subpackages Since upstream did not respond to our request mentioned in my previous comment, I prepared a patch from their commit in github which adds support to python3.
Here is a COPR build: https://copr.fedorainfracloud.org/coprs/ribeiro/fedora/build/458527/
Thank you for looking into this Athos. I'd try to avoid cherry-picking patches from upstream and would like to see a release. Askbot does not work on recent Fedoras anyways ("Branch master supports Django 1.8") Django-1.8 was in Fedora 23, we have Django-1.10 in rawhide.
(In reply to Matthias Runge from comment #6) > Thank you for looking into this Athos. I'd try to avoid cherry-picking > patches from upstream and would like to see a release. Ok, I agree with that. > Askbot does not work on recent Fedoras anyways ("Branch master supports > Django 1.8") > > Django-1.8 was in Fedora 23, we have Django-1.10 in rawhide. What should our approach be whenever 23 meets EOL and askbot is not supporting django 1.8?
In my understanding, we're keeping askbot, because we have ask.fedoraproject.org running. If it fails on current releases, I'd retire askbot. We could keep it alive in el6/7 branches.
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' of '25'. 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.
Fedora 25 changed to end-of-life (EOL) status on 2017-12-12. Fedora 25 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.
This is still relevant. Note that Django 2 drops Python 2 support. Either kill this, or update it to Python 3 please.
My vote would be to kill it, unless someone wants to maintain it. I can retire the package in 2 weeks.
Matthias, please retire.
thanks for the heads-up. done.
Thanks. Don't forget to obsolete it from python3-django, same as https://src.fedoraproject.org/rpms/python-django/c/c5e96280d692c5ac35e4f87a2168002abb0cbec2