golang-github-vbatts-tar-split 0.11.2+ds1-1build1 source package in Ubuntu

Changelog

golang-github-vbatts-tar-split (0.11.2+ds1-1build1) mantic; urgency=medium

  * No-change rebuild with Go 1.21.

 -- Michael Hudson-Doyle <email address hidden>  Thu, 24 Aug 2023 17:15:53 +1200

Upload details

Uploaded by:
Michael Hudson-Doyle
Uploaded to:
Mantic
Original maintainer:
Debian Go Packaging Team
Architectures:
any all
Section:
misc
Urgency:
Medium Urgency

See full publishing history Publishing

Series Pocket Published Component Section
Noble release universe misc
Mantic release universe misc

Downloads

File Size SHA-256 Checksum
golang-github-vbatts-tar-split_0.11.2+ds1.orig.tar.xz 64.5 KiB e2e54697f301c0a03893b36f6675e0892349f3808fc8d4dd93f3146f7a090c06
golang-github-vbatts-tar-split_0.11.2+ds1-1build1.debian.tar.xz 4.1 KiB c42d8ecf24b22db345497fa459122711fa07dfee6868bf8eee215e01f61a6c82
golang-github-vbatts-tar-split_0.11.2+ds1-1build1.dsc 2.5 KiB 1c1c2c20c35351983856c55b4c52e8f3e603a7fcfb50a709e96d7c813ec11f13

View changes file

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 immediately, 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 immediately, 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 tar-split