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.diff31
1 files changed, 18 insertions, 13 deletions
diff --git a/source/a/tar/tar.nolonezero.diff b/source/a/tar/tar.nolonezero.diff
index c47e067f..52967972 100644
--- a/source/a/tar/tar.nolonezero.diff
+++ b/source/a/tar/tar.nolonezero.diff
@@ -1,26 +1,31 @@
-diff -Nur tar-1.27.1.orig/src/list.c tar-1.27.1/src/list.c
---- tar-1.27.1.orig/src/list.c 2013-03-14 15:18:10.000000000 -0500
-+++ tar-1.27.1/src/list.c 2014-07-26 20:42:16.613004098 -0500
-@@ -211,6 +211,14 @@
+--- ./src/list.c.orig 2017-12-16 15:23:12.000000000 -0600
++++ ./src/list.c 2018-09-06 16:51:52.982740004 -0500
+@@ -242,15 +242,22 @@
if (!ignore_zeros_option)
{
+- char buf[UINTMAX_STRSIZE_BOUND];
+
-+ /*
++ /*
+ * 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];
++ *
++ * char buf[UINTMAX_STRSIZE_BOUND]; */
status = read_header (&current_header, &current_stat_info,
-@@ -220,6 +228,7 @@
- WARNOPT (WARN_ALONE_ZERO_BLOCK,
- (0, 0, _("A lone zero block at %s"),
- STRINGIFY_BIGINT (current_block_ordinal (), buf)));
-+#endif
+ read_header_auto);
+- if (status == HEADER_ZERO_BLOCK)
+- break;
+- WARNOPT (WARN_ALONE_ZERO_BLOCK,
+- (0, 0, _("A lone zero block at %s"),
+- STRINGIFY_BIGINT (current_block_ordinal (), buf)));
++ /* if (status == HEADER_ZERO_BLOCK)
++ * break;
++ * WARNOPT (WARN_ALONE_ZERO_BLOCK,
++ * (0, 0, _("A lone zero block at %s"),
++ * STRINGIFY_BIGINT (current_block_ordinal (), buf))); */
break;
}
status = prev_status;