Blame SOURCES/tar-1.28-loneZeroWarning.patch

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