when dev-python/pycrypto is built with USE=bindist, some algorithms are disabled which then prevent things like `ebuild ... manifest` from working ... # ebuild /usr/portage/app-editors/hexcurse/hexcurse-1.55.ebuild manifest >>> Creating Manifest for /usr/portage/app-editors/hexcurse Traceback (most recent call last): File "/usr/sbin/ebuild", line 139, in ? debug=debug, tree=mytree) File "/usr/lib/portage/pym/portage.py", line 3617, in doebuild manifestonly=1, myportdb=mydbapi) File "/usr/lib/portage/pym/portage.py", line 2777, in digestgen assumeDistHashesAlways=( File "/usr/lib/portage/pym/portage_manifest.py", line 439, in create self.fhashdict[mytype][f] = perform_multiple_checksums(self.pkgdir+f, self.hashes) File "/usr/lib/portage/pym/portage_checksum.py", line 235, in perform_multiple_checksums raise portage_exception.DigestException, x+" hash function not available (needs dev-python/pycrypto)" portage_exception.DigestException: RMD160 hash function not available (needs dev-python/pycrypto)
Can't confirm that here, even with USE=bindist pycrypto contains the RMD160 hash algorithm (only RC5 and IDEA are removed), and portage works just fine.
yeah i dunno where that was failing ... and looking at pycrypto, it only turns off IDEA and RC5 ...
