Hello community,

here is the log from the commit of package libftdi1 for openSUSE:Factory 
checked in at 2012-05-21 07:28:03
++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++
Comparing /work/SRC/openSUSE:Factory/libftdi1 (Old)
 and      /work/SRC/openSUSE:Factory/.libftdi1.new (New)
++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++

Package is "libftdi1", Maintainer is ""

Changes:
--------
--- /work/SRC/openSUSE:Factory/libftdi1/libftdi1.changes        2011-09-23 
02:08:14.000000000 +0200
+++ /work/SRC/openSUSE:Factory/.libftdi1.new/libftdi1.changes   2012-05-21 
07:28:04.000000000 +0200
@@ -1,0 +2,6 @@
+Thu May  3 16:21:44 UTC 2012 - [email protected]
+
+- license update: LGPL-2.1+ and GPL-2.0-with-classpath-exception
+  Use SPDX format (http://www.spdx.org/licenses)
+
+-------------------------------------------------------------------

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

Other differences:
------------------
++++++ libftdi1.spec ++++++
--- /var/tmp/diff_new_pack.r8f2AC/_old  2012-05-21 07:28:05.000000000 +0200
+++ /var/tmp/diff_new_pack.r8f2AC/_new  2012-05-21 07:28:05.000000000 +0200
@@ -23,7 +23,7 @@
 Name:           libftdi1
 Version:        0.18
 Release:        1
-License:        LGPL for libftdi and GPLv2+linking exception for the C++ 
wrapper
+License:        LGPL-2.1+ and GPL-2.0-with-classpath-exception
 Group:          Hardware/Other
 Url:            http://www.intra2net.com/en/developer/libftdi
 Source:         libftdi-%{version}.tar.bz2
@@ -34,7 +34,7 @@
 BuildRequires:  doxygen libusb-devel pkgconfig
 
 %package -n libftdi1-devel
-License:        LGPL for libftdi and GPLv2+linking exception for the C++ 
wrapper
+License:        LGPL-2.1+ and GPL-2.0-with-classpath-exception
 Summary:        Header files and static libraries for libftdi
 Group:          Development/Libraries/C and C++
 Requires:       libftdi1 = %{version}, libusb-devel

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

Reply via email to