How to Install and Uninstall tar-split Package on Ubuntu 20.10 (Groovy Gorilla)
Last updated: February 24,2025
1. Install "tar-split" package
Learn how to install tar-split on Ubuntu 20.10 (Groovy Gorilla)
$
sudo apt update
Copied
$
sudo apt install
tar-split
Copied
2. Uninstall "tar-split" package
This tutorial shows how to uninstall tar-split on Ubuntu 20.10 (Groovy Gorilla):
$
sudo apt remove
tar-split
Copied
$
sudo apt autoclean && sudo apt autoremove
Copied
3. Information about the tar-split package on Ubuntu 20.10 (Groovy Gorilla)
Package: tar-split
Architecture: amd64
Version: 0.11.1-1build1
Built-Using: go-md2man (= 1.0.10+ds-1), golang-1.14 (= 1.14.7-2ubuntu1), golang-blackfriday (= 1.5.2+git20200218.41c5fcc-1), golang-github-urfave-cli (= 1.22.2-4), golang-golang-x-sys (= 0.0~git20200523.0598657-1), golang-logrus (= 1.6.0-1)
Priority: extra
Section: universe/devel
Source: golang-github-vbatts-tar-split
Origin: Ubuntu
Maintainer: Ubuntu Developers
Original-Maintainer: Debian Go Packaging Team
Bugs: https://bugs.launchpad.net/ubuntu/+filebug
Installed-Size: 3949
Depends: libc6 (>= 2.32)
Filename: pool/universe/g/golang-github-vbatts-tar-split/tar-split_0.11.1-1build1_amd64.deb
Size: 1268560
MD5sum: 72fdc96f484046ffa469009ee2fcfa28
SHA1: daa9c587d06512c0bff144e852ec7d37f96bd2e6
SHA256: eae9a7cdf6f9a8da62980587ac882e3f624d3cd8028a60f5a1c4b4f048e5d96c
SHA512: aa3517dce0e97bd629fa7219ddc8419ca50df74d8e02c7bf301bfc8e3c18597d9c0cd60ecd60d604dc6ca48a106103103ccd44bc18574416ca45f242794bbf17
Homepage: https://github.com/vbatts/tar-split
Description-en: 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.
Description-md5: 0a7073586375397f4634a2441b79a786
Architecture: amd64
Version: 0.11.1-1build1
Built-Using: go-md2man (= 1.0.10+ds-1), golang-1.14 (= 1.14.7-2ubuntu1), golang-blackfriday (= 1.5.2+git20200218.41c5fcc-1), golang-github-urfave-cli (= 1.22.2-4), golang-golang-x-sys (= 0.0~git20200523.0598657-1), golang-logrus (= 1.6.0-1)
Priority: extra
Section: universe/devel
Source: golang-github-vbatts-tar-split
Origin: Ubuntu
Maintainer: Ubuntu Developers
Original-Maintainer: Debian Go Packaging Team
Bugs: https://bugs.launchpad.net/ubuntu/+filebug
Installed-Size: 3949
Depends: libc6 (>= 2.32)
Filename: pool/universe/g/golang-github-vbatts-tar-split/tar-split_0.11.1-1build1_amd64.deb
Size: 1268560
MD5sum: 72fdc96f484046ffa469009ee2fcfa28
SHA1: daa9c587d06512c0bff144e852ec7d37f96bd2e6
SHA256: eae9a7cdf6f9a8da62980587ac882e3f624d3cd8028a60f5a1c4b4f048e5d96c
SHA512: aa3517dce0e97bd629fa7219ddc8419ca50df74d8e02c7bf301bfc8e3c18597d9c0cd60ecd60d604dc6ca48a106103103ccd44bc18574416ca45f242794bbf17
Homepage: https://github.com/vbatts/tar-split
Description-en: 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.
Description-md5: 0a7073586375397f4634a2441b79a786