Re: python-django_1.8.18-1~bpo8+1_amd64.changes REJECTED
On Sat, 27 May 2017, Brian May wrote:
> > If upgrades from jessie to stretch without 1.8 delete user data,
>
> NO NO NO NO NO NO!
>
> Sorry, had to make that very clear.
>
> Upgrading to Django 1.10 will NOT DELETE OR CURRUPT DATA in anyway.
[…]
> As this happens inside the postinst script, when the migration fails,
> the package upgrade fails.
OK. Granted.
But that’s probably still RC (I’d personally consider it thus)
because a failing postinst during a dist-upgrade from oldstable
to stable can leave the system in a state that is hard to recover
from (e.g. you can’t fix the problem because something you need
to fix it is unconfigured or has its dependencies removed).
Again, just saying. I do not have any stake in Django, either
positive or negative.
bye,
//mirabilos
--
«MyISAM tables -will- get corrupted eventually. This is a fact of life. »
“mysql is about as much database as ms access” – “MSSQL at least descends
from a database” “it's a rebranded SyBase” “MySQL however was born from a
flatfile and went downhill from there” – “at least jetDB doesn’t claim to
be a database” ‣‣‣ Please, http://deb.li/mysql and MariaDB, finally die!
Reply to: