On Wed, Jan 19, 2022 at 10:09:36PM +0100, Ÿnérant wrote:
> However, Django-tables2 2.1.1 does not support Django 3.2, as I
> previously reported in this bug:
> https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=985774
>
> While there isn't any issue in Debian testing, this means that we must
> currently pin the package python3-django-tables2 from Debian testing if
> we want Django from backports.
So I've also added a Breaks in python3-django, however I haven't
uploaded that, leaving it up to whenever the next upload of
python3-django will be.
https://salsa.debian.org/python-team/packages/python-django/-/commit/07c7acd89a820b1a2eeef75c0542b8ccc9fc2ca4
This will make future updates of python3-django in bullseye-backports
uninstallable with the python3-django-table2 in bullseye.
> Is it so possible to upload django-tables2 in bullseye-backports to
> make it compatible with the version of Django that is in backports?
It surely is possible, however I don't want to take on that task myself,
hopefully somebody else will.
--
regards,
Mattia Rizzolo
GPG Key: 66AE 2B4A FCCF 3F52 DA18 4D18 4B04 3FCD B944 4540 .''`.
More about me: https://mapreri.org : :' :
Launchpad user: https://launchpad.net/~mapreri `. `'`
Debian QA page: https://qa.debian.org/developer.php?login=mattia `-
Attachment:
signature.asc
Description: PGP signature