|
|
990d53 |
From 60d08c6d82f0c33a6704c79afd416902eb8c663f Mon Sep 17 00:00:00 2001
|
|
|
990d53 |
From: rpm-build <rpm-build>
|
|
|
990d53 |
Date: Mon, 28 Jul 2014 08:08:50 +0200
|
|
|
990d53 |
Subject: [PATCH 1/9] Stop issuing lone zero block warnings (downstram)
|
|
|
990d53 |
|
|
|
990d53 |
Resolves: #135601
|
|
|
990d53 |
|
|
|
990d53 |
---
|
|
|
990d53 |
src/list.c | 11 +++++++++++
|
|
|
990d53 |
1 file changed, 11 insertions(+)
|
|
|
990d53 |
|
|
|
990d53 |
diff --git a/src/list.c b/src/list.c
|
|
|
990d53 |
index b4277e0..0c7a740 100644
|
|
|
990d53 |
--- a/src/list.c
|
|
|
990d53 |
+++ b/src/list.c
|
|
|
990d53 |
@@ -240,6 +240,14 @@ read_and (void (*do_something) (void))
|
|
|
990d53 |
|
|
|
990d53 |
if (!ignore_zeros_option)
|
|
|
990d53 |
{
|
|
|
990d53 |
+ /*
|
|
|
990d53 |
+ * According to POSIX tar specs, this is wrong, but on the web
|
|
|
990d53 |
+ * there are some tar specs that can trigger this, and some tar
|
|
|
990d53 |
+ * implementations create tars according to that spec. For now,
|
|
|
990d53 |
+ * let's not be pedantic about issuing the warning.
|
|
|
990d53 |
+ */
|
|
|
990d53 |
+#if 0
|
|
|
990d53 |
+
|
|
|
990d53 |
char buf[UINTMAX_STRSIZE_BOUND];
|
|
|
990d53 |
|
|
|
990d53 |
status = read_header (¤t_header, ¤t_stat_info,
|
|
|
990d53 |
@@ -249,6 +257,9 @@ read_and (void (*do_something) (void))
|
|
|
990d53 |
WARNOPT (WARN_ALONE_ZERO_BLOCK,
|
|
|
990d53 |
(0, 0, _("A lone zero block at %s"),
|
|
|
990d53 |
STRINGIFY_BIGINT (current_block_ordinal (), buf)));
|
|
|
990d53 |
+#endif
|
|
|
990d53 |
+ status = read_header (¤t_header, ¤t_stat_info,
|
|
|
990d53 |
+ read_header_auto);
|
|
|
990d53 |
break;
|
|
|
990d53 |
}
|
|
|
990d53 |
status = prev_status;
|
|
|
990d53 |
--
|
|
|
990d53 |
1.9.3
|
|
|
990d53 |
|