| 1 |
Source: golang-github-vbatts-tar-split |
| 2 |
Section: devel |
| 3 |
Priority: optional |
| 4 |
Standards-Version: 4.7.0 |
| 5 |
Maintainer: Debian Go Packaging Team <[email protected]> |
| 6 |
Uploaders: Tianon Gravi <[email protected]>, |
| 7 |
Tim Potter <[email protected]>, |
| 8 |
Dmitry Smirnov <[email protected]> |
| 9 |
Build-Depends: debhelper-compat (= 13), |
| 10 |
dh-golang, |
| 11 |
golang-any, |
| 12 |
golang-github-sirupsen-logrus-dev, |
| 13 |
golang-github-stretchr-testify-dev, |
| 14 |
golang-github-urfave-cli-dev |
| 15 |
Homepage: https://github.com/vbatts/tar-split |
| 16 |
Vcs-Browser: https://salsa.debian.org/go-team/packages/golang-github-vbatts-tar-split |
| 17 |
Vcs-Git: https://salsa.debian.org/go-team/packages/golang-github-vbatts-tar-split.git |
| 18 |
XS-Go-Import-Path: github.com/vbatts/tar-split |
| 19 |
Testsuite: autopkgtest-pkg-go |
| 20 |
|
| 21 |
Package: tar-split |
| 22 |
Architecture: any |
| 23 |
Depends: ${misc:Depends}, ${shlibs:Depends} |
| 24 |
Built-Using: ${misc:Built-Using} |
| 25 |
Description: tar archive assembly/disassembly |
| 26 |
Pristinely disassembling a tar archive, and stashing needed raw bytes and |
| 27 |
offsets to reassemble a validating original archive. |
| 28 |
. |
| 29 |
Eventually this should detect TARs that this is not possible with. |
| 30 |
. |
| 31 |
For example stored sparse files that have "holes" in them, will be read as a |
| 32 |
contiguous file, though the archive contents may be recorded in sparse format. |
| 33 |
Therefore when adding the file payload to a reassembled tar, to achieve |
| 34 |
identical output, the file payload would need be precisely re-sparsified. This |
| 35 |
is not something I seek to fix immediately, but would rather have an alert that |
| 36 |
precise reassembly is not possible. (see more |
| 37 |
http://www.gnu.org/software/tar/manual/html_node/Sparse-Formats.html) |
| 38 |
. |
| 39 |
Other caveat, while tar archives support having multiple file entries for the |
| 40 |
same path, we will not support this feature. If there are more than one entries |
| 41 |
with the same path, expect an err (like ErrDuplicatePath) or a resulting tar |
| 42 |
stream that does not validate your original checksum/signature. |
| 43 |
|
| 44 |
Package: golang-github-vbatts-tar-split-dev |
| 45 |
Architecture: all |
| 46 |
Depends: golang-github-sirupsen-logrus-dev, |
| 47 |
golang-github-urfave-cli-dev, |
| 48 |
${misc:Depends}, |
| 49 |
${shlibs:Depends} |
| 50 |
Multi-Arch: foreign |
| 51 |
Description: tar archive assembly/disassembly (source) |
| 52 |
Pristinely disassembling a tar archive, and stashing needed raw bytes and |
| 53 |
offsets to reassemble a validating original archive. |
| 54 |
. |
| 55 |
Eventually this should detect TARs that this is not possible with. |
| 56 |
. |
| 57 |
For example stored sparse files that have "holes" in them, will be read as a |
| 58 |
contiguous file, though the archive contents may be recorded in sparse format. |
| 59 |
Therefore when adding the file payload to a reassembled tar, to achieve |
| 60 |
identical output, the file payload would need be precisely re-sparsified. This |
| 61 |
is not something I seek to fix immediately, but would rather have an alert that |
| 62 |
precise reassembly is not possible. (see more |
| 63 |
http://www.gnu.org/software/tar/manual/html_node/Sparse-Formats.html) |
| 64 |
. |
| 65 |
Other caveat, while tar archives support having multiple file entries for the |
| 66 |
same path, we will not support this feature. If there are more than one entries |
| 67 |
with the same path, expect an err (like ErrDuplicatePath) or a resulting tar |
| 68 |
stream that does not validate your original checksum/signature. |
| 69 |
. |
| 70 |
Contract: Do not break the API of stdlib archive/tar in our fork (ideally find |
| 71 |
an upstream mergeable solution). |
| 72 |
. |
| 73 |
This package contains the source. |