[Python-modules-team] Bug#822224: Bug#822224: Further changes

2016-04-23 Thread Neil Williams
On Sat, 23 Apr 2016 12:26:06 +1000
Brian May  wrote:

> Neil Williams  writes:
> 
> > python-django and python-django-tables2 from jessie work but if
> > either one is pulled in from jessie-backports without the other,
> > restarting apache2 causes a HTTP500.  
> 
> I am not sure I see how adding the Breaks header helps resolve this?

I was hoping that a backported package depending on django and
django-tables could use both at the same versions as are in jessie as
well as also working with django and django-tables backports together -
yet avoiding breakages by having only one of those from backports.
Over-reaching things a bit..

It's better to move to django1.8 for the upstream security support, so
that's what I'll do instead, updating the django-tables dependency to
the backport too, once available. So the Breaks: change in django-tables
would be wrong.

Thanks for taking the time on this.

-- 


Neil Williams
=
http://www.linux.codehelp.co.uk/



pgpQkj88sO957.pgp
Description: OpenPGP digital signature
___
Python-modules-team mailing list
Python-modules-team@lists.alioth.debian.org
http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/python-modules-team

[Python-modules-team] Bug#822224: Bug#822224: Further changes

2016-04-22 Thread Brian May
Neil Williams  writes:

> python-django and python-django-tables2 from jessie work but if either
> one is pulled in from jessie-backports without the other, restarting
> apache2 causes a HTTP500.

I am not sure I see how adding the Breaks header helps resolve this?
-- 
Brian May 

___
Python-modules-team mailing list
Python-modules-team@lists.alioth.debian.org
http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/python-modules-team


[Python-modules-team] Bug#822224: Bug#822224: Further changes

2016-04-22 Thread Neil Williams
On Fri, 22 Apr 2016 20:28:28 +1000
Brian May  wrote:

> Neil Williams  writes:
> 
> > i.e. django-tables 1.1.6 reveals a "bug" in django 1.7 so django
> > needs to be updated to 1.8 before django-tables 1.1.6 can be
> > upgraded/installed.  
> 
> Sorry, not sure I understand the need for the Breaks. What happens if
> you upgrade django-tables and then upgrade django?

python-django and python-django-tables2 from jessie work but if either
one is pulled in from jessie-backports without the other, restarting
apache2 causes a HTTP500.

It's a bit of a stretch to call this a bug in django1.7 I know but it's
a (documented) change from django 1.7 to 1.8 which the version of
django-tables in jessie cannot handle.

With this combination in a (otherwise working) VM:

lava-server   2016.3.post1-5591.7
python-django 1.7.7-1+deb8u4
python-django-tables2 1.1.6-1~bpo8+1

i.e. upgraded django-tables with django from jessie.

sudo apache2ctl restart

causes a HTTP500

...
  File "/usr/lib/python2.7/dist-packages/django_tables2/tables.py", line 185, 
in __new__
extra[field_name] = columns.library.column_for_field(field)
  File "/usr/lib/python2.7/dist-packages/django_tables2/columns/base.py", line 
37, in column_for_field
column = candidate.from_field(field)
  File "/usr/lib/python2.7/dist-packages/django_tables2/columns/base.py", line 
256, in from_field
return cls(verbose_name=field.verbose_name)
AttributeError: 'ManyToManyRel' object has no attribute 'verbose_name'

then upgrade python-django & python-django-common to 1.8 already in
backports, apache2ctl restart again and everything works. 

> Apart from the Breaks header, all other the changes look fine and I
> will look at making these changes to the unstable version.
> -- 
> Brian May 


-- 


Neil Williams
=
http://www.linux.codehelp.co.uk/



pgpPKA205HeB0.pgp
Description: OpenPGP digital signature
___
Python-modules-team mailing list
Python-modules-team@lists.alioth.debian.org
http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/python-modules-team

[Python-modules-team] Bug#822224: Bug#822224: Further changes

2016-04-22 Thread Brian May
Neil Williams  writes:

> i.e. django-tables 1.1.6 reveals a "bug" in django 1.7 so django needs
> to be updated to 1.8 before django-tables 1.1.6 can be
> upgraded/installed.

Sorry, not sure I understand the need for the Breaks. What happens if
you upgrade django-tables and then upgrade django?

Apart from the Breaks header, all other the changes look fine and I will
look at making these changes to the unstable version.
-- 
Brian May 

___
Python-modules-team mailing list
Python-modules-team@lists.alioth.debian.org
http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/python-modules-team