Hello community,

here is the log from the commit of package python-M2Crypto for openSUSE:Factory 
checked in at 2011-12-21 15:41:40
++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++
Comparing /work/SRC/openSUSE:Factory/python-M2Crypto (Old)
 and      /work/SRC/openSUSE:Factory/.python-M2Crypto.new (New)
++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++

Package is "python-M2Crypto", Maintainer is ""

Changes:
--------
--- /work/SRC/openSUSE:Factory/python-M2Crypto/python-M2Crypto.changes  
2011-09-26 10:12:45.000000000 +0200
+++ /work/SRC/openSUSE:Factory/.python-M2Crypto.new/python-M2Crypto.changes     
2011-12-21 15:41:42.000000000 +0100
@@ -1,0 +2,5 @@
+Tue Dec 13 13:16:21 UTC 2011 - [email protected]
+
+- fix license to be in spdx.org format
+
+-------------------------------------------------------------------

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

Other differences:
------------------
++++++ python-M2Crypto.spec ++++++
--- /var/tmp/diff_new_pack.dNwQBS/_old  2011-12-21 15:41:43.000000000 +0100
+++ /var/tmp/diff_new_pack.dNwQBS/_new  2011-12-21 15:41:43.000000000 +0100
@@ -15,22 +15,20 @@
 # Please submit bugfixes or comments via http://bugs.opensuse.org/
 #
 
-
-
 Name:           python-M2Crypto
 Version:        0.21.1
 Release:        0
 Url:            http://chandlerproject.org/bin/view/Projects/MeTooCrypto
 Summary:        Crypto and SSL toolkit for Python
-License:        X11/MIT, ZPL-2.0, BSD-3-Clause
+License:        MIT and ZPL-2.0 and BSD-3-Clause
 Group:          Development/Languages/Python
 Source:         M2Crypto-%{version}.tar.gz
 BuildRoot:      %{_tmppath}/%{name}-%{version}-build
+BuildRequires:  openssl
+BuildRequires:  openssl-devel
 BuildRequires:  python-devel
 BuildRequires:  python-distribute
 BuildRequires:  swig
-BuildRequires:  openssl
-BuildRequires:  openssl-devel
 %if 0%{?suse_version}
 %py_requires
 %if 0%{?suse_version} > 1010

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

Reply via email to