Install gzrt with Homebrew

Project links

• Homepage

Commands and aliases

• gzrecover

Project history

Aaron M. Renn's project page explains the origin in backup recovery: a gzip archive failed partway through restore, and gzrecover was written to skip bad data and salvage what could be read. The page and README both stress that recovery is best-effort and that recovered output must be manually verified.

The project page lists gzrt 0.8 from October 2013 and points to a GitHub repository for sources. GitHub repository metadata records the public repository as created in February 2012, with the description 'gzip Recovery Toolkit aka gzrecover'.

Adoption history

gzrt adoption is mostly in Unix package repositories where administrators may need it once, urgently, for a damaged .gz or .tar.gz backup. The supplied package facts show Homebrew, Debian, Ubuntu, MacPorts, Nix, and zypper coverage, which is broad for a niche recovery tool.

Its adoption is also tied to gzip's dominance. Because .gz and .tar.gz files are common backup and source-distribution artifacts, a recovery utility for damaged gzip streams has a place in package collections even when it is not a daily-use command.

How it is used

gzrecover reads a corrupted gzip file or standard input and writes recovered output to a .recovered file by default, with options for output filename, standard-output pipeline mode, verbose logging, and splitting recovered segments. For recovered tarballs, the documentation recommends GNU cpio because tar may stop on format errors.

The project page cautions that many apparently corrupted gzip archives were transferred in FTP ASCII mode and should be re-transferred in binary mode before attempting recovery. That warning is part of the tool's operational history: it is a last-resort recovery command, not a replacement for gunzip.

Why package nerds care

gzrt is interesting to package nerds because it is tiny, old-school, and high-leverage: a single-purpose C utility that can rescue data from the same compressed archives package systems and admins rely on. It also illustrates why distributions keep niche tools around: the value appears when a corrupted backup is the only copy.

It pairs naturally with gzip, zlib, tar, and cpio. The documented tarball recovery flow is a classic Unix composition: run gzrecover to salvage a stream, then use cpio to extract around damaged tar records.

Timeline

• 2002: Copyright history for gzrecover begins.
• 2012: The public GitHub repository was created.
• 2013: gzrt 0.8 was published with bug fixes and improvements.
• 2010s-2020s: Package-manager coverage included Homebrew, Debian, Ubuntu, MacPorts, Nix, and zypper according to the supplied package facts.

Related projects

• gzrt is directly related to GNU gzip, zlib, GNU tar, and GNU cpio. It belongs beside other data-recovery and archive-repair utilities rather than general compression tools.

Sources

• https://api.github.com/repos/arenn/gzrt
• https://github.com/arenn/gzrt
• https://raw.githubusercontent.com/arenn/gzrt/master/README
• https://www.urbanophile.com/arenn/coding/gzrt/gzrt.html
• https://www.urbanophile.com/arenn/hacking/gzrt/gzrt.html