summaryrefslogtreecommitdiff
path: root/source/a/tar/tar.nolonezero.diff
diff options
context:
space:
mode:
Diffstat (limited to 'source/a/tar/tar.nolonezero.diff')
-rw-r--r--source/a/tar/tar.nolonezero.diff25
1 files changed, 25 insertions, 0 deletions
diff --git a/source/a/tar/tar.nolonezero.diff b/source/a/tar/tar.nolonezero.diff
new file mode 100644
index 00000000..3c6f6f97
--- /dev/null
+++ b/source/a/tar/tar.nolonezero.diff
@@ -0,0 +1,25 @@
+--- ./src/list.c.orig 2004-05-10 04:49:09.000000000 -0700
++++ ./src/list.c 2004-06-06 13:13:23.000000000 -0700
+@@ -138,6 +138,14 @@
+
+ if (!ignore_zeros_option)
+ {
++
++ /*
++ * According to POSIX tar specs, this is wrong, but on the web
++ * there are some tar specs that can trigger this, and some tar
++ * implementations create tars according to that spec. For now,
++ * let's not be pedantic about issuing the warning.
++ */
++#if 0
+ char buf[UINTMAX_STRSIZE_BOUND];
+
+ status = read_header (false);
+@@ -145,6 +153,7 @@
+ break;
+ WARN ((0, 0, _("A lone zero block at %s"),
+ STRINGIFY_BIGINT (current_block_ordinal (), buf)));
++#endif
+ break;
+ }
+ status = prev_status;