Bug 25659

Summary: python2-pycryptodome-3.7.2-1.mga7.x86_64 conflicts with python-pycrypto-2.6.1-14.mga7.x86_64
Product: Mageia Reporter: papoteur <yvesbrungard>
Component: RPM PackagesAssignee: All Packagers <pkg-bugs>
Status: RESOLVED OLD QA Contact:
Severity: normal    
Priority: Normal CC: davidwhodgins, geiger.david68210, jani.valimaa, olivier, smelror
Version: 7Keywords: IN_ERRATA7
Target Milestone: ---   
Hardware: All   
OS: Linux   
Whiteboard:
Source RPM: CVE:
Status comment:

Description papoteur 2019-11-05 20:25:08 CET
Description of problem:
During an upgrade 6->7
Can't be installed:
python2-pycryptodome-3.7.2-1.mga7.x86_64 (en raison de conflit avec python-pycrypto-2.6.1-14.mga7.x86_64)"
Comment 1 Olivier FAURAX 2020-01-12 21:06:11 CET
Confirmed :
Certains paquetages demandés ne peuvent pas être installés :
python2-pdfminer.six-20181108-1.mga7.noarch (car python2.7dist(pycryptodome) est non satisfait)
python2-pycryptodome-3.7.2-1.mga7.i586 (en raison de conflit avec python-pycrypto-2.6.1-14.mga7.x86_64)
python2-pycryptodome-3.7.2-1.mga7.x86_64 (en raison de conflit avec python-pycrypto-2.6.1-14.mga7.x86_64)

Keywords: (none) => FOR_ERRATA7
CC: (none) => olivier

Comment 2 David Walser 2020-01-13 15:31:37 CET
Are you sure?  Sophie doesn't see a python-pycrypto package in Mageia 7.
David Walser 2020-01-13 15:32:01 CET

CC: (none) => geiger.david68210, jani.valimaa, smelror

Comment 3 Olivier FAURAX 2020-01-13 15:38:27 CET
rpmfind finds it:
https://www.rpmfind.net/linux/rpm2html/search.php?query=pythonegg(2)(pycrypto)
Comment 5 David Walser 2020-01-13 20:24:44 CET
Interesting.  It was removed from Cauldron, but yeah I found it in SVN for 7.

Looks like Jani attempted to fix this:
http://svnweb.mageia.org/packages?view=revision&revision=1247892

but he only got the Python3 package and not the Python(2) package.
Comment 6 David Walser 2020-01-15 04:06:06 CET
Looking at it again, the Python(2) one actually is in there, and that's where this conflict comes from.  The conflicts are legit, so you'll have to uninstall one or the other.  Something like this should really be in the Release Notes though, not Errata.

Given that pycrypto was removed in Cauldron, maybe whatever still depends on it in Mageia 7 can be updated to use pycryptodome instead, which would solve this issue?  I don't know what still requires it.
Comment 7 Dave Hodgins 2020-01-15 06:43:14 CET
# urpmq --whatrequires python-pycrypto|sort -u
fwbackups
pulse-xmpp-agent
python2-dnspython
python2-twisted
python-keyczar
python-pycrypto

CC: (none) => davidwhodgins

Comment 8 papoteur 2020-01-16 10:55:41 CET
Added in errata,
https://wiki.mageia.org/en/Mageia_7_Errata#Python_modules
What would be a place in release notes? Python stack? Upgrading?

Keywords: FOR_ERRATA7 => IN_ERRATA7

Comment 9 Aurelien Oudelet 2021-07-06 13:16:25 CEST
Mageia 7 is EOL since July 1st 2021.
There will not have any further bugfix for this release.

You are encouraged to upgrade to Mageia 8 as soon as possible.

@reporter, if this bug still apply with Mageia 8, please let us know it.

@packager, if you work on the Mageia 7 version of your package, please check the Mageia 8 package if issue is also present. In this case, please fix the Mageia 8 version instead.

This bug report will be closed OLD if there is no further notice within 1st September 2021.
Comment 10 Marja Van Waes 2021-09-07 14:10:08 CEST
Hi bug reporter and hi assignee and others involved,

Please reopen this bug report if it is still valid for Mageia 8 or 9(cauldron), and change "Version:" in the upper left of this report accordingly.

This report is being closed as OLD because it was filed against Mageia 7, for which  support ended on June 30th 2021.

Thanks,
Marja

Resolution: (none) => OLD
Status: NEW => RESOLVED