Dear maintainer,

As mentioned in
https://lists.debian.org/debian-backports/2021/12/msg00018.html, django
is failing some autopkgtests in backports
https://release.debian.org/britney/excuses_backports-stable.html

I think that we should be consider ourself lucky that nowadays we have a
tool such as autopkgtests to detect all of those things.

Having said that, I wonder if python3-django should indeed grow as many
Breaks as possible, as to help users (which includes me in some cases
heh) to avoid installing a combination of django and its external
extensions.


As a practical example, I think  Breaks on djangorestframework would be
quite important, given how widespread it is.


Having said all of this, at the moment I don't think there are strict
rules about this topic, so I'll leave it to your discretion.

Hi Mattia,

No objection in principle. But would we have to maintain / keep on top
of this list, or do you think simply Break-ing on the most common
package (as you say, djangorestframework) would be enough?


Regards,

I'd just put a Breaks on the proper versions, following whatever
autopkgtest/ci.debian.net is reporting, regardless of the "popularity"
of a package.

Hey Mattia,

Just found this email misfiled in my inbox — apologies. :/   Please
either: let me know which Breaks you'd like to add; a way of parsing
them, even by eye, from ci.debian.net (including the right page to
look at — I don't use this site very much!); or simply go ahead and add
them yourself to the repo and I'll upload. :)


Best wishes,

Chris