Your message dated Tue, 7 Jan 2020 13:54:49 -0500
with message-id
<CAB4XWXzudY+5wq6Yv7GWY0KafrvxdxeR9pGjbxXavDQMi=k...@mail.gmail.com>
and subject line Re: Re: Bug#935394: python3-django breaks python3-mysqldb
(<<1.3.13), but only python3-mysqldb 1.3.10 is available
has caused the Debian Bug report #935394,
regarding python3-django breaks python3-mysqldb (<<1.3.13), but only
python3-mysqldb 1.3.10 is available
to be marked as done.
This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.
(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact [email protected]
immediately.)
--
935394: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=935394
Debian Bug Tracking System
Contact [email protected] with problems
--- Begin Message ---
Package: python3-django
Version: 2:2.2.4-1
Severity: important
Dear Maintainer,
python3-django is marked as Breaks: python3-mysqldb (<< 1.3.13), but the
latest
and greatest version available in sid is python3-mysqldb 1.3.10.
This renders e.g. graphite-web uninstallable as that depends on both
python3-django
and python3-mysqldb.
I believe this was caused by the fix for bug #931592.
Perhaps the breaks version for python3-mysqldb can be lowered, or
maybe(?) a
new (upstream)version of python3-mysqldb is needed? In that case, I'm
happy to
file a bug agsinst python3-mysqldb.
Thanks,
Jakob
-- System Information:
Debian Release: bullseye/sid
APT prefers unstable
APT policy: (500, 'unstable')
Architecture: amd64 (x86_64)
Kernel: Linux 4.19.0-1-amd64 (SMP w/2 CPU cores)
Kernel taint flags: TAINT_OOT_MODULE, TAINT_UNSIGNED_MODULE
Locale: LANG=en_DK.UTF-8, LC_CTYPE=en_DK.UTF-8 (charmap=UTF-8),
LANGUAGE=en_DK.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Init: systemd (via /run/systemd/system)
LSM: AppArmor: enabled
Versions of packages python3-django depends on:
ii python3 3.7.3-1
ii python3-sqlparse 0.2.4-1
ii python3-tz 2019.2-1
Versions of packages python3-django recommends:
ii libjs-jquery 3.3.1~dfsg-3
Versions of packages python3-django suggests:
pn bpython3 <none>
pn geoip-database-contrib <none>
pn gettext <none>
pn ipython3 <none>
pn libgdal20 <none>
pn libsqlite3-mod-spatialite <none>
pn python-django-doc <none>
pn python3-bcrypt <none>
pn python3-flup <none>
pn python3-memcache <none>
pn python3-mysqldb <none>
pn python3-pil <none>
pn python3-psycopg2 <none>
pn python3-sqlite <none>
pn python3-yaml <none>
-- no debconf information
--- End Message ---
--- Begin Message ---
Version: 1.4.4-1
On Thu, 22 Aug 2019 09:30:54 -0700 "Chris Lamb" <[email protected]> wrote:
> Therefore I think the best solution would be to upload a new version
> of python3-mysqldb. I'm taking the liberty of reassigning (with a
> "reverse" affects for visibility) here in lieu of asking you to file a
> separate bug.
this was done a long time ago, closing
--- End Message ---
_______________________________________________
Python-modules-team mailing list
[email protected]
https://alioth-lists.debian.net/cgi-bin/mailman/listinfo/python-modules-team
