Hi Pierre-Elliott,
>
> Hi,
>
> Thanks for your bug report!
>
> Did the latest django release change anything?
>
I went to have a look at what was installed and what was available (I’m mainly
tracking testing on this machine)
python3-django:
Installed: 2:3.2.9-2
Candidate: 2:3.2.9-2
Version table:
2:3.2.10-2 500
500 http://mirror.sov.uk.goscomb.net/debian
<http://mirror.sov.uk.goscomb.net/debian> unstable/main amd64 Packages
*** 2:3.2.9-2 990
990 http://mirror.sov.uk.goscomb.net/debian
<http://mirror.sov.uk.goscomb.net/debian> bookworm/main amd64 Packages
100 /var/lib/dpkg/status
2:2.2.24-1 500
500 http://mirror.sov.uk.goscomb.net/debian
<http://mirror.sov.uk.goscomb.net/debian> bullseye/main amd64 Packages
It was still broken with the installed package, and I pulled in 2:3.2.10-2 from
unstable to see if that fixed it, but I’m afraid I’m seeing the same problem.
Sorry. It’s an odd one really, I’ll see if I can look at the source code more
carefully soon (I develop Django apps myself, and haven’t seen this issue
before).
Kind regards,
CT.
