Opened at 2008-08-06T19:45:25Z
Closed at 2010-02-27T08:56:33Z
#498 closed enhancement (duplicate)
automate the production of .deb's of dependent libraries
| Reported by: | zooko | Owned by: | zooko |
|---|---|---|---|
| Priority: | minor | Milestone: | eventually |
| Component: | dev-infrastructure | Version: | 1.2.0 |
| Keywords: | debian ops deployment packaging | Cc: | |
| Launchpad Bug: |
Description
Automate the production of .deb's of any dependent library of Tahoe's which someone else doesn't already provide .deb's for. This certainly includes zfec and pycryptopp for starters.
See also http://allmydata.org/trac/zfec/ticket/1 (automate the production of .deb's) and http://allmydata.org/trac/pycryptopp/ticket/10 (automate the production of .deb's).
This is the new improved better solution to #469 (build pycryptopp+zfec debs for hardy).
Change History (6)
comment:1 Changed at 2008-08-06T19:45:36Z by zooko
- Keywords ops deployment packaging added
comment:2 Changed at 2008-11-25T21:15:23Z by zooko
- Status changed from new to assigned
comment:3 Changed at 2008-12-05T20:46:37Z by zooko
Currently we don't provide .deb's for amd64 architecture. If this ticket were fixed, then it would be very easy for us to do so.
comment:4 Changed at 2009-05-07T23:09:24Z by zooko
- Milestone changed from undecided to 1.5.0
I want to have this working with the v1.5 release.
comment:5 Changed at 2009-06-30T17:53:13Z by zooko
- Milestone changed from 1.5.0 to eventually
We've made some progress on this -- see the "stdeb' steps on the zfec and pycryptopp buildbots:
http://allmydata.org/buildbot-zfec/waterfall
http://allmydata.org/buildbot-pycryptopp/waterfall
However, the resulting .deb's aren't 100% correct yet. For one thing, zfec depends on argparse and pyutil which are themselves not properly available through apt. So, we're almost there.
comment:6 Changed at 2010-02-27T08:56:33Z by davidsarah
- Resolution set to duplicate
- Status changed from assigned to closed
Duplicate of #769.
This is currently blocked on http://buildbot.net/trac/ticket/212 (buildbot doesn't respond to darcs tags).
According to Denis Bonnenfant, some of the binary .deb's that we provide depend on the wrong libc (a libc from Ubuntu instead of from Debian):
http://allmydata.org/pipermail/tahoe-dev/2008-November/000892.html
This is not too surprising, since I created the .deb's for Debian by cp'ing the .deb's for Ubuntu.
The best way to fix this would be to script our actual Debian buildslaves to produce .deb's in response to darcs tags.
Well, really this ticket isn't blocked on buildbot #212. I can go ahead and script buildslaves to produce .deb's and then force them to do so by clicking the "Force Build" button.