summaryrefslogtreecommitdiffstats
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, 12 insertions, 13 deletions
diff --git a/source/a/tar/tar.nolonezero.diff b/source/a/tar/tar.nolonezero.diff
index 0209c692a..e1316beb3 100644
--- a/source/a/tar/tar.nolonezero.diff
+++ b/source/a/tar/tar.nolonezero.diff
@@ -1,22 +1,21 @@
-diff -Nur tar-1.23.orig//src/list.c tar-1.23//src/list.c
---- tar-1.23.orig//src/list.c 2010-01-26 05:28:09.000000000 -0600
-+++ tar-1.23//src/list.c 2010-03-15 23:46:19.841670026 -0500
-@@ -138,6 +138,14 @@
+--- ./src/list.c.orig 2010-11-01 15:34:59.000000000 -0500
++++ ./src/list.c 2010-11-08 13:42:14.000000000 -0600
+@@ -212,6 +212,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
++ /*
++ * 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 (&current_header, &current_stat_info,
-@@ -147,6 +155,7 @@
+ status = read_header (&current_header, &current_stat_info,
+@@ -221,6 +229,7 @@
WARNOPT (WARN_ALONE_ZERO_BLOCK,
(0, 0, _("A lone zero block at %s"),
STRINGIFY_BIGINT (current_block_ordinal (), buf)));