Yes, port m2crypto to python3 it's the right way, but unfortunately I'm
not so skilled to migrate a software to python3.
I understand your vision, but my request was only this: there are no
ways to see python3-pykcs11 (v1.3.0-1 and later) and python-pykcs11
(v1.2.4-1) packages to coexists in the same branch? I don't expect an
updated and maintained python2 package, but I wish that the obsolete
library is still live as 'unmaintained' or 'orphan' to ensure a soft
transition.
in other words: I think that the new python3 package can be uploaded as
a new and not as a replacement for the version 1.2.4 that has been
kicked out from the the next stable branch.
--
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
