2016-06-30 22:26:57 +02:00
|
|
|
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 @@
|
2009-08-26 17:00:38 +02:00
|
|
|
|
|
|
|
if (!ignore_zeros_option)
|
|
|
|
{
|
|
|
|
+
|
2011-04-25 15:37:00 +02:00
|
|
|
+ /*
|
|
|
|
+ * 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
|
2009-08-26 17:00:38 +02:00
|
|
|
char buf[UINTMAX_STRSIZE_BOUND];
|
|
|
|
|
2011-04-25 15:37:00 +02:00
|
|
|
status = read_header (¤t_header, ¤t_stat_info,
|
2016-06-30 22:26:57 +02:00
|
|
|
@@ -220,6 +228,7 @@
|
2010-05-19 10:58:23 +02:00
|
|
|
WARNOPT (WARN_ALONE_ZERO_BLOCK,
|
|
|
|
(0, 0, _("A lone zero block at %s"),
|
|
|
|
STRINGIFY_BIGINT (current_block_ordinal (), buf)));
|
2009-08-26 17:00:38 +02:00
|
|
|
+#endif
|
|
|
|
break;
|
|
|
|
}
|
|
|
|
status = prev_status;
|