[thud, warrior, zeus][meta-python] Conundrum: python-pycrypto and python-pycryptodome

[thud, warrior, zeus][meta-python] Conundrum: python-pycrypto and python-pycryptodome

[Tim Orling]

python-pycrypto [1] is rather old and un-maintained [2].
python-pycryptodome [3] is more modern and is basically a drop in
replacement. However, the two cannot be installed at the same time.
Instead, one would install python-pycryptodomex which does not conflict
with the paths of python-pycrypto [4].

In an effort to enable packagegroup-meta-python [5] and meta-python-image
[6], one runs into the existing python-pycrypto and python-pycryptodome
recipes attempting to install the same files to the same locations (no
surprise, they are providing the same libraries).

For the stable branches, should we rename python-pycryptodome to
python-cryptodomex and PROVIDES python-pycryptodome?

[1]
https://git.openembedded.org/meta-openembedded/tree/meta-python/recipes-devtools/python/python-pycrypto_2.6.1.bb?h=zeus
[2] https://github.com/dlitz/pycrypto/issues/285
[3]
https://git.openembedded.org/meta-openembedded/tree/meta-python/recipes-devtools/python/python-pycryptodome_3.4.11.bb?h=zeus
[4]
https://stackoverflow.com/questions/48155294/what-is-pycryptodomex-and-how-does-it-differ-from-pycryptodome
[5]
https://git.openembedded.org/meta-openembedded/tree/meta-python/recipes-core/packagegroups/packagegroup-meta-python.bb?h=zeus#n21
[6]
https://git.openembedded.org/meta-openembedded/tree/meta-python/recipes-core/images/meta-python-image.bb?h=zeus

Re: [thud, warrior, zeus][meta-python] Conundrum: python-pycrypto and python-pycryptodome

[Adrian Bunk]

On Wed, Dec 04, 2019 at 09:00:20PM -0800, Tim Orling wrote:
> python-pycrypto [1] is rather old and un-maintained [2].
> python-pycryptodome [3] is more modern and is basically a drop in
> replacement. However, the two cannot be installed at the same time.
> Instead, one would install python-pycryptodomex which does not conflict
> with the paths of python-pycrypto [4].
> 
> In an effort to enable packagegroup-meta-python [5] and meta-python-image
> [6], one runs into the existing python-pycrypto and python-pycryptodome
> recipes attempting to install the same files to the same locations (no
> surprise, they are providing the same libraries).
> 
> For the stable branches, should we rename python-pycryptodome to
> python-cryptodomex and PROVIDES python-pycryptodome?
>...

The minimal change for stable branches would be to add RCONFLICTS
on python{,3}-pycryptodome to python{,3}-pycrypto.

In a stable branch changing what users get installed is not really
worth it for a tiny bit of improved testing coverage.

Based on what you wrote, for master the best solution will likely 
include removing python{,3}-pycrypto.

cu
Adrian

Re: [thud, warrior, zeus][meta-python] Conundrum: python-pycrypto and python-pycryptodome

[Tim Orling]

On Thu, Dec 5, 2019 at 4:39 AM Adrian Bunk <bunk@stusta.de> wrote:

> On Wed, Dec 04, 2019 at 09:00:20PM -0800, Tim Orling wrote:
> > python-pycrypto [1] is rather old and un-maintained [2].
> > python-pycryptodome [3] is more modern and is basically a drop in
> > replacement. However, the two cannot be installed at the same time.
> > Instead, one would install python-pycryptodomex which does not conflict
> > with the paths of python-pycrypto [4].
> >
> > In an effort to enable packagegroup-meta-python [5] and meta-python-image
> > [6], one runs into the existing python-pycrypto and python-pycryptodome
> > recipes attempting to install the same files to the same locations (no
> > surprise, they are providing the same libraries).
> >
> > For the stable branches, should we rename python-pycryptodome to
> > python-cryptodomex and PROVIDES python-pycryptodome?
> >...
>
> The minimal change for stable branches would be to add RCONFLICTS
> on python{,3}-pycryptodome to python{,3}-pycrypto.
>

