File: control

package info (click to toggle)
golang-github-vbatts-tar-split 0.11.1-1
  • links: PTS, VCS
  • area: main
  • in suites: bullseye, sid
  • size: 736 kB
  • sloc: makefile: 6
file content (71 lines) | stat: -rw-r--r-- 3,395 bytes parent folder | download
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
59
60
61
62
63
64
65
66
67
68
69
70
71
Source: golang-github-vbatts-tar-split
Section: devel
Priority: optional
Standards-Version: 4.4.0
Maintainer: Debian Go Packaging Team <pkg-go-maintainers@lists.alioth.debian.org>
Uploaders: Tianon Gravi <tianon@debian.org>,
           Tim Potter <tpot@hpe.com>,
           Dmitry Smirnov <onlyjob@debian.org>
Build-Depends: debhelper (>= 12~),
               dh-golang,
               golang-any,
               golang-github-sirupsen-logrus-dev,
               golang-github-urfave-cli-dev
Homepage: https://github.com/vbatts/tar-split
Vcs-Browser: https://salsa.debian.org/go-team/packages/golang-github-vbatts-tar-split
Vcs-Git: https://salsa.debian.org/go-team/packages/golang-github-vbatts-tar-split.git
XS-Go-Import-Path: github.com/vbatts/tar-split
Testsuite: autopkgtest-pkg-go

Package: tar-split
Architecture: any
Depends: ${misc:Depends}, ${shlibs:Depends}
Built-Using: ${misc:Built-Using}
Description: 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.

Package: golang-github-vbatts-tar-split-dev
Architecture: all
Depends: golang-github-sirupsen-logrus-dev,
         golang-github-urfave-cli-dev,
         ${misc:Depends},
         ${shlibs:Depends}
Description: 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.