[Alexis Murzeau]
> Currently, packages which depends on python3-pycryptodome are:
> - python3-httpsig
> - python3-pysnmp4
Note, I had to patch python3-httpsig to get it to use the current
namespace. Feel free to NMU when needed, but remember to check out
debian/patches/2001-cryptodomex-namespace.
❦ 13 août 2018 22:05 +0200, Alexis Murzeau :
> 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
Hi,
On Fri, 06 Jul 2018 01:09:20 -0700 Andres Salomon
wrote:
>
>
> On Thu, Jun 14, 2018 at 1:57 AM, Petter Reinholdtsen
> 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.
On Thu, Jun 14, 2018 at 1:57 AM, Petter Reinholdtsen
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
[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
wit
I modified the package to provide/conflict with python-crypto, and that
seems to work. I didn't test upgrade paths, though.
--- a/debian/control2018-03-06 06:53:25.0 +
+++ b/debian/control2018-03-26 00:40:04.081250416 +
@@ -13,6 +13,8 @@
Package: python-pycryptodome
Arch
agree with Alexis Murzeau.
my suggest is pythonX-pycryptodome conflicts to and provides pythonX-crypto,
and pythonX-pycryptodomex is a new package.
BR.
Ning.
7 matches
Mail list logo
