automate the production of .deb's of dependent libraries #498

Closed
opened 2008-08-06 19:45:25 +00:00 by zooko · 5 comments

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).

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).
zooko added the
dev-infrastructure
minor
enhancement
1.2.0
labels 2008-08-06 19:45:25 +00:00
zooko added this to the undecided milestone 2008-08-06 19:45:25 +00:00
zooko self-assigned this 2008-08-06 19:45:25 +00:00
Author

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.

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.
Author

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.

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.
Author

I want to have this working with the v1.5 release.

I want to have this working with the v1.5 release.
zooko modified the milestone from undecided to 1.5.0 2009-05-07 23:09:24 +00:00
Author

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.

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.
zooko modified the milestone from 1.5.0 to eventually 2009-06-30 17:53:13 +00:00
davidsarah commented 2010-02-27 08:56:33 +00:00
Owner

Duplicate of #769.

Duplicate of #769.
tahoe-lafs added the
duplicate
label 2010-02-27 08:56:33 +00:00
davidsarah closed this issue 2010-02-27 08:56:33 +00:00
Sign in to join this conversation.
No Milestone
No Assignees
2 Participants
Notifications
Due Date
The due date is invalid or out of range. Please use the format 'yyyy-mm-dd'.

No due date set.

Reference: tahoe-lafs/trac-2024-07-25#498
No description provided.