Summary: | Verification of ebuild checksum very slow - sys-apps/portage-2.1.10.65 amd64 | ||
---|---|---|---|
Product: | Portage Development | Reporter: | Honza <hkmaly> |
Component: | Core | Assignee: | Portage team <dev-portage> |
Status: | RESOLVED DUPLICATE | ||
Severity: | normal | CC: | matthew4196 |
Priority: | Normal | ||
Version: | 2.1 | ||
Hardware: | All | ||
OS: | Linux | ||
Whiteboard: | |||
Package list: | Runtime testing required: | --- |
Description
Honza
2012-07-28 17:40:25 UTC
Ok, tried few other packages and seems that only the WHIRLPOOL takes so long. (links doesn't have it and was checked fast). Can I somehow select that sha512 is enough for me? Looking at http://archives.gentoo.org/gentoo-portage-dev/msg_545bb5944498d07c53e1878caea491ca.xml ... can portage TELL user what hash implementation is it using? On some -v flag or something ... trying to recompile mhash, pycrypto, python-fchksum and python-2.6 just in case ... Looking at compiled filenames, dev-python/pycrypto-2.6 does not compile whirlpool. Emerge of (~amd64 keyworded) dev-python/python-mhash-1.4 helped A LOT.qt-everywhere-opensource-src-4.8.2.tar.gz finally verified in matter of minutes, instead of previous not-finished-after-hour ... ... so, I would propose: 1) stabilize dev-python/python-mhash-1.4 2) add a check for available hash functions in portage postinst and warning that emerging will be slow as hell if no accelerated version is available with list of packages providing it (starting with dev-python/python-mhash). Latest portage skips the whirlpool hashes when necessary: http://git.overlays.gentoo.org/gitweb/?p=proj/portage.git;a=commit;h=63e25313d785f40abff3197fe0f3a3eeaa617f7d *** This bug has been marked as a duplicate of bug 425046 *** |