Hello community,

here is the log from the commit of package tar for openSUSE:Factory checked in 
at 2014-08-01 11:48:27
++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++
Comparing /work/SRC/openSUSE:Factory/tar (Old)
 and      /work/SRC/openSUSE:Factory/.tar.new (New)
++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++

Package is "tar"

Changes:
--------
--- /work/SRC/openSUSE:Factory/tar/tar.changes  2014-04-06 09:54:01.000000000 
+0200
+++ /work/SRC/openSUSE:Factory/.tar.new/tar.changes     2014-08-01 
11:48:30.000000000 +0200
@@ -1,0 +2,9 @@
+Mon Jul 28 20:01:53 UTC 2014 - [email protected]
+
+- don't print lone zero blocks warning (bnc#881863)
+  * there are many tar implementations around that create invalid
+    archives with a zero block in the middle
+  * https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=235820
+  * added tar-ignore_lone_zero_blocks.patch from Fedora
+
+-------------------------------------------------------------------

New:
----
  tar-ignore_lone_zero_blocks.patch

++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++

Other differences:
------------------
++++++ tar.spec ++++++
--- /var/tmp/diff_new_pack.L72Pke/_old  2014-08-01 11:48:31.000000000 +0200
+++ /var/tmp/diff_new_pack.L72Pke/_new  2014-08-01 11:48:31.000000000 +0200
@@ -36,6 +36,10 @@
 Patch7:         tar-1.26-remove_O_NONBLOCK.patch
 Patch8:         tar-fix_eternal_loop_in_handle_option.patch
 Patch10:        paxutils-rtapelib_mtget.patch
+# don't print warning about zero blocks
+# the patch is used in Fedora and Debian
+# https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=235820
+Patch11:        tar-ignore_lone_zero_blocks.patch
 Patch20:        add_readme-tests.patch
 %if 0%{?suse_version} >= %min_suse_ver
 BuildRequires:  help2man
@@ -80,6 +84,7 @@
 %patch7 -p1
 %patch8 -p1
 %patch10 -p1
+%patch11 -p1
 %patch20 -p1
 
 %build


++++++ tar-ignore_lone_zero_blocks.patch ++++++
Index: tar-1.26/src/list.c
===================================================================
--- tar-1.26.orig/src/list.c    2011-02-16 23:12:16.000000000 +0100
+++ tar-1.26/src/list.c 2014-06-11 11:48:38.129824435 +0200
@@ -212,6 +212,14 @@ read_and (void (*do_something) (void))
 
          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,9 @@ read_and (void (*do_something) (void))
              WARNOPT (WARN_ALONE_ZERO_BLOCK,
                       (0, 0, _("A lone zero block at %s"),
                        STRINGIFY_BIGINT (current_block_ordinal (), buf)));
+#endif
+             status = read_header (&current_header, &current_stat_info,
+                                   read_header_auto);
              break;
            }
          status = prev_status;

-- 
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]

Reply via email to