[Python-modules-team] Bug#886291: pycryptodome naming

[Alexis Murzeau]

Hi,

On Fri, 06 Jul 2018 01:09:20 -0700 Andres Salomon <dilinger at queued.net>
wrote:
> 
> 
> On Thu, Jun 14, 2018 at 1:57 AM, Petter Reinholdtsen <pere at hungry.com> 
> wrote:
> > [Andres Salomon]
> >>  I modified the package to provide/conflict with python-crypto, and 
> >> that
> >>  seems to work.  I didn't test upgrade paths, though.
> > 
> > Would it be better to introduce a extra set of Crypto compatible 
> > packages?
> > It would allow those packages using the current namespace to keep 
> > working
> > without changes, and allow them to use the "compat" packages if they
> > want to.
> 
> 
> It sounds like that's the intent upstream, according to
> (https://www.pycryptodome.org/en/latest/src/introduction.html)?
> 
> I think in the ideal scenario, there's a python3-pycryptodome binary 
> package
> that conflicts/provides python3-crypto and uses the Crypto namespace,
> and a python3-pycryptodomex binary package that uses the Cryptodome
> namespace.  Just the latter would probably be fine, though.
> 

Currently, packages which depends on python3-pycryptodome are:
- python3-httpsig
- python3-pysnmp4

python3-httpsig exists only in unstable.
python3-pysnmp4 exists in stable but depends on python3-crypto and the
version in testing/unstable is the same.

I suggests this to ensure an upgrade path while renaming around this
package:
- Change httpsig and pysnmp4 dependencies on python3-pycryptodome to
"python3-pycrytodomex (>= 3.6.1-3) | python3-pycrytodome (<< 3.6.1-3)"
- Wait both package to enter testing (at this time, python3-pycrytodomex
doesn't exists yet)
- Update python3-pycryptodome to version 3.6.1-3 to build pycryptodome
instead of pycryptodomex
- Introduce python3-pycryptodomex at version 3.6.1-3
- After python3-pycryptodomex version 3.6.1-3 enter testing, maybe
update httpsig and pysnmp4 dependencies on python3-pycryptodome to
"python3-pycrytodomex" only

Adding maintainers of python3-pysnmp4 as they are involved in this scenario.

This scenario assume python3-pycryptodome 3.6.1-3 won't be released
before or while this scenario is in progress.

Maybe also add Provides/Replaces/Conflicts for the new
python3-pycryptodomex on the previous python3-pycryptodome (<< 3.6.1-3)
package.

I'm not sure about the timing of the upload of python3-pycryptodomex as
it is new. Will it be delayed ? That would cause breakage between the
python3-pycryptodome 3.6.1-3 entering unstable and python3-pycryptodomex
entering unstable.

-- 
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/20180813/6dfa363e/attachment-0002.sig>