Hello community,

here is the log from the commit of package libtirpc for openSUSE:Factory 
checked in at 2013-11-29 16:23:17
++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++
Comparing /work/SRC/openSUSE:Factory/libtirpc (Old)
 and      /work/SRC/openSUSE:Factory/.libtirpc.new (New)
++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++

Package is "libtirpc"

Changes:
--------
--- /work/SRC/openSUSE:Factory/libtirpc/libtirpc.changes        2013-10-02 
08:50:08.000000000 +0200
+++ /work/SRC/openSUSE:Factory/.libtirpc.new/libtirpc.changes   2013-11-29 
16:23:18.000000000 +0100
@@ -1,0 +2,13 @@
+Wed Nov 13 22:18:38 UTC 2013 - [email protected]
+
+- Use krb5 rather than gssglue to provide gss
+  access routines.
+  Both krb5 and gssglue provide routines of the same
+  name, and both can get linked into rpc.gssd, resulting
+  in some confusion.
+  Upstream support seems to be leaning heavily towards
+  avoiding libgssglue.  nfs-utils is built without it,
+  and best to build libtirpc without it.
+  (bnc#841788)
+
+-------------------------------------------------------------------

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

Other differences:
------------------
++++++ libtirpc.spec ++++++
--- /var/tmp/diff_new_pack.6VTcvf/_old  2013-11-29 16:23:18.000000000 +0100
+++ /var/tmp/diff_new_pack.6VTcvf/_new  2013-11-29 16:23:18.000000000 +0100
@@ -26,7 +26,7 @@
 Summary:        Transport Independent RPC Library
 License:        BSD-4-Clause
 Group:          System/Libraries
-BuildRequires:  libgssglue-devel
+BuildRequires:  krb5-devel
 BuildRequires:  libtool
 BuildRequires:  pkg-config
 Url:            http://sourceforge.net/projects/libtirpc/
@@ -84,8 +84,7 @@
 %configure --disable-static \
                --with-pic \
                --libdir=/%{_lib} \
-               --enable-gss \
-               --with-gssglue
+               --enable-gss
 %{__make} %{?_smp_mflags}
 
 %install

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

Reply via email to