On 9/17/21 10:54 AM, Carsten Schoenert wrote:
Hi,
Am Tue, Sep 14, 2021 at 09:18:18PM +0200 schrieb Paul Gevers:
...
Currently this regression is blocking the migration of python-django to
testing [1]. Of course, python-django shouldn't just break your
autopkgtest (or even worse, your package), but it seems to me that the
change in python-django was intended and your package needs to update to
the new situation.
If this is a real problem in your package (and not only in your
autopkgtest), the right binary package(s) from python-django should
really add a versioned Breaks on the unfixed version of (one of your)
package(s). Note: the Breaks is nice even if the issue is only in the
autopkgtest as it helps the migration software to figure out the right
versions to combine in the tests.
I did a quick import of the currently most recent version 5.24.0 and did
afterwards a rebuild of this version.
The built of the binary packages and also the autopkgtest works without
further needed adjustments so updating django-axes to a recent version
would be enough to fix this issue.
Thanks! I have also checked for the compatibility of axes code with
Django 3.2. All the changes need seem to be already in
place[1][2][3][4]. I will work to update the packaging to newer version.
Links:
1)
https://github.com/jazzband/django-axes/commit/b4a71de81fd2d1c316c819fff4c68581ada6208d
2)
https://github.com/jazzband/django-axes/commit/876b6f3dc4377daa6e1d2a1244ea7a86bf952695
3)
https://github.com/jazzband/django-axes/commit/2e074eebc5752dbedde5f66ece0d9a38bc8694cd
4)
https://github.com/jazzband/django-axes/commit/4986c240a6ccea6f52c1a18ca08f56ad2d6fa6de#diff-b8833de46a20430033cf627e5843a9a394547e8d6dd62d1a6c05e1f31039244e
--
Sunil
