tahoe-deps (v18) tarball is broken #1335

Closed
opened 2011-01-23 22:19:09 +00:00 by warner · 2 comments
warner commented 2011-01-23 22:19:09 +00:00
Owner

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 of tahoe-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.

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 of `tahoe-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.
tahoe-lafs added the
packaging
major
defect
1.8.1
labels 2011-01-23 22:19:09 +00:00
tahoe-lafs added this to the 1.8.2 milestone 2011-01-23 22:19:09 +00:00
warner commented 2011-01-26 07:02:54 +00:00
Author
Owner

This is preventing automatic uploads of generated tarballs. I may try to look into this myself on wednesday.

This is preventing automatic uploads of generated tarballs. I may try to look into this myself on wednesday.
zooko commented 2011-01-28 15:34:35 +00:00
Author
Owner

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 of tahoe-deps-v19.tar.bz2 with bzip2, compressed the ones in tahoe-deps-v19.tar.gz with gzip, and left the ones in tahoe-deps-v19.tar.lz uncompressed (in order to make the .tar.lz downloadable slightly smaller). The tarballs builder is green.

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 of `tahoe-deps-v19.tar.bz2` with bzip2, compressed the ones in `tahoe-deps-v19.tar.gz` with gzip, and left the ones in `tahoe-deps-v19.tar.lz` uncompressed (in order to make the `.tar.lz` downloadable slightly smaller). The tarballs builder is green.
tahoe-lafs added the
fixed
label 2011-01-28 15:34:35 +00:00
zooko closed this issue 2011-01-28 15:34:35 +00:00
Sign in to join this conversation.
No milestone
No project
No assignees
1 participant
Notifications
Due date
The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Dependencies

No dependencies set.

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