Blame SOURCES/tar-1.28-loneZeroWarning.patch

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