Hello community,

here is the log from the commit of package libvpd2 for openSUSE:Factory checked 
in at 2012-06-05 12:02:32
++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++
Comparing /work/SRC/openSUSE:Factory/libvpd2 (Old)
 and      /work/SRC/openSUSE:Factory/.libvpd2.new (New)
++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++

Package is "libvpd2", Maintainer is "[email protected]"

Changes:
--------
--- /work/SRC/openSUSE:Factory/libvpd2/libvpd2.changes  2012-03-22 
12:36:09.000000000 +0100
+++ /work/SRC/openSUSE:Factory/.libvpd2.new/libvpd2.changes     2012-06-05 
12:02:33.000000000 +0200
@@ -1,0 +2,5 @@
+Fri Jun  1 13:35:11 UTC 2012 - [email protected]
+
+- clean up spec file 
+
+-------------------------------------------------------------------

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

Other differences:
------------------
++++++ libvpd2.spec ++++++
--- /var/tmp/diff_new_pack.WjS1Bn/_old  2012-06-05 12:02:35.000000000 +0200
+++ /var/tmp/diff_new_pack.WjS1Bn/_new  2012-06-05 12:02:35.000000000 +0200
@@ -19,20 +19,20 @@
 Name:           libvpd2
 Version:        2.1.3
 Release:        0
-BuildRequires:  gcc-c++
-BuildRequires:  libtool
-BuildRequires:  pkg-config
-BuildRequires:  sqlite3-devel
-BuildRequires:  zlib-devel
 Summary:        VPD Database access library for lsvpd
 License:        LGPL-2.1+
 Group:          Development/Libraries/Other
 Url:            http://linux-diag.sourceforge.net/Lsvpd.html
-BuildRoot:      %{_tmppath}/%{name}-%{version}-build
 Source:         libvpd-%{version}.tar.bz2
 Source2:        baselibs.conf
 Patch0:         libvpd2-gcc47.patch
 Patch3:         libvpd.async.patch
+BuildRequires:  gcc-c++
+BuildRequires:  libtool
+BuildRequires:  pkg-config
+BuildRequires:  sqlite3-devel
+BuildRequires:  zlib-devel
+BuildRoot:      %{_tmppath}/%{name}-%{version}-build
 
 %description
 The libvpd_cxx package contains the classes that are used to access a

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

Reply via email to