Blame SOURCES/tar-1.28-loneZeroWarning.patch

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