build pycryptopp+zfec debs for hardy #469
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
3 Participants
Notifications
Due Date
No due date set.
Reference: tahoe-lafs/trac-2024-07-25#469
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?
We've got a hardy buildslave set up, and it's producing tahoe debs, but these are uninstallable because they depend upon python-pycryptopp and python-zfec, which have not been packaged for hardy yet. It looks like python-pyutil and python-argparse might be required too.
This ticket will be resolved when suitable debs are installed in our APT repository (
dev:~buildslave/tahoe-debs
). deharo1 is available for building the packages, deharo2 is reserved for testing their installation (deharo2 pulls from the tahoe-debs APT repo).We hit this again today trying to test our tahoe-server debs on deharo2.
As it stands now, Tahoe is not deployable by ops on Hardy.
This would be blocking deployment of new monitoring, if I hadn't already worked around this once.
We hit this again today, trying to set up prodweb3 as an incident-gatherer server.
Zooko, what's your ETA on this one?
it looks like python-pyutil is required too, and python-argparse, at least the gutsy debs I found require them, so we need these packaged too.
This has been fixed by cp'ing all the gutsy debs into the hardy repository.
See also the better, long-term fix: #498 (automate the production of .deb's of dependent libraries).