lzip/lziprecover
1
0
Fork 0
Code Issues Activity

Merging upstream version 1.18~pre1.

Browse source 
Signed-off-by: Daniel Baumann <daniel@debian.org>
This commit is contained in:
Daniel Baumann 2025-02-21 11:25:43 +01:00
parent 2afbebfdd4
commit 708d27c30a
Signed by: daniel
GPG key ID: FBB4F0E80A80222F
17 changed files with 452 additions and 200 deletions
Download patch file Download diff file Expand all files Collapse all files

4
doc/lziprecover.1
View file

@ -1,5 +1,5 @@
.\" DO NOT MODIFY THIS FILE! It was generated by help2man 1.46.1.
.TH LZIPRECOVER "1" "May 2015" "lziprecover 1.17" "User Commands"
.TH LZIPRECOVER "1" "June 2015" "lziprecover 1.18-pre1" "User Commands"
.SH NAME
lziprecover \- recovers data from damaged lzip files
.SH SYNOPSIS
@ -30,7 +30,7 @@ send decompressed output to standard output
decompress
.TP
\fB\-D\fR, \fB\-\-range\-decompress=\fR<range>
decompress only a range of bytes (N\-M)
decompress a range of bytes (N\-M) to stdout
.TP
\fB\-f\fR, \fB\-\-force\fR
overwrite existing output files

28
doc/lziprecover.info
View file

@ -12,7 +12,7 @@ File: lziprecover.info, Node: Top, Next: Introduction, Up: (dir)
Lziprecover Manual
******************
This manual is for Lziprecover (version 1.17, 28 May 2015).
This manual is for Lziprecover (version 1.18-pre1, 30 June 2015).
* Menu:
@ -274,7 +274,7 @@ files::), if at least one backup copy of the file is made.
separate media.
How does lzip compare with gzip and bzip2 with respect to data
safety? Lets suppose that you made a backup copy of your valuable
safety? Lets suppose that you made a backup of your valuable
scientific data, compressed it, and stored two copies on separate
media. Years later you notice that both copies are corrupt.
@ -652,18 +652,18 @@ Concept index

Tag Table:
Node: Top231
Node: Introduction1208
Node: Invoking lziprecover4304
Node: Data safety9737
Node: Repairing files11666
Node: Merging files13568
Node: File names15409
Node: File format15873
Node: Examples18277
Ref: ddrescue-example19523
Node: Unzcrash20779
Node: Problems23333
Node: Concept index23885
Node: Introduction1214
Node: Invoking lziprecover4310
Node: Data safety9743
Node: Repairing files11667
Node: Merging files13569
Node: File names15410
Node: File format15874
Node: Examples18278
Ref: ddrescue-example19524
Node: Unzcrash20780
Node: Problems23334
Node: Concept index23886

End Tag Table

10
doc/lziprecover.texi
View file

@ -6,8 +6,8 @@
@finalout
@c %**end of header
@set UPDATED 28 May 2015
@set VERSION 1.17
@set UPDATED 30 June 2015
@set VERSION 1.18-pre1
@dircategory Data Compression
@direntry
@ -302,9 +302,9 @@ The only remedy for total device failure is storing backup copies in
separate media.
How does lzip compare with gzip and bzip2 with respect to data safety?
Lets suppose that you made a backup copy of your valuable scientific
data, compressed it, and stored two copies on separate media. Years
later you notice that both copies are corrupt.
Lets suppose that you made a backup of your valuable scientific data,
compressed it, and stored two copies on separate media. Years later you
notice that both copies are corrupt.
If you compressed with gzip and both copies suffer any damage in the
data stream, even if it is just one altered bit, the original data can't