Hello community,

here is the log from the commit of package libqt5-qtwebkit for openSUSE:13.1 
checked in at 2013-10-06 14:27:30
++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++
Comparing /work/SRC/openSUSE:13.1/libqt5-qtwebkit (Old)
 and      /work/SRC/openSUSE:13.1/.libqt5-qtwebkit.new (New)
++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++

Package is "libqt5-qtwebkit"

Changes:
--------
--- /work/SRC/openSUSE:13.1/libqt5-qtwebkit/libqt5-qtwebkit.changes     
2013-10-04 13:54:34.000000000 +0200
+++ /work/SRC/openSUSE:13.1/.libqt5-qtwebkit.new/libqt5-qtwebkit.changes        
2013-10-06 14:27:32.000000000 +0200
@@ -1,0 +2,6 @@
+Fri Oct  4 20:08:51 UTC 2013 - [email protected]
+
+- Drop the memory check from the spec, we are utilizing _constraints
+  for that. Also reduce the processor constraint to 4.
+
+-------------------------------------------------------------------

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

Other differences:
------------------
++++++ libqt5-qtwebkit.spec ++++++
--- /var/tmp/diff_new_pack.oitZV1/_old  2013-10-06 14:27:32.000000000 +0200
+++ /var/tmp/diff_new_pack.oitZV1/_new  2013-10-06 14:27:32.000000000 +0200
@@ -176,13 +176,6 @@
 export CFLAGS="$CFLAGS %{optflags} -DOPENSSL_LOAD_CONF"
 export LDFLAGS="$LDFLAGS -Wl,--reduce-memory-overheads -Wl,--no-keep-memory"
 
-free -m
-FREESPACE=`free -m | grep Mem | cut -c15-18`
-if [ "$FREESPACE" -lt 2000 ]; then
-echo not enough memory
-exit 1
-fi
-
 qmake
 make
 

++++++ _constraints ++++++
--- /var/tmp/diff_new_pack.oitZV1/_old  2013-10-06 14:27:32.000000000 +0200
+++ /var/tmp/diff_new_pack.oitZV1/_new  2013-10-06 14:27:32.000000000 +0200
@@ -1,8 +1,8 @@
 <constraints>
  <hardware>
-  <memory>
-   <size unit="G">5</size>
-  </memory>
-  <processors>8</processors>
+  <physicalmemory>
+   <size unit="G">4</size>
+  </physicalmemory>
+  <processors>4</processors>
  </hardware>
 </constraints>

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

Reply via email to