From owner-freebsd-python@freebsd.org Wed Apr 22 06:41:18 2020 Return-Path: Delivered-To: freebsd-python@mailman.nyi.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mailman.nyi.freebsd.org (Postfix) with ESMTP id E5D472A82A6 for ; Wed, 22 Apr 2020 06:41:18 +0000 (UTC) (envelope-from bugzilla-noreply@freebsd.org) Received: from mailman.nyi.freebsd.org (unknown [127.0.1.3]) by mx1.freebsd.org (Postfix) with ESMTP id 496W6k5s8Sz3JBM for ; Wed, 22 Apr 2020 06:41:18 +0000 (UTC) (envelope-from bugzilla-noreply@freebsd.org) Received: by mailman.nyi.freebsd.org (Postfix) id C73B52A82A3; Wed, 22 Apr 2020 06:41:18 +0000 (UTC) Delivered-To: python@mailman.nyi.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mailman.nyi.freebsd.org (Postfix) with ESMTP id C6FEB2A82A2 for ; Wed, 22 Apr 2020 06:41:18 +0000 (UTC) (envelope-from bugzilla-noreply@freebsd.org) Received: from mxrelay.nyi.freebsd.org (mxrelay.nyi.freebsd.org [IPv6:2610:1c1:1:606c::19:3]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) server-signature RSA-PSS (4096 bits) client-signature RSA-PSS (4096 bits) client-digest SHA256) (Client CN "mxrelay.nyi.freebsd.org", Issuer "Let's Encrypt Authority X3" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 496W6k4xYPz3JBL for ; Wed, 22 Apr 2020 06:41:18 +0000 (UTC) (envelope-from bugzilla-noreply@freebsd.org) Received: from kenobi.freebsd.org (kenobi.freebsd.org [IPv6:2610:1c1:1:606c::50:1d]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) server-signature RSA-PSS (4096 bits)) (Client did not present a certificate) by mxrelay.nyi.freebsd.org (Postfix) with ESMTPS id 8C4EFE88A for ; Wed, 22 Apr 2020 06:41:18 +0000 (UTC) (envelope-from bugzilla-noreply@freebsd.org) Received: from kenobi.freebsd.org ([127.0.1.5]) by kenobi.freebsd.org (8.15.2/8.15.2) with ESMTP id 03M6fIx4095464 for ; Wed, 22 Apr 2020 06:41:18 GMT (envelope-from bugzilla-noreply@freebsd.org) Received: (from www@localhost) by kenobi.freebsd.org (8.15.2/8.15.2/Submit) id 03M6fIId095463 for python@FreeBSD.org; Wed, 22 Apr 2020 06:41:18 GMT (envelope-from bugzilla-noreply@freebsd.org) X-Authentication-Warning: kenobi.freebsd.org: www set sender to bugzilla-noreply@freebsd.org using -f From: bugzilla-noreply@freebsd.org To: python@FreeBSD.org Subject: [Bug 240820] www/py-django111: SQLite backend broken after 3.26 Date: Wed, 22 Apr 2020 06:41:18 +0000 X-Bugzilla-Reason: AssignedTo CC X-Bugzilla-Type: changed X-Bugzilla-Watch-Reason: None X-Bugzilla-Product: Ports & Packages X-Bugzilla-Component: Individual Port(s) X-Bugzilla-Version: Latest X-Bugzilla-Keywords: needs-qa X-Bugzilla-Severity: Affects Some People X-Bugzilla-Who: kai@FreeBSD.org X-Bugzilla-Status: Open X-Bugzilla-Resolution: X-Bugzilla-Priority: --- X-Bugzilla-Assigned-To: python@FreeBSD.org X-Bugzilla-Flags: maintainer-feedback? maintainer-feedback? merge-quarterly? X-Bugzilla-Changed-Fields: see_also Message-ID: In-Reply-To: References: Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable X-Bugzilla-URL: https://bugs.freebsd.org/bugzilla/ Auto-Submitted: auto-generated MIME-Version: 1.0 X-BeenThere: freebsd-python@freebsd.org X-Mailman-Version: 2.1.29 Precedence: list List-Id: FreeBSD-specific Python issues List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 22 Apr 2020 06:41:19 -0000 https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=3D240820 Kai Knoblich changed: What |Removed |Added ---------------------------------------------------------------------------- See Also| |https://github.com/django/d | |jango/pull/11986 --- Comment #4 from Kai Knoblich --- (In reply to rozhuk.im from comment #0) (In reply to Kubilay Kocak from comment #3) Hi, for the record here's a short overview: * The original PR #10733 with a slighty different patch (=3D diff against D= jango 2.x branch) got merged (2018-12-07) into the 2.x branch of Django but not in the 1.11 branch. * Two PRs #11610 (2019-07-30) and #11986 (2019-10-29), which contain the attached patch of this bug, were created by different users to get it merged into the Django 1.11 branch. Both PRs were rejected by upstream. Considering those facts and the following points: 1) SQLite 3.26 was introduced to the Ports tree via ports r486622 (2018-12-= 04). 2) This bug was reported nine months later after databases/sqlite3 was upda= ted to 3.26. 3) The issue with SQLite seems to be happen in some rare cases when using foreign key restraints. Upstream recommends as a workaround to rebuild the whole tables by not using migrations as described in [1]. 4) Django 1.11 is End-of-Life since April 2020 and there's already progress= in the Ports tree to switch the consumers of Django 1.11 to Django 2.2 (current LTS release), see also bug #245309. 5) I also tried to reproduce the issue with Django 1.11 and migrations from SQLite 3.25 to SQLite 3.31 but without any luck so far. Originally I was under the impression that the original PR #10733 was merged into all branches of Django but on further review it came to light that this isn't the case. After discussing the whole situation with koobs@ we believe the best way is= to leave the www/py-django111 port in its current state. because Django 1.11 is End-of-Life, the issue isn't reproducible and there's a workaround as noted= at 3) which might be another reason why upstream didn't backport that patch for Django 1.11. -- [1] https://docs.djangoproject.com/en/2.1/releases/2.0/#foreign-key-constraints= -are-now-enabled-on-sqlite --=20 You are receiving this mail because: You are the assignee for the bug. You are on the CC list for the bug.=