First Last Prev Next    No search results available      Search page      Enter new bug
Bug#: 126817
Alias:
Product:
Component:
Status: RESOLVED
Resolution: FIXED
Assigned To: Python Gentoo Team <python@gentoo.org>
Hardware:
OS:
Version:
Priority:
Severity:
Reporter: Jani Averbach <jaa@jaa.iki.fi>
Add CC:
CC:
Remove selected CCs
URL:
Summary:
Status Whiteboard:
Keywords:

Filename Description Type Creator Created Size Actions
Create a New Attachment (proposed patch, testcase, etc.) View All

Bug 126817 depends on: Show dependency tree
Bug 126817 blocks:
Votes: 0    Show votes for this bug    Vote for this bug

Additional Comments: (this is where you put emerge --info)


Not eligible to see or edit group visibility for this bug.






View Bug Activity   |   Format For Printing   |   XML   |   Clone This Bug

Description:   Opened: 2006-03-19 08:05 0000 
Hello,

Please hard-mask pycrypto 2.0 because it generates wrong hashes on amd64.

There is already 2.0.1, which fixes that. I was bitten by this bug.

zcat /usr/share/doc/pycrypto-2.0.1-r4/ChangeLog.gz  | head -n10

2.0.1
=====

 * Fix SHA256 and RIPEMD on AMD64 platform.
 * Deleted Demo/ directory.
 * Add PublicKey to Crypto.__all__


2.0

------- Comment #1 From Carsten Lohrke 2006-03-19 08:31:22 0000 ------- 
Looks like the latest ebuild should go stable on amd64 asap.

------- Comment #2 From Mike Doty 2006-03-19 10:02:49 0000 ------- 
2.0.1-r4 is now stable for amd64.

------- Comment #3 From Frank 2006-04-18 02:38:43 0000 ------- 
(In reply to comment #2)
> 2.0.1-r4 is now stable for amd64.
> 

but when i emerge it, portage says it's masked on keyword ~x86  (on a ~amd64
system)
Something i am doing wrong ?
First Last Prev Next    No search results available      Search page      Enter new bug