Opened at 2011-10-30T14:26:14Z
Closed at 2012-05-31T23:34:22Z
#1574 closed defect (fixed)
PyCrypto 2.4 doesn't build with setuptools
Reported by: | zooko | Owned by: | somebody |
---|---|---|---|
Priority: | major | Milestone: | 1.9.2 |
Component: | packaging | Version: | 1.9.0b1 |
Keywords: | setuptools pycrypto packaging | Cc: | |
Launchpad Bug: | 881130 |
Description (last modified by zooko)
Apparently PyCrypto 2.4 doesn't build with setuptools (or zc.buildout or virtualenv):
https://bugs.launchpad.net/pycrypto/+bug/881130
This is visible as a failure on FreeStorm's buildslave:
The characteristic error message is that the build ends with:
error: Setup script exited with error: src/config.h: No such file or directory
Here are my notes about it:
https://tahoe-lafs.org/pipermail/tahoe-dev/2011-October/006807.html
Change History (3)
comment:1 Changed at 2011-10-30T14:26:51Z by zooko
- Description modified (diff)
comment:2 Changed at 2011-10-31T02:35:26Z by warner
- Milestone changed from 1.9.0 to soon
comment:3 Changed at 2012-05-31T23:34:22Z by davidsarah
- Keywords packaging added
- Milestone changed from soon to 1.9.2
- Resolution set to fixed
- Status changed from new to closed
This was fixed in 5af3bfda6190b511 (and is also on the 1.9.2 branch), by excluding PyCrypto 2.4 from the versions we allow in src/allmydata/_auto_deps.py. PyCrypto 2.4.1 does not have the packaging bug.
Note: See
TracTickets for help on using
tickets.
oops, I opened #1575 as a dup. There are some more notes over there.
For 1.9, I've decided to go with the "host binary eggs" fix, since the alternatives are even more gross. That means no code changes need to be made for this. The installability of tahoe-1.9 on systems that don't already have pycrypto available will depend upon volunteers providing us with eggs that we can host, or upon installers being willing to use the workaround of running tahoe's python setup.py build twice.
So this is no longer a 1.9 blocker.