Bug 533190 – sys-apps/portage-2.2.14: no longer accepts python-mhash as python[ssl] alternative

• Status: VERIFIED NEEDINFO
• Product: Gentoo Linux

[Description Matthew Millar 2014-12-21 15:23:37 UTC]

Since portage-2.2.8-r2, an upgrade to portage-2.2.14 requires python[ssl] without consideration of python-mhash as an alternative dependancy.



Reproducible: Always

Steps to Reproduce:
1. USE="-ssl" emerge -1epv portage
2.
3.
Actual Results:  
ebuild   R    ] dev-lang/python-2.7.7:2.7  USE="ncurses readline ssl* threads (wide-unicode) xml -berkdb -build -doc -examples -gdbm -hardened -ipv6 -sqlite -tk -wininst" 0 KiB
[ebuild   R    ] sys-apps/portage-2.2.14::gentoo [2.2.14::sarahs_overlay] USE="(ipc) -build -doc -epydoc (-selinux) -xattr" LINGUAS="-ru" PYTHON_TARGETS="python2_7 (-pypy) -python3_3 -python3_4" 0 KiB

Total: 2 packages (2 reinstalls), Size of downloads: 0 KiB

The following USE changes are necessary to proceed:
 (see "package.use" in the portage(5) man page for more details)
# required by sys-apps/portage-2.2.14[-build,python_targets_python2_7]
# required by portage (argument)
=dev-lang/python-2.7.7 ssl

Expected Results:  
[ebuild   R    ] app-crypt/mhash-0.9.9.9-r1  USE="-static-libs" 0 KiB
...
[binary   R    ] dev-python/python-mhash-1.4-r1  PYTHON_TARGETS="python2_7" 0 KiB
...
[binary   R    ] dev-lang/python-2.7.7:2.7  USE="ncurses readline threads (wide-unicode) xml -berkdb -build -doc -examples -gdbm -hardened -ipv6 -sqlite -ssl -tk -wininst" 0 KiB
[ebuild     UD ] sys-apps/portage-2.2.8-r2::gentoo [2.2.14::sarahs_overlay] USE="(ipc) -build -doc -epydoc (-pypy2_0) -python2% -python3% (-selinux) -xattr" LINGUAS="-ru" PYTHON_TARGETS="python2_7 (-pypy2_0) (-python2_6) (-python3_2) -python3_3 -python3_4 (-pypy%)" 0 KiB

[Comment 1 Michał Górny 2014-12-21 15:32:26 UTC]

That is the intended behavior.

[Comment 2 Matthew Millar 2014-12-22 11:04:43 UTC]

Why is it the intended behavior? Python-mhash still works for generating WHIRLPOOL hashes.

If python-mhash is no longer supported then the comment re #425046 in the ebuild needs updating.

[Comment 3 Michał Górny 2014-12-22 11:22:37 UTC]

(In reply to Matthew Millar from comment #2)
> Why is it the intended behavior? Python-mhash still works for generating
> WHIRLPOOL hashes.

For Python 2.7 maybe. Expressing the dependency of 'we need python[ssl] except for python2.7 where we need either python[ssl] or python-mhash' is simply too cumbersome. We install python[ssl] by default, so there's no point in adding a lot of complexity for the corner case of people who disable ssl support and still use python2.7.

> If python-mhash is no longer supported then the comment re #425046 in the
> ebuild needs updating.

Updated.