tar/patches/tar-1.14-loneZeroWarning.patch

   1 diff -ruNp tar-1.22.orig/src/list.c tar-1.22/src/list.c
   2 --- tar-1.22.orig/src/list.c    2008-10-30 12:10:04.000000000 +0100
   3 +++ tar-1.22/src/list.c 2009-03-06 00:03:05.925105425 +0100
   4 @@ -138,6 +138,14 @@ read_and (void (*do_something) (void))
   5
   6           if (!ignore_zeros_option)
   7             {
   8 +             /*
   9 +              * According to POSIX tar specs, this is wrong, but on the web
  10 +              * there are some tar specs that can trigger this, and some tar
  11 +              * implementations create tars according to that spec.  For now,
  12 +              * let's not be pedantic about issuing the warning.
  13 +              */
  14 +#if 0
  15 +
  16               char buf[UINTMAX_STRSIZE_BOUND];
  17
  18               status = read_header (&current_header, &current_stat_info,
  19 @@ -147,6 +155,9 @@ read_and (void (*do_something) (void))
  20               WARNOPT (WARN_ALONE_ZERO_BLOCK,
  21                        (0, 0, _("A lone zero block at %s"),
  22                         STRINGIFY_BIGINT (current_block_ordinal (), buf)));
  23 +#endif
  24 +             status = read_header (&current_header, &current_stat_info,
  25 +                                   read_header_auto);
  26               break;
  27             }
  28           status = prev_status;