[Python-modules-team] Bug#886291: Debian package transition: Rename package and reuse old name with new content

[Alexis Murzeau]

Hi,

Thanks for your replies.

On 19/08/2018 12:18, Simon McVittie wrote:
> According to apt-file(1), python3-pycryptodome contains
> /usr/lib/python3/dist-packages/Cryptodome, which you use via "import
> Cryptodome". If you're renaming packages anyway, would it be better for
> the package containing /usr/lib/python3/dist-packages/Cryptodome to be
> the python3-cryptodome package?
>
> (My reasoning is that the name you import is the name of the "ABI",
> the same way the ABI of, for example, libdbus is represented by its
> SONAME libdbus-1.so.3, which we translate into libdbus-1-3 as a Debian
> package name.)

The naming pycryptodome and pycryptodomex are the ones used by upstream
on PyPi. So the goal is to have the same names as upstream uses for
these too different packages. pycryptodome on PyPi use
`dist-packages/Crypto` which is meant to be a drop-in replacement for
python-crypto.


> It's OK for packages in unstable to be uninstallable or unbuildable for
> a short time, as long as Depends/Breaks/Conflicts or RC bugs ensure that
> the brokenness doesn't propagate into testing.
>
> For instance, if you are going ahead with your renaming plan, you could
> give the new packages a versioned Breaks on python3-httpsig (<< H) and
> python3-pysnmp4 (<< S), where H is the first version of python3-httpsig
> that has been modified to use/expect the new (py)cryptodome(x) package
> layout, and S is the corresponding version of python3-pysnmp4.
>
>     smcv
>

On 20/08/2018 16:11, Gianfranco Costamagna wrote:
> 
> 
>> I'm not sure of the transition policies when handling transitions on
>> testing and unstable only (ie: not involving stable).
>> But that should ensure there is no breakage between package in the archive.
> 
> 
> if you are just renaming a package,, and the reverse-deps are not too many,
> better avoid transitional packages, ask for a transition slot on release.d.o,
> open bugs (MBF?) with patches, and raise to serious once RT acks the transition.
> 
> G.
> 

Ok thanks, I will consider the transition slot and adding breaks to the
new pycryptodome packages over the old reverse-dependencies.
Actually, pycryptodome is under the ongoing transition of python 3.7 so
any package changes will wait the end of that one.

-- 
Alexis Murzeau
PGP: B7E6 0EBB 9293 7B06 BDBC  2787 E7BD 1904 F480 937F

-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 833 bytes
Desc: OpenPGP digital signature
URL: <http://alioth-lists.debian.net/pipermail/python-modules-team/attachments/20180823/76f87577/attachment.sig>