Hello community,

here is the log from the commit of package python-mock for openSUSE:Factory 
checked in at 2014-02-26 06:55:09
++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++
Comparing /work/SRC/openSUSE:Factory/python-mock (Old)
 and      /work/SRC/openSUSE:Factory/.python-mock.new (New)
++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++

Package is "python-mock"

Changes:
--------
--- /work/SRC/openSUSE:Factory/python-mock/python-mock.changes  2014-02-13 
15:10:47.000000000 +0100
+++ /work/SRC/openSUSE:Factory/.python-mock.new/python-mock.changes     
2014-02-26 06:55:13.000000000 +0100
@@ -1,0 +2,11 @@
+Tue Feb 18 13:37:33 CET 2014 - [email protected]
+
+- added LICENSE.txt as doc file 
+
+-------------------------------------------------------------------
+Wed Feb 12 19:06:24 UTC 2014 - [email protected]
+
+- license update: BSD-2-Clause
+  See the License.txt file
+
+-------------------------------------------------------------------
@@ -11 +22 @@
-  newer than Python 2.7.x
+  newer than Python 2.7.x (bnc#863813)

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

Other differences:
------------------
++++++ python-mock.spec ++++++
--- /var/tmp/diff_new_pack.q5QYNr/_old  2014-02-26 06:55:14.000000000 +0100
+++ /var/tmp/diff_new_pack.q5QYNr/_new  2014-02-26 06:55:14.000000000 +0100
@@ -21,7 +21,7 @@
 Release:        0
 Url:            http://www.voidspace.org.uk/python/mock/
 Summary:        A Python Mocking and Patching Library for Testing
-License:        BSD-3-Clause
+License:        BSD-2-Clause
 Group:          Development/Languages/Python
 Source:         
http://pypi.python.org/packages/source/m/mock/mock-%{version}.tar.gz
 # PATCH-FIX-UPSTREAM [email protected] -- 
http://code.google.com/p/mock/issues/detail?id=194
@@ -61,7 +61,7 @@
 
 %files
 %defattr(-,root,root,-)
-%doc README.txt html
+%doc README.txt LICENSE.txt html
 %{python_sitelib}/*
 
 %changelog

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

Reply via email to