Hello community,

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

Package is "libqt5-qtsensors"

Changes:
--------
--- /work/SRC/openSUSE:Factory/libqt5-qtsensors/libqt5-qtsensors.changes        
2014-05-22 06:39:01.000000000 +0200
+++ /work/SRC/openSUSE:Factory/.libqt5-qtsensors.new/libqt5-qtsensors.changes   
2014-06-04 18:38:38.000000000 +0200
@@ -1,0 +2,6 @@
+Mon Jun  2 19:39:02 UTC 2014 - [email protected]
+
+- Add baselibs.conf
+- Make private headers noarch
+
+-------------------------------------------------------------------

New:
----
  baselibs.conf

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

Other differences:
------------------
++++++ libqt5-qtsensors.spec ++++++
--- /var/tmp/diff_new_pack.P12YqX/_old  2014-06-04 18:38:39.000000000 +0200
+++ /var/tmp/diff_new_pack.P12YqX/_new  2014-06-04 18:38:39.000000000 +0200
@@ -36,6 +36,7 @@
 %define tar_version qtsensors-opensource-src-%{real_version}
 %endif
 Source:         %{tar_version}.tar.xz
+Source1:        baselibs.conf
 BuildRequires:  fdupes
 BuildRequires:  libQt5Core-private-headers-devel >= %{version}
 BuildRequires:  pkgconfig(Qt5Core) >= %{version}
@@ -78,6 +79,7 @@
 %package private-headers-devel
 Summary:        Non-ABI stable experimental API
 Group:          Development/Libraries/C and C++
+BuildArch:      noarch
 Requires:       %{name}-devel = %{version}
 Requires:       libQt5Core-private-headers-devel >= %{version}
 Provides:       libQt5Sensors-private-headers-devel = %{version}

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

Reply via email to