[opensuse-factory] What's up with python-pycrypto ? Gone from factory?
All, I have 2 packages I maintain that depend on python-pycrypto and now won't install in factory. Is this: - a temporary glitch - a lack of a maintainer - a problem with the upstream package Thanks Greg -- Greg Freemyer Advances are made by answering questions. Discoveries are made by questioning answers. — Bernard Haisch -- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-factory+owner@opensuse.org
On 16/05/18 10:58, Greg Freemyer wrote:
All,
I have 2 packages I maintain that depend on python-pycrypto and now won't install in factory.
Is this:
- a temporary glitch
- a lack of a maintainer
- a problem with the upstream package
Thanks Greg
According to the following sr it has been replaced by python-pycryptodome, this was done as part of the dlp cleanup I guess. https://build.opensuse.org/request/show/605243 -- Simon Lees (Simotek) http://simotek.net Emergency Update Team keybase.io/simotek SUSE Linux Adelaide Australia, UTC+10:30 GPG Fingerprint: 5B87 DB9D 88DC F606 E489 CEC5 0922 C246 02F0 014B
On Wed, May 16, 2018 at 12:36 AM, Simon Lees
On 16/05/18 10:58, Greg Freemyer wrote:
All,
I have 2 packages I maintain that depend on python-pycrypto and now won't install in factory.
Is this:
- a temporary glitch
- a lack of a maintainer
- a problem with the upstream package
Thanks Greg
According to the following sr it has been replaced by python-pycryptodome, this was done as part of the dlp cleanup I guess. https://build.opensuse.org/request/show/605243
python-pycryptodome seems to have the appropriate provides/obsoletes statements: Provides: python-pycrypto = %{version} Obsoletes: python-pycrypto < %{version} But I can't install it as python-pycrypto. On a fresh tumbleweed VM zypper in python-pycrypto gets "Package python-pycrypto not found" That SR should not have been accepted. Can we get it reverted for now? Greg -- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-factory+owner@opensuse.org
On Wed, 2018-05-16 at 07:14 -0400, Greg Freemyer wrote:
On Wed, May 16, 2018 at 12:36 AM, Simon Lees
wrote: On 16/05/18 10:58, Greg Freemyer wrote:
All,
I have 2 packages I maintain that depend on python-pycrypto and now won't install in factory.
Is this:
- a temporary glitch
- a lack of a maintainer
- a problem with the upstream package
Thanks Greg
According to the following sr it has been replaced by python-pycryptodome, this was done as part of the dlp cleanup I guess. https://build.opensuse.org/request/show/605243
python-pycryptodome seems to have the appropriate provides/obsoletes statements:
Provides: python-pycrypto = %{version} Obsoletes: python-pycrypto < %{version}
But I can't install it as python-pycrypto.
Those are translated by python-singlespec to python2-pycrypto and python3-pycrypto zypper info --provides python2-pycryptodome … Provides : [4] python-pycryptodome = 3.6.1-1.1 python2-pycrypto = 3.6.1 python2-pycryptodome = 3.6.1-1.1 python2-pycryptodome(x86-64) = 3.6.1-1.1 Cheers Dominique
On Wed, May 16, 2018 at 7:19 AM, Dominique Leuenberger / DimStar
On Wed, 2018-05-16 at 07:14 -0400, Greg Freemyer wrote:
On Wed, May 16, 2018 at 12:36 AM, Simon Lees
wrote: On 16/05/18 10:58, Greg Freemyer wrote:
All,
I have 2 packages I maintain that depend on python-pycrypto and now won't install in factory.
Is this:
- a temporary glitch
- a lack of a maintainer
- a problem with the upstream package
Thanks Greg
According to the following sr it has been replaced by python-pycryptodome, this was done as part of the dlp cleanup I guess. https://build.opensuse.org/request/show/605243
python-pycryptodome seems to have the appropriate provides/obsoletes statements:
Provides: python-pycrypto = %{version} Obsoletes: python-pycrypto < %{version}
But I can't install it as python-pycrypto.
Those are translated by python-singlespec to python2-pycrypto and python3-pycrypto
zypper info --provides python2-pycryptodome … Provides : [4] python-pycryptodome = 3.6.1-1.1 python2-pycrypto = 3.6.1 python2-pycryptodome = 3.6.1-1.1 python2-pycryptodome(x86-64) = 3.6.1-1.1
Cheers Dominique
In my mind that's a bug. If every package that requires python-pycrypto is going to have to be edited why bother with the provides/obsoletes pair in the first place. Let me know if I should adjust my 2 spec files or not. Thanks Greg -- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-factory+owner@opensuse.org
On Wed, 2018-05-16 at 07:40 -0400, Greg Freemyer wrote:
Those are translated by python-singlespec to python2-pycrypto and python3-pycrypto
zypper info --provides python2-pycryptodome … Provides : [4] python-pycryptodome = 3.6.1-1.1 python2-pycrypto = 3.6.1 python2-pycryptodome = 3.6.1-1.1 python2-pycryptodome(x86-64) = 3.6.1-1.1
Cheers Dominique
In my mind that's a bug.
The translation is intentional (the spec is used to build py2 and py3 packages in one go) - as for the old package name no longer being there, that CAN be considered a bug indeed. Care to file a bug report? Will be up to the maintainer to decide if it's worthy to add the legacy names.
If every package that requires python-pycrypto is going to have to be edited why bother with the provides/obsoletes pair in the first place.
Obviously, we took care of everything inside the distro to not fall over (and I think we missed nothing this time) . Ever considered submitting your packages too? :)
Let me know if I should adjust my 2 spec files or not.
There is no way we can predict what all is 'out there' and how everybody makes use of things. The shortest/quickest way is to change to python2-pycryptodome, and no longer rely on old/unmaintained pycrypto code. Cheers Dominique
On Mai 16 2018, Dominique Leuenberger / DimStar
Obviously, we took care of everything inside the distro to not fall over (and I think we missed nothing this time)
https://build.opensuse.org/package/show/openSUSE:Factory/python-troveclient https://build.opensuse.org/package/show/openSUSE:Factory/salt Andreas. -- Andreas Schwab, SUSE Labs, schwab@suse.de GPG Key fingerprint = 0196 BAD8 1CE9 1970 F4BE 1748 E4D4 88E3 0EEA B9D7 "And now for something completely different." -- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-factory+owner@opensuse.org
On Wed, 2018-05-16 at 14:08 +0200, Andreas Schwab wrote:
On Mai 16 2018, Dominique Leuenberger / DimStar
wrote: Obviously, we took care of everything inside the distro to not fall over (and I think we missed nothing this time)
https://build.opensuse.org/package/show/openSUSE:Factory/python-troveclient https://build.opensuse.org/package/show/openSUSE:Factory/salt
Andreas.
Thanks for the pointers! So we still have a gap in the delete request process?!? I wonder how that could still slip - and the answer is easy: human error! The bot DID warn about it but the obsoletes/provides of the pycryptodome was believed to take care of the ones we checked. Cheers, Dominique
On Wed, May 16, 2018 at 8:08 AM, Andreas Schwab
On Mai 16 2018, Dominique Leuenberger / DimStar
wrote: Obviously, we took care of everything inside the distro to not fall over (and I think we missed nothing this time)
https://build.opensuse.org/package/show/openSUSE:Factory/python-troveclient https://build.opensuse.org/package/show/openSUSE:Factory/salt
zypper in python-volatilty zypper in python-dfVFS So yes, some things were missed. Greg -- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-factory+owner@opensuse.org
On Wed, 2018-05-16 at 08:17 -0400, Greg Freemyer wrote:
On Wed, May 16, 2018 at 8:08 AM, Andreas Schwab
wrote: On Mai 16 2018, Dominique Leuenberger / DimStar
wrote: Obviously, we took care of everything inside the distro to not fall over (and I think we missed nothing this time)
https://build.opensuse.org/package/show/openSUSE:Factory/python-troveclient https://build.opensuse.org/package/show/openSUSE:Factory/salt
zypper in python-volatilty zypper in python-dfVFS
So yes, some things were missed.
Thanks to Tomas' quick reaction: Fixed in openSUSE:Factory (will be part of snapshot 0516): the python-pycrypto name is now also obsoleted/provided (or rather, will be, onc ethe build completes) Cheers, Dominique
On Wed, May 16, 2018 at 8:32 AM, Dominique Leuenberger / DimStar
On Wed, 2018-05-16 at 08:17 -0400, Greg Freemyer wrote:
On Wed, May 16, 2018 at 8:08 AM, Andreas Schwab
wrote: On Mai 16 2018, Dominique Leuenberger / DimStar
wrote: Obviously, we took care of everything inside the distro to not fall over (and I think we missed nothing this time)
https://build.opensuse.org/package/show/openSUSE:Factory/python-troveclient https://build.opensuse.org/package/show/openSUSE:Factory/salt
zypper in python-volatilty zypper in python-dfVFS
So yes, some things were missed.
Thanks to Tomas' quick reaction: Fixed in openSUSE:Factory (will be part of snapshot 0516): the python-pycrypto name is now also obsoleted/provided (or rather, will be, onc ethe build completes)
Cheers, Dominique
Thanks Dominique / Tomas / All, That was exactly what I was hoping would happen. The conversion from python-* to python2-* is obviously a pain, but I'm happy to see the old name maintained as a provides/obsoletes. Greg -- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-factory+owner@opensuse.org
On 16/05/18 13:32, Dominique Leuenberger / DimStar wrote:
On Wed, 2018-05-16 at 08:17 -0400, Greg Freemyer wrote:
On Wed, May 16, 2018 at 8:08 AM, Andreas Schwab
wrote: On Mai 16 2018, Dominique Leuenberger / DimStar
wrote: Obviously, we took care of everything inside the distro to not fall over (and I think we missed nothing this time)
https://build.opensuse.org/package/show/openSUSE:Factory/python-troveclient https://build.opensuse.org/package/show/openSUSE:Factory/salt
zypper in python-volatilty zypper in python-dfVFS
So yes, some things were missed.
Thanks to Tomas' quick reaction: Fixed in openSUSE:Factory (will be part of snapshot 0516): the python-pycrypto name is now also obsoleted/provided (or rather, will be, onc ethe build completes)
Cheers, Dominique
Hello, It seems that Ansible is also broken in the latest snapshots Problem: nothing provides python-pycrypto >= 2.6 needed by ansible-2.5.1-1.1.noarch Solution 1: do not install ansible-2.5.1-1.1.noarch Solution 2: break ansible-2.5.1-1.1.noarch by ignoring some of its dependencies -- markos SUSE LINUX GmbH | GF: Felix Imendörffer, Jane Smithard, Graham Norton HRB 21284 (AG Nürnberg) Maxfeldstr. 5, D-90409, Nürnberg
On Wed, May 16, 2018 at 10:18 AM, Markos Chandras
On 16/05/18 13:32, Dominique Leuenberger / DimStar wrote:
On Wed, 2018-05-16 at 08:17 -0400, Greg Freemyer wrote:
On Wed, May 16, 2018 at 8:08 AM, Andreas Schwab
wrote: On Mai 16 2018, Dominique Leuenberger / DimStar
wrote: Obviously, we took care of everything inside the distro to not fall over (and I think we missed nothing this time)
https://build.opensuse.org/package/show/openSUSE:Factory/python-troveclient https://build.opensuse.org/package/show/openSUSE:Factory/salt
zypper in python-volatilty zypper in python-dfVFS
So yes, some things were missed.
Thanks to Tomas' quick reaction: Fixed in openSUSE:Factory (will be part of snapshot 0516): the python-pycrypto name is now also obsoleted/provided (or rather, will be, onc ethe build completes)
Cheers, Dominique
Hello,
It seems that Ansible is also broken in the latest snapshots
Problem: nothing provides python-pycrypto >= 2.6 needed by ansible-2.5.1-1.1.noarch Solution 1: do not install ansible-2.5.1-1.1.noarch Solution 2: break ansible-2.5.1-1.1.noarch by ignoring some of its dependencies
As Dominique implied, ansible is fine in factory as of this morning: https://build.opensuse.org/package/binary/openSUSE:Factory/ansible/standard/... So you just have to wait for the next tumbleweed snapshot. Greg -- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-factory+owner@opensuse.org
participants (5)
-
Andreas Schwab
-
Dominique Leuenberger / DimStar
-
Greg Freemyer
-
Markos Chandras
-
Simon Lees