Hello community,

here is the log from the commit of package python-imaging for openSUSE:Factory 
checked in at 2013-03-01 07:50:12
++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++
Comparing /work/SRC/openSUSE:Factory/python-imaging (Old)
 and      /work/SRC/openSUSE:Factory/.python-imaging.new (New)
++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++

Package is "python-imaging", Maintainer is "[email protected]"

Changes:
--------
--- /work/SRC/openSUSE:Factory/python-imaging/python-imaging.changes    
2012-04-17 07:49:01.000000000 +0200
+++ /work/SRC/openSUSE:Factory/.python-imaging.new/python-imaging.changes       
2013-03-01 07:50:14.000000000 +0100
@@ -1,0 +2,11 @@
+Thu Feb 28 08:56:10 UTC 2013 - [email protected]
+
+- license update: HPND
+
+
+-------------------------------------------------------------------
+Wed Feb 27 06:18:23 UTC 2013 - [email protected]
+
+- update license to new format
+
+-------------------------------------------------------------------

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

Other differences:
------------------
++++++ python-imaging.spec ++++++
--- /var/tmp/diff_new_pack.Q87j22/_old  2013-03-01 07:50:15.000000000 +0100
+++ /var/tmp/diff_new_pack.Q87j22/_new  2013-03-01 07:50:15.000000000 +0100
@@ -1,7 +1,7 @@
 #
 # spec file for package python-imaging
 #
-# Copyright (c) 2012 SUSE LINUX Products GmbH, Nuernberg, Germany.
+# Copyright (c) 2013 SUSE LINUX Products GmbH, Nuernberg, Germany.
 #
 # All modifications and additions to the file contributed by third parties
 # remain the property of their copyright owners, unless otherwise agreed
@@ -52,7 +52,7 @@
 Requires:       tk
 Obsoletes:      pyimglib
 Summary:        The Python Imaging Library - PIL
-License:        Python-2.0 ; MIT
+License:        HPND
 Group:          Development/Libraries/Python
 Source:         Imaging-%{version}.tar.bz2
 Source1:        pil-handbook.pdf

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

Reply via email to