Processing commands for cont...@bugs.debian.org:
> reassign 807097 django-compat
Bug #807097 [django-hijack] incompatible with django1.9
Bug reassigned from package 'django-hijack' to 'django-compat'.
No longer marked as found in versions 1.0.10-1.
Ignoring request to alter fixed versions of bug #
reassign 807097 django-compat
found 807097 1.0.7-2
affects 807097 + python-django-hijack
thanks
On Tue, 8 Dec 2015 13:41:16 +0530
Senthil Kumaran S wrote:
> On Tuesday 08 December 2015 01:04 PM, Brian May wrote:
> >>> From your stack trace it would appear that the calling
> >>> application - dja
On Tuesday 08 December 2015 01:04 PM, Brian May wrote:
>>> From your stack trace it would appear that the calling application -
>>> django-hijack - doesn't actually use add_to_builtins, however it uses
>>> the file from django-compat that tries to import the symbol anyway.
>>
>> ARRRGGHHH! OK, th
Neil Williams writes:
>> From your stack trace it would appear that the calling application -
>> django-hijack - doesn't actually use add_to_builtins, however it uses
>> the file from django-compat that tries to import the symbol anyway.
>
> ARRRGGHHH! OK, that looks like hijack should test the i
reassign 807097 django-hijack
retitle 807097 incompatible with django1.9
found 807097 1.0.10-1
thanks
On Sun, 06 Dec 2015 20:21:17 +1100
Brian May wrote:
> Sorry, accidentally sent private response by mistake. Resending.
>
> Neil Williams writes:
>
> > Downgrading to 1.8 in testing fixes the
Processing commands for cont...@bugs.debian.org:
> reassign 807097 django-hijack
Bug #807097 [python-django] python-django: Undeclared removal of previously
supported features causes crashes
Bug reassigned from package 'python-django' to 'django-hijack'.
No longer marked as found in versions pyth
Brian May writes:
from django.template import Origin, TemplateDoesNotExist
This will only work with Django 1.7.x and 1.9.x, not Django 1.8.x
However Django 1.8.x doesn't have the reference from
django/template/loaders/filesystem.py, so shouldnt be triggering this.
Unless you somehow ended
Brian May writes:
> So looks like Django 1.8 does have it, but it moved. Which perhaps
> should have been a warning that maybe this was a private symbol not
> intended for apps to use.
For the record, it looks like add_to_builtins was not present in django
1.9rc1, which was the version I believe
Raphael Hertzog writes:
> On Sat, 05 Dec 2015, Neil Williams wrote:
>> http://paste.debian.net/341382/
>
> So this one is fairly obvious, I already replied that it's
> django.template.base.Origin that you should have used in the first place
> since where the code actually is... relying on the fac
Sorry, accidentally sent private response by mistake. Resending.
Neil Williams writes:
> Downgrading to 1.8 in testing fixes the problem, so if this isn't the
> root cause, something else in 1.9 is producing a misleading traceback.
> There's no reference to add-to-builtins in the lava-server cod
On Sun, 06 Dec 2015 13:03:21 +1100
Brian May wrote:
I'm going to see if I can create a LAVA job tomorrow which demonstrates
the problem. It'll need to use changes which are still in upstream
review (the combined changes that are planned for the pending 2015.12
release) and I'll install django1.7
On Sat, 5 Dec 2015 22:06:05 +0100
Raphael Hertzog wrote:
> On Sat, 05 Dec 2015, Neil Williams wrote:
> > http://paste.debian.net/341382/
>
> So this one is fairly obvious, I already replied that it's
> django.template.base.Origin that you should have used in the first
> place since where the c
On Sun, 06 Dec 2015 13:03:21 +1100
Brian May wrote:
> Raphael Hertzog writes:
>
> > This one is actually documented, add_to_builtins has never been a
> > public API.
> >
> > https://docs.djangoproject.com/en/1.9/releases/1.9/#django-template-base-add-to-builtins-is-removed
> >
>
> I thought
Raphael Hertzog writes:
> This one is actually documented, add_to_builtins has never been a public
> API.
>
> https://docs.djangoproject.com/en/1.9/releases/1.9/#django-template-base-add-to-builtins-is-removed
I thought this was removed in Django 1.8 - I remember as it caused me
significant prob
On Sat, 05 Dec 2015, Neil Williams wrote:
> http://paste.debian.net/341382/
So this one is fairly obvious, I already replied that it's
django.template.base.Origin that you should have used in the first place
since where the code actually is... relying on the fact that it was
also imported in djang
Package: python-django
Version: 1.9-1
Severity: grave
Justification: renders package unusable
http://paste.debian.net/341382/
http://paste.debian.net/341383/
I had previously tested django1.9 from experimental and have prepared changes
which allow
lava-server to run and for all the unit tests t
16 matches
Mail list logo
