[PKG-Openstack-devel] Bug#832338: Bug#832338: Also affects latest Sid - 3:9.0.1-2

[Thomas Goirand]

On 08/23/2016 10:01 PM, Turbo Fredriksson wrote:
> Please don't leave the package in this horrible, broken state!
> 
> 
> You need to package an older version to replace this if you can't
> get it to work. Granted, Sid is 'unstable', but that does NOT mean
> that it's the same as 'completely broken'. That's what 'testing' is
> for!
> 
> Waiting weeks (months?) for a working dashboard simply isn't acceptable!!

Hi there,

What I find not acceptable is the tone you're using here, disregarding
the work that's ongoing.

On 08/23/2016 10:01 PM, Turbo Fredriksson wrote:
> If I had enough knowledge in python/django, I would!
>
> But washing your hands and say "fix it yourself if having
> a completely broken package in Debian GNU/Linux" is RUDE,
> at best!
>
> We are Debian GNU/Linux! Our standards should be higher than
> that!

It's very easy to say "I don't know python/django", and at the same time
just shout loud "please fix". I stand by the side of Ondrej here. If you
think you can provide a fix, please do. If you don't, be patient, and
trust the package maintainers are working on the issue.

You don't realize is that what broke Horizon is the new version of
Django (ie: 1.10). The persons to blame here are the ones who maintain
python-django in Debian, who uploaded a version which broke more than 20
packages. They've been doing this way over and over again, without
considering slower careful transitions. That's IMO what isn't at the
level of the Debian standard for transitions.

An older version will work even less than the Mitaka version, for which
I contributed many Django 1.9 patches. Even more: the Mitaka version of
Horizon upstream doesn't even work with Django 1.9, and the Debian
package has patches which aren't applied upstream.

Also, I've been working a lot on Django 1.10 compatibility upstream.
This will come with version 1.10.0~b3 (ie: Newton b3), which is due for
next week, as one of the upstream contributors told me it's in a nice
shape now.

Please realize that the Django 1.10 compatibility isn't an easy thing to
work on. I already contributed half a dozen (not easy to write) patches
for it, and upstream authors also spent a large amount of time on it.

Be a little bit more patient, and you'll see that OpenStack Newton will
work, with a working dashboard.

Cheers,

Thomas Goirand (zigo)