golang-github-vbatts-tar-split 0.9.10-1 source package in Ubuntu
Changelog
golang-github-vbatts-tar-split (0.9.10-1) unstable; urgency=medium * Update to 0.9.10 upstream release -- Tianon Gravi <email address hidden> Sat, 24 Oct 2015 11:00:17 -0700
Upload details
- Uploaded by:
- Debian Go Packaging Team
- Uploaded to:
- Sid
- Original maintainer:
- Debian Go Packaging Team
- Architectures:
- any all
- Section:
- misc
- Urgency:
- Medium Urgency
See full publishing history Publishing
| Series | Published | Component | Section | |
|---|---|---|---|---|
| Xenial | release | universe | misc |
Downloads
| File | Size | SHA-256 Checksum |
|---|---|---|
| golang-github-vbatts-tar-split_0.9.10-1.dsc | 2.3 KiB | 8db01d014ddeecb68c2364f9ce7b67213260d333c9780f78c4ba8be74d5e0a58 |
| golang-github-vbatts-tar-split_0.9.10.orig.tar.gz | 45.7 KiB | fe009d855990a84453d5a3e562b311badd0a43507d46c94a91ef8ebeb316ba98 |
| golang-github-vbatts-tar-split_0.9.10-1.debian.tar.xz | 3.4 KiB | f019fa7ec63f2166eddfd8fffdd3bad66e0f7c029f8adee891ba1b6a9d9c9ddc |
Available diffs
- diff from 0.9.7-2 to 0.9.10-1 (3.2 KiB)
No changes file available.
Binary packages built by this source
- golang-github-vbatts-tar-split-dev: tar archive assembly/disassembly (source)
Pristinely disassembling a tar archive, and stashing needed raw bytes and
offsets to reassemble a validating original archive.
.
Eventually this should detect TARs that this is not possible with.
.
For example stored sparse files that have "holes" in them, will be read as a
contiguous file, though the archive contents may be recorded in sparse format.
Therefore when adding the file payload to a reassembled tar, to achieve
identical output, the file payload would need be precisely re-sparsified. This
is not something I seek to fix imediately, but would rather have an alert that
precise reassembly is not possible. (see more
http://www.gnu. org/software/ tar/manual/ html_node/ Sparse- Formats. html)
.
Other caveat, while tar archives support having multiple file entries for the
same path, we will not support this feature. If there are more than one entries
with the same path, expect an err (like ErrDuplicatePath) or a resulting tar
stream that does not validate your original checksum/signature.
.
Contract: Do not break the API of stdlib archive/tar in our fork (ideally find
an upstream mergeable solution).
.
This package contains the source.
- tar-split: tar archive assembly/disassembly
Pristinely disassembling a tar archive, and stashing needed raw bytes and
offsets to reassemble a validating original archive.
.
Eventually this should detect TARs that this is not possible with.
.
For example stored sparse files that have "holes" in them, will be read as a
contiguous file, though the archive contents may be recorded in sparse format.
Therefore when adding the file payload to a reassembled tar, to achieve
identical output, the file payload would need be precisely re-sparsified. This
is not something I seek to fix imediately, but would rather have an alert that
precise reassembly is not possible. (see more
http://www.gnu. org/software/ tar/manual/ html_node/ Sparse- Formats. html)
.
Other caveat, while tar archives support having multiple file entries for the
same path, we will not support this feature. If there are more than one entries
with the same path, expect an err (like ErrDuplicatePath) or a resulting tar
stream that does not validate your original checksum/signature.
- tar-split-dbgsym: debug symbols for package tar-split
Pristinely disassembling a tar archive, and stashing needed raw bytes and
offsets to reassemble a validating original archive.
.
Eventually this should detect TARs that this is not possible with.
.
For example stored sparse files that have "holes" in them, will be read as a
contiguous file, though the archive contents may be recorded in sparse format.
Therefore when adding the file payload to a reassembled tar, to achieve
identical output, the file payload would need be precisely re-sparsified. This
is not something I seek to fix imediately, but would rather have an alert that
precise reassembly is not possible. (see more
http://www.gnu. org/software/ tar/manual/ html_node/ Sparse- Formats. html)
.
Other caveat, while tar archives support having multiple file entries for the
same path, we will not support this feature. If there are more than one entries
with the same path, expect an err (like ErrDuplicatePath) or a resulting tar
stream that does not validate your original checksum/signature.
