Hello community, here is the log from the commit of package python-Django1 for openSUSE:Factory checked in at 2019-02-01 11:45:02 ++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++ Comparing /work/SRC/openSUSE:Factory/python-Django1 (Old) and /work/SRC/openSUSE:Factory/.python-Django1.new.28833 (New) ++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++
Package is "python-Django1" Fri Feb 1 11:45:02 2019 rev:8 rq:669477 version:1.11.18 Changes: -------- --- /work/SRC/openSUSE:Factory/python-Django1/python-Django1.changes 2019-01-10 15:22:28.654384081 +0100 +++ /work/SRC/openSUSE:Factory/.python-Django1.new.28833/python-Django1.changes 2019-02-01 11:45:04.100575722 +0100 @@ -1,0 +2,12 @@ +Tue Jan 29 09:08:11 UTC 2019 - Tomáš Chvátal <[email protected]> + +- Enable tests like on regular django to detect regressions for + the python2 based variant too + +------------------------------------------------------------------- +Tue Jan 29 09:03:12 UTC 2019 - Tomáš Chvátal <[email protected]> + +- Add patch to work well with sqlite 3.26 and newer: + * django-sqlite-326.patch + +------------------------------------------------------------------- @@ -4 +16 @@ -- Update to 1.11.18 +- Update to 1.11.18 (bsc#1120932, CVE-2019-3498) New: ---- django-sqlite-326.patch ++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++ Other differences: ------------------ ++++++ python-Django1.spec ++++++ --- /var/tmp/diff_new_pack.r049WK/_old 2019-02-01 11:45:05.148574646 +0100 +++ /var/tmp/diff_new_pack.r049WK/_new 2019-02-01 11:45:05.152574641 +0100 @@ -12,7 +12,7 @@ # license that conforms to the Open Source Definition (Version 1.9) # published by the Open Source Initiative. -# Please submit bugfixes or comments via http://bugs.opensuse.org/ +# Please submit bugfixes or comments via https://bugs.opensuse.org/ # @@ -32,8 +32,23 @@ Source1: https://www.djangoproject.com/m/pgp/Django-%{version}.checksum.txt#/Django-%{version}.tar.gz.asc Source2: %{name}.keyring Source99: python-Django1-rpmlintrc +Patch0: django-sqlite-326.patch +BuildRequires: %{python_module Jinja2 >= 2.9.2} +BuildRequires: %{python_module Pillow} +BuildRequires: %{python_module PyYAML} +BuildRequires: %{python_module argon2-cffi >= 16.1.0} BuildRequires: %{python_module base} +BuildRequires: %{python_module bcrypt} +BuildRequires: %{python_module docutils} +BuildRequires: %{python_module geoip2} +BuildRequires: %{python_module mock} +BuildRequires: %{python_module numpy} +BuildRequires: %{python_module pylibmc} +BuildRequires: %{python_module python-memcached >= 1.59} +BuildRequires: %{python_module pytz} BuildRequires: %{python_module setuptools} +BuildRequires: %{python_module sqlparse} +BuildRequires: %{python_module tblib} BuildRequires: fdupes BuildRequires: python-rpm-macros Requires: python-Pillow @@ -48,6 +63,11 @@ Provides: python-South = %{version} Obsoletes: python-South < %{version} BuildArch: noarch +# python-selenium is supported only on the Intel architecture +# Django testsuite runs just fine without, just skips the affected tests +%ifarch %{ix86} x86_64 +BuildRequires: %{python_module selenium} +%endif %ifpython2 Obsoletes: %{oldpython}-Django < %{version} Provides: %{oldpython}-Django = %{version} @@ -69,6 +89,7 @@ echo "`grep -e '^[0-9a-f]\{64\} Django-%{version}.tar.gz' %{SOURCE1} | cut -c1-64` %{SOURCE0}" | sha256sum -c %setup -q -n Django-%{version} +%patch0 -p1 %build %python_build @@ -99,6 +120,11 @@ popd } +%check +export LANG=en_US.UTF8 +export PYTHONDONTWRITEBYTECODE=1 +%python_expand PYTHONPATH=%{buildroot}%{$python_sitelib} $python tests/runtests.py + %post %{python_install_alternative django-admin.py django-admin} ++++++ django-sqlite-326.patch ++++++ From: Simon Charette <[email protected]> Date: Thu, 6 Dec 2018 11:37:43 -0500 Subject: Fixed #29182 -- Adjusted SQLite schema table alteration to support 3.26. SQLite 3.26 repoints foreign key constraints on table renames even when foreign_keys pragma is off which breaks every operation that requires a table rebuild to simulate unsupported ALTER TABLE statements. Fortunately the newly introduced legacy_alter_table pragma allows one to disable this behavior and restore the previous schema editor assumptions. Thanks Florian Apolloner, Christoph Trassl, Chris Lamb for the report and troubleshooting assistance. --- django/db/backends/sqlite3/schema.py | 2 ++ 1 file changed, 2 insertions(+) Index: Django-1.11.18/django/db/backends/sqlite3/schema.py =================================================================== --- Django-1.11.18.orig/django/db/backends/sqlite3/schema.py +++ Django-1.11.18/django/db/backends/sqlite3/schema.py @@ -24,10 +24,12 @@ class DatabaseSchemaEditor(BaseDatabaseS c.execute('PRAGMA foreign_keys') self._initial_pragma_fk = c.fetchone()[0] c.execute('PRAGMA foreign_keys = 0') + self.connection.cursor().execute('PRAGMA legacy_alter_table = ON') return super(DatabaseSchemaEditor, self).__enter__() def __exit__(self, exc_type, exc_value, traceback): super(DatabaseSchemaEditor, self).__exit__(exc_type, exc_value, traceback) + self.connection.cursor().execute('PRAGMA legacy_alter_table = OFF') with self.connection.cursor() as c: # Restore initial FK setting - PRAGMA values can't be parametrized c.execute('PRAGMA foreign_keys = %s' % int(self._initial_pragma_fk))
