Control: reassign -1 python3-django
Control: affects -1 src:python-django-postgres-extra
On Thu, Oct 09, 2025 at 07:04:52AM +0200, Bas Couwenberg wrote:
Source: python-django-postgres-extra
Version: 2.0.9-1
Severity: serious
Justification: autopkgtest failure
Dear Maintainer,
The autopkgtest of your package is failing with postgresql-common (284) which
depends on postgresql-18:
[...]
77s if excluding_constraints_and_indexes:
77s > assert target_constraints == {}
77s E AssertionError: assert {'tests_d5121...ne, ...}, ...} == {}
77s E
77s E Left contains 7 more items:
77s E {'tests_d51210b1_age_not_null': {'check': False,
77s E 'columns': ['age'],
77s E 'definition': None,
77s E 'foreign_key': None,
77s E 'index': False,...
77s E
77s E ...Full output truncated (52 lines hidden), use '-vv' to show
77s
77s tests/test_schema_editor_clone_model_to_schema.py:72: AssertionError
https://ci.debian.net/packages/p/python-django-postgres-extra/testing/amd64/65001064/
I think this was caused by
https://git.postgresql.org/gitweb/?p=postgresql.git;a=commitdiff;h=14e87ffa5,
but looking at the implementation of this test, it would need a change
to Django for django-postgres-extra to be able to filter out not-null
constraints here. And when I looked into what that would involve in
Django, I found this:
https://github.com/django/django/pull/19910
I tried cherry-picking that and confirmed that it fixes
django-postgres-extra's tests. Chris, does cherry-picking this into the
version of Django in unstable sound reasonable to you? I'm happy to do
the work - just wanted to get a second opinion.
Thanks,
--
Colin Watson (he/him) [[email protected]]
