Some misconceptions resolved:
* This bug does not cause any data to be deleted.
* This bug does not cause any data to be currupted.
* This bug does not cause any data to be lost.
* This bug only affects one application. Out of many others that use Django.
The damage this bug does cause:
* If you
Hello Raphael,
On 05/24/2017 09:46 PM, Raphael Hertzog wrote:
> On Wed, 24 May 2017, Uwe Kleine-König wrote:
>> With my model that would be:
>>
>> - sid/testing has both, latest version and latest LTS (including
>>security)
>> - jessie-backports strictly follows django-lts and so shouldn't b
Hello, I hope you are well.
My name is Carol Marshall and I work for a Search Marketing company in
Sydney, Australia.
I was doing some research on your industry and I landed on your website.
Thing is i had a look at some of the other businesses who are currently
ranked on Page 1 and I truly belie
Accepted:
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512
Format: 1.8
Date: Sat, 20 May 2017 15:34:31 +0200
Source: python-django
Binary: python-django python3-django python-django-common python-django-doc
Architecture: source all
Version: 1.8.18-1~bpo8+1
Distribution: jessie-backports
Urgency:
Accepted:
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512
Format: 1.8
Date: Sat, 20 May 2017 15:34:31 +0200
Source: python-django
Binary: python-django python3-django python-django-common python-django-doc
Architecture: source all
Version: 1.8.18-1~bpo8+1
Distribution: jessie-backports
Urgency:
python-django_1.8.18-1~bpo8+1_amd64.changes uploaded successfully to localhost
along with the files:
python-django_1.8.18-1~bpo8+1.dsc
python-django_1.8.18.orig.tar.gz
python-django_1.8.18-1~bpo8+1.debian.tar.xz
python-django_1.8.18-1~bpo8+1_all.deb
python3-django_1.8.18-1~bpo8+1_all.deb
Neil Williams writes:
> Again, I also spotted this and thought it was the source. However,
> changing this causes the migration to fail with 1.10 as there are
> objects in this model which must be applied before
> lava_scheduler_app/0001_initial will complete. e.g. the AuthToken
> object is refer
On May 26, 2017 3:04:03 AM EDT, Adrian Bunk wrote:
>On Fri, May 26, 2017 at 05:46:22AM +, Scott Kitterman wrote:
>>
>>
>> On May 26, 2017 12:30:17 AM EDT, Neil Williams
>wrote:
>> >On Fri, 26 May 2017 04:11:49 +
>> >Scott Kitterman wrote:
>> >
>> >> I don't see any way to completely
On Fri, 26 May 2017 10:16:41 +0100
Neil Williams wrote:
> On Fri, 26 May 2017 10:05:58 +0100
> Neil Williams wrote:
>
> > On Fri, 26 May 2017 18:56:04 +1000
> > Brian May wrote:
> >
> > > Neil Williams writes:
> > >
> > > > django.db.migrations.exceptions.InconsistentMigrationHistory:
On Fri, 26 May 2017 10:05:58 +0100
Neil Williams wrote:
> On Fri, 26 May 2017 18:56:04 +1000
> Brian May wrote:
>
> > Neil Williams writes:
> >
> > > django.db.migrations.exceptions.InconsistentMigrationHistory:
> > > Migration lava_scheduler_app.0001_initial is applied before its
> > > dep
On Fri, 26 May 2017 18:56:04 +1000
Brian May wrote:
> Neil Williams writes:
>
> > django.db.migrations.exceptions.InconsistentMigrationHistory:
> > Migration lava_scheduler_app.0001_initial is applied before its
> > dependency linaro_django_xmlrpc.0001_initial on database
> > 'default'.
>
>
Signature for changes file was already seen at 2017-05-20 15:05:48.551935.
Please refresh the signature of the changes file if you want to upload it again.
===
Please feel free to respond to this email if you don't understand why
your files were rejected, or if you upload new files which addr
Neil Williams writes:
> django.db.migrations.exceptions.InconsistentMigrationHistory: Migration
> lava_scheduler_app.0001_initial is applied before its dependency
> linaro_django_xmlrpc.0001_initial on database 'default'.
Ok, I see what is going on now. Untested theory at the moment, but it
fits
On Fri, 26 May 2017 18:20:07 +1000
Brian May wrote:
> Neil Williams writes:
>
> > Applying linaro_django_xmlrpc.0001_initial... FAKED
>
> I am speculating this line might be very relevant. Taken from the
> Django 1.8 migration.
>
> Looks like this never had a migration before, so now need
python-django_1.8.18-1~bpo8+1_amd64.changes uploaded successfully to localhost
along with the files:
python-django_1.8.18-1~bpo8+1.dsc
python-django_1.8.18.orig.tar.gz
python-django_1.8.18-1~bpo8+1.debian.tar.xz
python-django_1.8.18-1~bpo8+1_all.deb
python3-django_1.8.18-1~bpo8+1_all.deb
On Fri, 26 May 2017 18:05:08 +1000
Brian May wrote:
> Neil Williams writes:
>
> > Upgrading directly to Stretch:
>
> Just to clarify: Was this upgrading the entire system to stretch, or
> just the relevant packages?
Starting point was 8.8 jessie, installed postgresql then installed
lava-ser
Neil Williams writes:
> Applying linaro_django_xmlrpc.0001_initial... FAKED
I am speculating this line might be very relevant. Taken from the Django
1.8 migration.
Looks like this never had a migration before, so now needs to be
faked. I wonder if this is what is triggering the Django 1.10 bu
Авторский способ заработка в интернете!
от 130 у.е. за день!
Показываю как заработать в интернете - это быстро и очень просто!
Перейти на сайт: http://git.com.tw/mc8m3.html
не получать почту
List-Unsubscribe
___
Python-modules-team mailing list
Python
Neil Williams writes:
> Upgrading directly to Stretch:
Just to clarify: Was this upgrading the entire system to stretch, or
just the relevant packages?
--
Brian May
___
Python-modules-team mailing list
Python-modules-team@lists.alioth.debian.org
htt
On Fri, May 26, 2017 at 05:46:22AM +, Scott Kitterman wrote:
>
>
> On May 26, 2017 12:30:17 AM EDT, Neil Williams wrote:
> >On Fri, 26 May 2017 04:11:49 +
> >Scott Kitterman wrote:
> >
> >> I don't see any way to completely resolve this before stretch
> >> releases other than removing l
20 matches
Mail list logo