automate the production of .deb's of dependent libraries #498
Labels
No Label
0.2.0
0.3.0
0.4.0
0.5.0
0.5.1
0.6.0
0.6.1
0.7.0
0.8.0
0.9.0
1.0.0
1.1.0
1.10.0
1.10.1
1.10.2
1.10a2
1.11.0
1.12.0
1.12.1
1.13.0
1.14.0
1.15.0
1.15.1
1.2.0
1.3.0
1.4.1
1.5.0
1.6.0
1.6.1
1.7.0
1.7.1
1.7β
1.8.0
1.8.1
1.8.2
1.8.3
1.8β
1.9.0
1.9.0-s3branch
1.9.0a1
1.9.0a2
1.9.0b1
1.9.1
1.9.2
1.9.2a1
LeastAuthority.com automation
blocker
cannot reproduce
cloud-branch
code
code-dirnodes
code-encoding
code-frontend
code-frontend-cli
code-frontend-ftp-sftp
code-frontend-magic-folder
code-frontend-web
code-mutable
code-network
code-nodeadmin
code-peerselection
code-storage
contrib
critical
defect
dev-infrastructure
documentation
duplicate
enhancement
fixed
invalid
major
minor
n/a
normal
operational
packaging
somebody else's problem
supercritical
task
trivial
unknown
was already fixed
website
wontfix
worksforme
No Milestone
No Assignees
2 Participants
Notifications
Due Date
No due date set.
Reference: tahoe-lafs/trac-2024-07-25#498
Loading…
Reference in New Issue
Block a user
No description provided.
Delete Branch "%!s()"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
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).
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.
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.
I want to have this working with the v1.5 release.
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.
Duplicate of #769.