this is only a python 2 issue.


> In a stable branch changing what users get installed is not really
> worth it for a tiny bit of improved testing coverage.
>

on the stable branches, packagegroup-meta-python and meta-python-image
would still be broken, now with a warning that x conflicts with y.

To be clear, the packagegroup and image have been broken for the stable
branches for some time now.


> Based on what you wrote, for master the best solution will likely
> include removing python{,3}-pycrypto.
>

python-pycrypto is python 2 only and will thus be dropped from master. The
conflict has already been fixed on meta-python2 by adding
python-cryptodomex and fixing packages that depended upon python-cryptodome

https://git.openembedded.org/meta-python2/commit/?id=18615f47dbbd109bc2350b86e078da93d066e5e5


> cu
> Adrian
>

Re: [thud, warrior, zeus][meta-python] Conundrum: python-pycrypto and python-pycryptodome

[Adrian Bunk]

On Thu, Dec 05, 2019 at 06:33:15AM -0800, Tim Orling wrote:
> On Thu, Dec 5, 2019 at 4:39 AM Adrian Bunk <bunk@stusta.de> wrote:
> > On Wed, Dec 04, 2019 at 09:00:20PM -0800, Tim Orling wrote:
> > > python-pycrypto [1] is rather old and un-maintained [2].
> > > python-pycryptodome [3] is more modern and is basically a drop in
> > > replacement. However, the two cannot be installed at the same time.
> > > Instead, one would install python-pycryptodomex which does not conflict
> > > with the paths of python-pycrypto [4].
> > >
> > > In an effort to enable packagegroup-meta-python [5] and meta-python-image
> > > [6], one runs into the existing python-pycrypto and python-pycryptodome
> > > recipes attempting to install the same files to the same locations (no
> > > surprise, they are providing the same libraries).
> > >
> > > For the stable branches, should we rename python-pycryptodome to
> > > python-cryptodomex and PROVIDES python-pycryptodome?
> > >...
> >
> > The minimal change for stable branches would be to add RCONFLICTS
> > on python{,3}-pycryptodome to python{,3}-pycrypto.
> 
> this is only a python 2 issue.
>...

Adding both python3-pycryptodome and python3-pycrypto to an image failed 
for me in master with the same error.

cu
Adrian

Re: [thud, warrior, zeus][meta-python] Conundrum: python-pycrypto and python-pycryptodome

[Tim Orling]

On Thu, Dec 5, 2019 at 6:58 AM Adrian Bunk <bunk@stusta.de> wrote:

> On Thu, Dec 05, 2019 at 06:33:15AM -0800, Tim Orling wrote:
> > On Thu, Dec 5, 2019 at 4:39 AM Adrian Bunk <bunk@stusta.de> wrote:
> > > On Wed, Dec 04, 2019 at 09:00:20PM -0800, Tim Orling wrote:
> > > > python-pycrypto [1] is rather old and un-maintained [2].
> > > > python-pycryptodome [3] is more modern and is basically a drop in
> > > > replacement. However, the two cannot be installed at the same time.
> > > > Instead, one would install python-pycryptodomex which does not
> conflict
> > > > with the paths of python-pycrypto [4].
> > > >
> > > > In an effort to enable packagegroup-meta-python [5] and
> meta-python-image
> > > > [6], one runs into the existing python-pycrypto and
> python-pycryptodome
> > > > recipes attempting to install the same files to the same locations
> (no
> > > > surprise, they are providing the same libraries).
> > > >
> > > > For the stable branches, should we rename python-pycryptodome to
> > > > python-cryptodomex and PROVIDES python-pycryptodome?
> > > >...
> > >
> > > The minimal change for stable branches would be to add RCONFLICTS
> > > on python{,3}-pycryptodome to python{,3}-pycrypto.
> >
> > this is only a python 2 issue.
> >...
>
> Adding both python3-pycryptodome and python3-pycrypto to an image failed
> for me in master with the same error.
>

Thank you for testing. I’ll follow up on that for master.


> cu
> Adrian
>