#759 closed defect (fixed)
bundle newer pycryptopp into SUMO packages
| Reported by: | zooko | Owned by: | warner |
|---|---|---|---|
| Priority: | major | Milestone: | 1.5.0 |
| Component: | packaging | Version: | 1.4.1 |
| Keywords: | Cc: | ||
| Launchpad Bug: |
Description
The Desert Island build is broken because TahoeLAFS now requires pycryptopp >= 0.5.15, and the SUMO tarball comes with 0.5.14:
http://allmydata.org/buildbot/builders/clean/builds/2070/steps/test-desert-island/logs/stdio
Change History (3)
comment:1 Changed at 2009-07-15T01:14:15Z by warner
- Status changed from new to assigned
comment:2 Changed at 2009-07-15T07:12:11Z by warner
- Resolution set to fixed
- Status changed from assigned to closed
Done. desert-island-test is now green.
Note that we haven't actually built tarballs for a month, since one of the "Supported Builders" has gone AWOL, and the buildbot is configured to wait for all supported builders to finish a build before creating tarballs or debs. I plan to remove that coarse dependency and replace it with something smaller.. not sure what yet.
comment:3 Changed at 2009-07-15T12:49:42Z by zooko
The reason it didn't build tarballs all that time was because one of the supported builders was red -- the 'mac-exe' builder on ootles.
Please don't unliterally change that code -- that's the implementation of our Buildbot Policy http://allmydata.org/trac/tahoe/wiki/BuildbotPolicy . If you think the policy should be different, let's talk about it first.
In other words, I intended for it not to build tarballs all that time, because that way people who downloaded a tarball during that month would be getting one that was produced from source code that passed all the supported builders, including the 'mac-exe' builder.
If that's too long to go with no new packages, then maybe this means 'mac-exe' should be removed from Supported.
I'll add it to the tahoe-deps bundle, that should fix it.