Hello community,

here is the log from the commit of package libjingle for openSUSE:Factory
checked in at Fri May 27 11:55:47 CEST 2011.



--------
--- libjingle/libjingle.changes 2011-04-28 15:04:42.000000000 +0200
+++ /mounts/work_src_done/STABLE/libjingle/libjingle.changes    2011-05-22 
12:13:27.000000000 +0200
@@ -1,0 +2,5 @@
+Sun May 22 10:12:17 UTC 2011 - [email protected]
+
+- Added 32 bit libs to the build
+
+-------------------------------------------------------------------

calling whatdependson for head-i586


New:
----
  baselibs.conf

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

Other differences:
------------------
++++++ libjingle.spec ++++++
--- /var/tmp/diff_new_pack.jCdUuj/_old  2011-05-27 11:55:23.000000000 +0200
+++ /var/tmp/diff_new_pack.jCdUuj/_new  2011-05-27 11:55:23.000000000 +0200
@@ -22,13 +22,14 @@
 Url:            http://cgit.collabora.co.uk/git/libjingle.git/
 BuildRequires:  gcc-c++ libexpat-devel openssl-devel pkg-config
 Version:        0.3.12
-Release:        14
+Release:        16
 License:        BSD3c(or similar)
 BuildRoot:      %{_tmppath}/%{name}-%{version}-build
 %define debug_package_requires libjingle-0_3-0 = %{version}-%{release}
 Group:          Productivity/Networking/Other
 Summary:        Library for Peer-to-Peer Applications
-Source:         
http://farsight.freedesktop.org/releases/libjingle/%{name}-%{version}.tar.bz2
+Source0:        
http://farsight.freedesktop.org/releases/libjingle/%{name}-%{version}.tar.bz2
+Source1:        baselibs.conf
 # PATCH-FIX-UPSTREAM libjingle-gcc44.patch [email protected] -- Sent to 
upstream by mail
 Patch0:         libjingle-gcc44.patch
 # PATCH-FIX-UPSTREAM libjingle-0.3.12-openssl.patch [email protected] -- Fix build 
with openssl 1.0, patch from fedora 12. Sent to upstream by mail.

++++++ baselibs.conf ++++++
libjingle-0_3-0

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



Remember to have fun...

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

Reply via email to