[Cc: ftpmaster - please see the discussion below and, if necessary, the earlier discussion in this bug report. We would really like your input on this bug - how should we proceed?]
On Sun, Nov 24, 2024 at 03:11:17AM -0500, Sandro Tosi wrote: > > My preference would be to follow PyPI's naming and rename as follows: > > > > * python-multipart source: python-python-multipart > > * python3-multipart binary: python3-python-multipart > > > > And although it's a bit odd, we could package the new python3-multipart > > with a transitional dependency on python3-python-multipart until all its > > real reverse-dependencies have been updated in a stable release. > > > > But maybe you have another idea? > > yes i do. I just uploaded python-multipart_0.0.17-2 to experimental > with the *binary* package name change from python3-multipart to > python3-python-multipart (common python3- prefix plus the module > import name) and without the compatibility `multipart` module in it. > Once it clears NEW, please check it does what you need it to do. > > I will not rename the source package. PyPI has it as python-multipart, > upstream gh has it as python-multipart, and debian already has it as > src:python-multipart so that's not gonna change. > > the module you want to introduce is named `multipart` in PyPI, so you > can introduce a package in debian with src:multipart name (no, there's > no requirement whatsoever to have the `python` prefix on source > package names) which is currently available, and a > bin:python3-multipart, probably with a conflict with the old version > of that package. Unfortunately, the ftpmasters have made the decision that they now require new source package names that are specific to Python to have a source package name of python-* (unless the package name is already clearly Python specific). So we will have to discuss this with them - copying in ftpmaster for their input on this question. > Along with this, i will *not* handle the transition from the old > bin:python3-multipart for its reverse dependencies, so please have a > look if you wanna take care of that or ask the support of someone > else. > > Once you confirm the 0.0.17-2 package works as for your needs, i'll > upload it to unstable and your work can continue, Best wishes, Julian
