Blame SOURCES/tar-1.14-loneZeroWarning.patch
|
|
b77676 |
diff --git a/src/list.c b/src/list.c
|
|
|
b77676 |
index cf2de09..f4e6e0a 100644
|
|
|
b77676 |
--- a/src/list.c
|
|
|
b77676 |
+++ b/src/list.c
|
|
|
b77676 |
@@ -212,6 +212,14 @@ read_and (void (*do_something) (void))
|
|
|
b77676 |
|
|
|
b77676 |
if (!ignore_zeros_option)
|
|
|
b77676 |
{
|
|
|
b77676 |
+ /*
|
|
|
b77676 |
+ * According to POSIX tar specs, this is wrong, but on the web
|
|
|
b77676 |
+ * there are some tar specs that can trigger this, and some tar
|
|
|
b77676 |
+ * implementations create tars according to that spec. For now,
|
|
|
b77676 |
+ * let's not be pedantic about issuing the warning.
|
|
|
b77676 |
+ */
|
|
|
b77676 |
+#if 0
|
|
|
b77676 |
+
|
|
|
b77676 |
char buf[UINTMAX_STRSIZE_BOUND];
|
|
|
b77676 |
|
|
|
b77676 |
status = read_header (¤t_header, ¤t_stat_info,
|
|
|
b77676 |
@@ -221,6 +229,9 @@ read_and (void (*do_something) (void))
|
|
|
b77676 |
WARNOPT (WARN_ALONE_ZERO_BLOCK,
|
|
|
b77676 |
(0, 0, _("A lone zero block at %s"),
|
|
|
b77676 |
STRINGIFY_BIGINT (current_block_ordinal (), buf)));
|
|
|
b77676 |
+#endif
|
|
|
b77676 |
+ status = read_header (¤t_header, ¤t_stat_info,
|
|
|
b77676 |
+ read_header_auto);
|
|
|
b77676 |
break;
|
|
|
b77676 |
}
|
|
|
b77676 |
status = prev_status;
|