Ubuntu
golang-github-vbatts-tar-split package

golang-github-vbatts-tar-split 0.11.2+ds1-1ubuntu0.24.04.1 source package in Ubuntu

Changelog

golang-github-vbatts-tar-split (0.11.2+ds1-1ubuntu0.24.04.1) noble-security; urgency=medium

  * No change rebuild due to golang-1.21 update

 -- Nishit Majithia <email address hidden>  Fri, 12 Jul 2024 12:05:08 +0530

Upload details

Uploaded by:
Nishit Majithia
Uploaded to:
Noble
Original maintainer:
Ubuntu Developers
Architectures:
any all
Section:
devel
Urgency:
Medium Urgency

See full publishing history Publishing

Series Pocket Published Component Section
Noble updates universe misc
Noble security 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-1ubuntu0.24.04.1.debian.tar.xz 4.2 KiB cf511e486745eea5941db7dc7a09b16021b5f5ddbf10b6354b9e4a5f6fbcd6b5
golang-github-vbatts-tar-split_0.11.2+ds1-1ubuntu0.24.04.1.dsc 2.4 KiB 03c5714981840222ed8495b0c8601b51f8ba09a356885f3164f806fd089eeb8f

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