tahoe-deps (v18) tarball is broken #1335
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#1335
Loading…
Reference in New Issue
No description provided.
Delete Branch "%!s(<nil>)"
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?
The current "
tahoe-deps.tar.gz
" tarball (containing a copy of source for all of Tahoe's dependencies) is broken. It was recently rebuilt (to update a couple of the tarballs), and accidentally made to unpack into the wrong directory (tahoe-deps-v18/
instead oftahoe-deps/
). As a result, the "tarballs" builder is red: http://tahoe-lafs.org/buildbot/builders/tarballs/builds/796/steps/tarballs/logs/stdio .The fix is to regenerate this tarball with the correct directory name. I've also asked zooko to leave the component tarballs in their original (compressed) pristine-upstream state, to match what earlier tahoe-deps bundles did.
I think this should block the 1.8.2 release, especially since the builder that produces our shipping Tahoe tarballs is red as a result.
This is preventing automatic uploads of generated tarballs. I may try to look into this myself on wednesday.
Okay I've built a new tahoe-deps tarball with all of the latest stable versions of each of the components and with the directory name fixed to be
tahoe-deps
. I compressed the components oftahoe-deps-v19.tar.bz2
with bzip2, compressed the ones intahoe-deps-v19.tar.gz
with gzip, and left the ones intahoe-deps-v19.tar.lz
uncompressed (in order to make the.tar.lz
downloadable slightly smaller). The tarballs builder is green.