Hi Colin, On Wed, Nov 06, 2024 at 06:00:43PM +0000, Colin Watson wrote: > This bug is starting to accumulate other Python 3.13-related bugs that > it blocks, so I'd like to agree a plan. > [...] > So, my proposal is as follows: > > * Rename python-multipart source package to python-python-multipart, > and its binary package to python3-python-multipart. Yes, it's a bit > ugly, but there are currently 13 other binary packages in the archive > whose names start with "python3-python-", so there's precedent, and > it matches the way we usually transform PyPI names into Debian > package names. python3-python-multipart should have Breaks/Replaces: > python3-multipart (<< 0.1) (the oldest release of > https://pypi.org/project/multipart/, which is also newer than any > release of https://pypi.org/project/python-multipart/). > [...] > > How does this sound? Sandro, I'd especially like to get your feedback > on this, because doing a source+binary package rename in an NMU sounds > ... painful, especially if it turns out later that there wasn't > consensus.
My thoughts... (1) I agree with this renaming and Colin's general proposals, especially as upstream has now renamed their import. (2) Please take a look at https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1073445#25 (though I'm not proposing changing the package name in this NMU). (3) I would suggest tweaking Colin's proposal: the other binary/source packages currently (build-)depending on python3-multipart should all be upgraded *first* to change their python3-multipart dependency to read: python3-multipart (<< 0.1) | python3-python-multipart This way, when the python3-multipart package is renamed, these other packages will continue to work without change (unless the newer version of python3-multipart that I'm planning to NMU breaks them anyway). (4) With the maintainer's current non-responsiveness, it may make sense to salvage these three interlinked packages (fastapi, python-multipart, sqlmodel). That will take longer than an NMU, but will help with the longer-term maintenance of these packages. (I would propose transferring them to the Debian Python Team if they are salvaged.) Best wishes, Julian
