Note: This is a beta release of Red Hat Bugzilla 5.0. The data contained within is a snapshot of the live data so any changes you make will not be reflected in the production Bugzilla. Also email is disabled so feel free to test any aspect of the site that you want. File any problems you find or give feedback here.
Bug 242480 - python-crypto fails to build on ppc64
Summary: python-crypto fails to build on ppc64
Alias: None
Product: Fedora
Classification: Fedora
Component: python-crypto
Version: 7
Hardware: ppc64
OS: Linux
Target Milestone: ---
Assignee: Thorsten Leemhuis
QA Contact: Fedora Extras Quality Assurance
Depends On:
Blocks: FE-ExcludeArch-ppc64, F-ExcludeArch-ppc64
TreeView+ depends on / blocked
Reported: 2007-06-04 14:15 UTC by Paul Howarth
Modified: 2007-11-30 22:12 UTC (History)
0 users

Fixed In Version: 2.0.1-7.1.fc7
Doc Type: Bug Fix
Doc Text:
Clone Of:
Last Closed: 2007-06-13 21:05:33 UTC

Attachments (Terms of Use)

Description Paul Howarth 2007-06-04 14:15:46 UTC
Full build log available here:

Problem appears to be that site-packages/Crypto/PublicKey/ is not
created, and this is probably due to not finding the GMP library. I
speculate (not having a ppc64 box) that the existing patch for x86_64 would also
fix ppc64 if applied.

The absence of python-crypto from the F7 ppc64 repository is causing dependency
problems for bittorrent, which requires it.

Comment 1 David Woodhouse 2007-06-04 14:26:30 UTC
Yes, that patch seems to have been the wrong way to handle it from the start.
Perhaps something like the following, instead of applying that patch:

sed -i s:/lib:/%_lib:g

Comment 2 David Woodhouse 2007-06-04 15:25:40 UTC
Committed and built in rawhide. Could probably do with a F-7 build but I'll
leave that to package maintainer, along with questions about whether to add a
disttag, etc.

Comment 3 Fedora Update System 2007-06-13 21:05:27 UTC
python-crypto-2.0.1-7.1.fc7 has been pushed to the Fedora 7 stable repository.  If problems still persist, please make note of it in this bug report.

Note You need to log in before you can comment on or make changes to this bug.