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.diff29
1 files changed, 15 insertions, 14 deletions
diff --git a/source/a/tar/tar.nolonezero.diff b/source/a/tar/tar.nolonezero.diff
index 3c6f6f97b..0209c692a 100644
--- a/source/a/tar/tar.nolonezero.diff
+++ b/source/a/tar/tar.nolonezero.diff
@@ -1,24 +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
+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 @@
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 (false);
-@@ -145,6 +153,7 @@
- break;
- WARN ((0, 0, _("A lone zero block at %s"),
- STRINGIFY_BIGINT (current_block_ordinal (), buf)));
+ status = read_header (&current_header, &current_stat_info,
+@@ -147,6 +155,7 @@
+ WARNOPT (WARN_ALONE_ZERO_BLOCK,
+ (0, 0, _("A lone zero block at %s"),
+ STRINGIFY_BIGINT (current_block_ordinal (), buf)));
+#endif
break;
}