2018-09-07 01:22:45 +02:00
|
|
|
--- ./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 @@
|
2009-08-26 17:00:38 +02:00
|
|
|
|
|
|
|
if (!ignore_zeros_option)
|
|
|
|
{
|
2018-09-07 01:22:45 +02:00
|
|
|
- char buf[UINTMAX_STRSIZE_BOUND];
|
2009-08-26 17:00:38 +02:00
|
|
|
+
|
2018-09-07 01:22:45 +02:00
|
|
|
+ /*
|
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.
|
2018-09-07 01:22:45 +02:00
|
|
|
+ *
|
|
|
|
+ * char buf[UINTMAX_STRSIZE_BOUND]; */
|
2009-08-26 17:00:38 +02:00
|
|
|
|
2011-04-25 15:37:00 +02:00
|
|
|
status = read_header (¤t_header, ¤t_stat_info,
|
2018-09-07 01:22:45 +02:00
|
|
|
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))); */
|
2009-08-26 17:00:38 +02:00
|
|
|
break;
|
|
|
|
}
|
|
|
|
status = prev_status;
|