Hi Mattia,
> However I noticed that you only applied that patch to the
> bullseye-backports branch. I wonder why not just push it to "sid" as
> well, and reduce the delta between bookworm and bullseye-backports to be
> as little as possible?
Definitely agree with the principle about minimising
On Fri, Apr 09, 2021 at 08:54:30AM +0100, Chris Lamb wrote:
> Thank you for your in-depth investigation and patch. I have applied it
> and am uploading 2:2.2.19-1~bpo10+2 as I speak/type which will close
> this bug.
Uploads to -backports don't close bugs, so this bug wasn't close.
However I
[adding Jens Reinsberger to CC]
Hi Wookey,
> It seems to work fine. We have a fairly complicated database schema in
> our django app, but we are not doing anything very 'fancy' (like
> transaction rollbacks). Despite much reading of issues, bug reports
> and commits, I have not been able to
I have just built a patched version of python-django which changes the
check for python3-mysqldb >= 1.3.13 so that it runs on the existing
1.3.10 stable version.
It seems to work fine. We have a fairly complicated database schema in
our django app, but we are not doing anything very 'fancy' (like
Hi Jens,
(Just to save myself looking it up again, the version in buster right
now is 1.3.10-2.)
> Unfortunately it needs python3-mysqldb >= 1.3.13 in order to work with
> MySQL/MariaDB, which is not available in backports.
So, I'd prefer not to upload/maintain this backport myself as I have
Package: python3-django
Version: 2:2.2.17-2~bpo10+1
Severity: normal
Dear Maintainer,
since the stable version of python3-django is utterly out of date and
not maintained anymore upstream, I wanted to use the backports version.
Unfortunately it needs python3-mysqldb >= 1.3.13 in order to work
6 matches
Mail list logo
