Hello community,

here is the log from the commit of package telepathy-farstream for 
openSUSE:Factory checked in at 2012-03-29 19:03:05
++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++
Comparing /work/SRC/openSUSE:Factory/telepathy-farstream (Old)
 and      /work/SRC/openSUSE:Factory/.telepathy-farstream.new (New)
++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++

Package is "telepathy-farstream", Maintainer is ""

Changes:
--------
--- /work/SRC/openSUSE:Factory/telepathy-farstream/telepathy-farstream.changes  
2012-03-23 12:06:39.000000000 +0100
+++ 
/work/SRC/openSUSE:Factory/.telepathy-farstream.new/telepathy-farstream.changes 
    2012-03-29 19:03:11.000000000 +0200
@@ -1,0 +2,25 @@
+Tue Mar 20 22:28:11 UTC 2012 - [email protected]
+
+- Update to version 0.2.3:
+  + Fix various bugs.
+  + Improve debug messages.
+  + Improve GI annotations.
+  + Use the generic marshallers.
+
+-------------------------------------------------------------------
+Fri Mar  9 09:48:27 UTC 2012 - [email protected]
+
+- Update to version 0.2.2:
+  + Allow an Endpoint to be removed so as it work with Rakia call
+    transfers
+  + Ignore glib post-2.26 deprecations
+  + added a tf_channel_new_finish() function
+  + Misc bug fixes
+- Add explicit pkgconfig(glib-2.0) and pkgconfig(gobject-2.0)
+  BuildRequires. They are being pulled in by others already, but
+  having explicit BuildRequires allows us to require them
+  versioned.
+- Rename telepathy-farstream1 to telepathy-farstream2, following
+  the upstream soname change.
+
+-------------------------------------------------------------------

Old:
----
  telepathy-farstream-0.2.1.tar.gz

New:
----
  telepathy-farstream-0.2.3.tar.gz

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

Other differences:
------------------
++++++ telepathy-farstream.spec ++++++
--- /var/tmp/diff_new_pack.LWXYwW/_old  2012-03-29 19:03:15.000000000 +0200
+++ /var/tmp/diff_new_pack.LWXYwW/_new  2012-03-29 19:03:15.000000000 +0200
@@ -18,7 +18,7 @@
 
 
 Name:           telepathy-farstream
-Version:        0.2.1
+Version:        0.2.3
 Release:        1
 License:        LGPL-2.1+
 Summary:        Telepathy library to handle Call channels
@@ -29,6 +29,8 @@
 BuildRequires:  pkgconfig(dbus-glib-1)
 BuildRequires:  pkgconfig(farstream-0.1) >= 0.1.0
 BuildRequires:  pkgconfig(gio-2.0)
+BuildRequires:  pkgconfig(glib-2.0) >= 2.30
+BuildRequires:  pkgconfig(gobject-2.0) >= 2.30
 BuildRequires:  pkgconfig(gst-python-0.10)
 BuildRequires:  pkgconfig(pygobject-2.0)
 BuildRequires:  pkgconfig(telepathy-glib) >= 0.17.5
@@ -37,11 +39,11 @@
 Telepathy Farstream is a Telepathy client library that uses Farsight2
 to handle Call channels.
 
-%package -n libtelepathy-farstream1
+%package -n libtelepathy-farstream2
 Summary:        Telepathy library to handle Call channels
 Group:          System/Libraries
 
-%description -n libtelepathy-farstream1
+%description -n libtelepathy-farstream2
 Telepathy Farstream is a Telepathy client library that uses Farsight2
 to handle Call channels.
 
@@ -56,7 +58,7 @@
 %package devel
 Summary:        Telepathy library to handle Call channels -- Development Files
 Group:          Development/Languages/C and C++
-Requires:       libtelepathy-farstream1 = %{version}
+Requires:       libtelepathy-farstream2 = %{version}
 
 %description devel
 Telepathy Farstream is a Telepathy client library that uses Farsight2
@@ -76,11 +78,11 @@
 %clean
 rm -rf %{buildroot}
 
-%post -n libtelepathy-farstream1 -p /sbin/ldconfig
+%post -n libtelepathy-farstream2 -p /sbin/ldconfig
 
-%postun -n libtelepathy-farstream1 -p /sbin/ldconfig
+%postun -n libtelepathy-farstream2 -p /sbin/ldconfig
 
-%files -n libtelepathy-farstream1
+%files -n libtelepathy-farstream2
 %defattr(-, root, root)
 %doc ChangeLog COPYING NEWS README
 %{_libdir}/libtelepathy-farstream.so.*

++++++ telepathy-farstream-0.2.1.tar.gz -> telepathy-farstream-0.2.3.tar.gz 
++++++
++++ 10497 lines of diff (skipped)

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

Reply via email to