summaryrefslogtreecommitdiffstats
path: root/source/a/tar/tar.nolonezero.diff
blob: e1316beb3c2f8e90c9ac3ada8913c540f91f0d26 (plain) (blame)
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
--- ./src/list.c.orig	2010-11-01 15:34:59.000000000 -0500
+++ ./src/list.c	2010-11-08 13:42:14.000000000 -0600
@@ -212,6 +212,14 @@
 
 	  if (!ignore_zeros_option)
 	    {
+
+	      /* 
+	       * 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.
+	       */
+#if 0	       
 	      char buf[UINTMAX_STRSIZE_BOUND];
 
 	      status = read_header (&current_header, &current_stat_info,
@@ -221,6 +229,7 @@
 	      WARNOPT (WARN_ALONE_ZERO_BLOCK,
 		       (0, 0, _("A lone zero block at %s"),
 			STRINGIFY_BIGINT (current_block_ordinal (), buf)));
+#endif
 	      break;
 	    }
 	  status = prev_status;