Hello,
sorry for the late notice; Django 2.1 was recently released, and I intend to update Django in F29 to version 2.1.
Apparently, all depending packages still build, all the details in https://bugzilla.redhat.com/show_bug.cgi?id=1611025
If I don't hear anything against it until Monday, I'll merge rawhide into F29.
Matthias
On 22.8.2018 10:59, Matthias Runge wrote:
Hello,
sorry for the late notice; Django 2.1 was recently released, and I intend to update Django in F29 to version 2.1.
Apparently, all depending packages still build, all the details in https://bugzilla.redhat.com/show_bug.cgi?id=1611025
2 packages don't. Sorry if that was confusing. They only build in f29 (that is without Django 2.1).
On Wed, Aug 22, 2018 at 11:51:34AM +0200, Miro Hrončok wrote:
On 22.8.2018 10:59, Matthias Runge wrote:
Hello,
sorry for the late notice; Django 2.1 was recently released, and I intend to update Django in F29 to version 2.1.
Apparently, all depending packages still build, all the details in https://bugzilla.redhat.com/show_bug.cgi?id=1611025
2 packages don't. Sorry if that was confusing. They only build in f29 (that is without Django 2.1).
Ah, sorry, I've misread the comment.
Django-avatar: seems to be failing, according to the classifiers, it doesn't support Django-2.0 either, although commits hint something else. This year already saw 2 commits to upstream, nothing connected to 2.1.
django-countries: has seen more commits upstream this year.
However, these packages would be broken by the upgrade :(
Thoughts?
On 22.8.2018 13:13, Matthias Runge wrote:
On Wed, Aug 22, 2018 at 11:51:34AM +0200, Miro Hrončok wrote:
On 22.8.2018 10:59, Matthias Runge wrote:
Hello,
sorry for the late notice; Django 2.1 was recently released, and I intend to update Django in F29 to version 2.1.
Apparently, all depending packages still build, all the details in https://bugzilla.redhat.com/show_bug.cgi?id=1611025
2 packages don't. Sorry if that was confusing. They only build in f29 (that is without Django 2.1).
Ah, sorry, I've misread the comment.
Django-avatar: seems to be failing, according to the classifiers, it doesn't support Django-2.0 either, although commits hint something else. This year already saw 2 commits to upstream, nothing connected to 2.1.
django-countries: has seen more commits upstream this year.
However, these packages would be broken by the upgrade :(
Thoughts?
Keep the update in rawhide for now, try to get the packages fixed and if it cannot be done before beta freeze, don't push the update?
python-devel@lists.fedoraproject.org
-
Matthias Runge -
Miro Hrončok