Following the plan in https://bugs.debian.org/1085728, here's a patch to
cope with this package renaming.  It should be applied before the new
python-multipart version is uploaded to unstable.  Once
python3-python-multipart reaches testing, the Depends can be simplified
at your leisure to just "python3-python-multipart <!nocheck>".

By the way, when testing this, I noticed that your package's autopkgtest
fails if you try to run it in a simple unshare container (e.g. via
"sbuild --chroot-mode=unshare --run-autopkgtest") and if the host system
has a PostgreSQL server running.  This is exactly what the
"isolation-container" restriction is for ("The test wants to start
services or open network TCP ports"), so I'd recommend adding that to
the Restrictions field in debian/tests/control.

Thanks,

Dear maintainer,

I've prepared an NMU for gavodachs (versioned as 2.10+dfsg-1.1) and
uploaded it to DELAYED/10.  Please feel free to tell me if I should
delay it longer.

Regards,

Dear Colin,

I have to admit my Debian-Fu fails for figuring out what DELAYED/10
means.  If the question is whether I am fine with the NMU to go
ahead: I am.

Incidentally, if it's not asking too much, I'd be grateful for MRs
against https://salsa.debian.org/debian-astro-team/gavodachs for
these changes (the dependencies should already be there).

Thanks!

Dear Colin,

I have to admit my Debian-Fu fails for figuring out what DELAYED/10
means.  If the question is whether I am fine with the NMU to go
ahead: I am.

Incidentally, if it's not asking too much, I'd be grateful for MRs
against https://salsa.debian.org/debian-astro-team/gavodachs for
these changes (the dependencies should already be there).

Thanks!

https://www.debian.org/doc/manuals/developers-reference/pkgs.en.html#delayed-incoming

Thanks for confirming; I've rescheduled that NMU now for immediate
processing.

https://salsa.debian.org/debian-astro-team/gavodachs/-/merge_requests/5

Regards,