DevHeads.net

Intent to upgrade Django in f29 to 2.1

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 <a href="https://bugzilla.redhat.com/show_bug.cgi?id=1611025" title="https://bugzilla.redhat.com/show_bug.cgi?id=1611025">https://bugzilla.redhat.com/show_bug.cgi?id=1611025</a>

If I don't hear anything against it until Monday, I'll merge rawhide into
F29.

Matthias

Comments

Re: Intent to upgrade Django in f29 to 2.1

By =?UTF-8?B?TWlyb... at 08/22/2018 - 04:51

On 22.8.2018 10:59, Matthias Runge wrote:
2 packages don't. Sorry if that was confusing. They only build in f29
(that is without Django 2.1).

Re: Intent to upgrade Django in f29 to 2.1

By Matthias Runge at 08/22/2018 - 06:13

On Wed, Aug 22, 2018 at 11:51:34AM +0200, Miro HronĨok wrote:
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?

Re: Intent to upgrade Django in f29 to 2.1

By =?UTF-8?B?TWlyb... at 08/22/2018 - 12:12

On 22.8.2018 13:13, Matthias Runge wrote:
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?