Hello community,

here is the log from the commit of package libvshadow for openSUSE:Factory 
checked in at 2016-01-28 17:23:10
++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++
Comparing /work/SRC/openSUSE:Factory/libvshadow (Old)
 and      /work/SRC/openSUSE:Factory/.libvshadow.new (New)
++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++

Package is "libvshadow"

Changes:
--------
--- /work/SRC/openSUSE:Factory/libvshadow/libvshadow.changes    2015-01-30 
15:04:52.000000000 +0100
+++ /work/SRC/openSUSE:Factory/.libvshadow.new/libvshadow.changes       
2016-01-28 17:23:53.000000000 +0100
@@ -1,0 +2,8 @@
+Mon Jan 25 12:27:50 UTC 2016 - [email protected]
+
+- update to v0~20160110
+       * worked on Python 3 support
+       * worked on win2k3 format support
+       * introduced new function has_in_volume_data
+
+-------------------------------------------------------------------

Old:
----
  libvshadow-alpha-20150106.tar.gz

New:
----
  libvshadow-alpha-20160110.tar.gz

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

Other differences:
------------------
++++++ libvshadow.spec ++++++
--- /var/tmp/diff_new_pack.kJzmvn/_old  2016-01-28 17:23:54.000000000 +0100
+++ /var/tmp/diff_new_pack.kJzmvn/_new  2016-01-28 17:23:54.000000000 +0100
@@ -1,7 +1,7 @@
 #
 # spec file for package libvshadow
 #
-# Copyright (c) 2015 SUSE LINUX Products GmbH, Nuernberg, Germany.
+# Copyright (c) 2016 SUSE LINUX GmbH, Nuernberg, Germany.
 #
 # All modifications and additions to the file contributed by third parties
 # remain the property of their copyright owners, unless otherwise agreed
@@ -18,7 +18,7 @@
 
 Name:           libvshadow
 %define lname  libvshadow1
-%define timestamp      20150106
+%define timestamp      20160110
 Version:        0~%{timestamp}
 Release:        0
 Summary:        Library to access the Volume Shadow Snapshot (VSS) format

++++++ libvshadow-alpha-20150106.tar.gz -> libvshadow-alpha-20160110.tar.gz 
++++++
++++ 26196 lines of diff (skipped)


Reply via email to