Hello community,

here is the log from the commit of package libqt5-qtsvg for openSUSE:Factory 
checked in at 2014-06-04 18:38:41
++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++
Comparing /work/SRC/openSUSE:Factory/libqt5-qtsvg (Old)
 and      /work/SRC/openSUSE:Factory/.libqt5-qtsvg.new (New)
++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++

Package is "libqt5-qtsvg"

Changes:
--------
--- /work/SRC/openSUSE:Factory/libqt5-qtsvg/libqt5-qtsvg.changes        
2014-05-22 06:39:04.000000000 +0200
+++ /work/SRC/openSUSE:Factory/.libqt5-qtsvg.new/libqt5-qtsvg.changes   
2014-06-04 18:38:42.000000000 +0200
@@ -1,0 +2,6 @@
+Mon Jun  2 10:20:41 UTC 2014 - [email protected]
+
+- Add baselibs.conf
+- Make private headers noarch
+
+-------------------------------------------------------------------

New:
----
  baselibs.conf

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

Other differences:
------------------
++++++ libqt5-qtsvg.spec ++++++
--- /var/tmp/diff_new_pack.vVpR2S/_old  2014-06-04 18:38:45.000000000 +0200
+++ /var/tmp/diff_new_pack.vVpR2S/_new  2014-06-04 18:38:45.000000000 +0200
@@ -36,6 +36,7 @@
 %define tar_version qtsvg-opensource-src-%{real_version}
 %endif
 Source:         %{tar_version}.tar.xz
+Source1:        baselibs.conf
 BuildRequires:  libQt5Core-private-headers-devel >= %{version}
 BuildRequires:  libQt5Gui-private-headers-devel >= %{version}
 BuildRequires:  libQt5Widgets-private-headers-devel >= %{version}
@@ -84,6 +85,7 @@
 %package private-headers-devel
 Summary:        Non-ABI stable experimental API
 Group:          Development/Libraries/C and C++
+BuildArch:      noarch
 Requires:       %{name}-devel = %{version}
 Provides:       libQt5Svg-private-headers-devel = %{version}
 Obsoletes:      libQt5Svg-private-headers-devel < %{version}

++++++ baselibs.conf ++++++
libQt5Svg5
libqt5-qtsvg-devel
        requires "libQt5Svg5-<targettype> = <version>"--
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]

Reply via email to