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

Adrian Bunk bunk at stusta.de
Thu Dec 5 14:58:50 UTC 2019


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 at 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


More information about the Openembedded-devel mailing list