Source: python-django Control: found -1 python-django/2:4.0.6-1 Severity: serious Tags: sid bookworm User: debian...@lists.debian.org Usertags: breaks Control: affects -1 django-mailman3 django-invitations Control: affects -1 django-oauth-toolkit django-tables Control: affects -1 djangorestframework-filters factory-boy Control: affects -1 python-django-braces python-django-celery-results Control: affects -1 python-django-dbconn-retry python-django-extensions Control: affects -1 python-django-extra-views Control: affects -1 python-django-rest-framework-guardian
Dear maintainer(s),With a recent upload of python-django the autopkgtest of django-mailman3, django-invitations, django-oauth-toolkit, django-tables, djangorestframework-filters, factory-boy, python-django-braces, python-django-celery-results, python-django-dbconn-retry, python-django-extensions, python-django-extra-views and python-django-rest-framework-guardian fail in testing when that autopkgtest is run with the binary packages of python-django from unstable. It passes when run with only packages from testing.
I note that the changelog has this:"This security release mitigates the issue, but we have identified improvements to the Database API methods related to date extract and truncate that would be beneficial to add to Django 4.1 before it's final release. This will impact 3rd party database backends using Django 4.1 release candidate 1 or newer, until they are able to update to the API changes. We apologize for the inconvenience."
I guess that means that these breakages might be intentional, but even if all this is to be expected, it would be good to add a *versioned* Breaks to python-django3 for all the packages that it really breaks (not just the autopkgtest).
Currently this regression is blocking the migration of python-django to testing [1].
Paul
OpenPGP_signature
Description: OpenPGP digital signature
