Hello community,

here is the log from the commit of package protobuf for openSUSE:Factory 
checked in at 2012-05-22 08:18:03
++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++
Comparing /work/SRC/openSUSE:Factory/protobuf (Old)
 and      /work/SRC/openSUSE:Factory/.protobuf.new (New)
++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++

Package is "protobuf", Maintainer is ""

Changes:
--------
--- /work/SRC/openSUSE:Factory/protobuf/protobuf.changes        2012-04-18 
12:35:08.000000000 +0200
+++ /work/SRC/openSUSE:Factory/.protobuf.new/protobuf.changes   2012-05-22 
08:18:05.000000000 +0200
@@ -1,0 +2,6 @@
+Sat May 19 18:25:52 UTC 2012 - [email protected]
+
+- BuildRequire zlib-devel otherwise gzip_stream is not built 
+  thus breaking newer releases of mosh.
+
+-------------------------------------------------------------------

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

Other differences:
------------------
++++++ protobuf.spec ++++++
--- /var/tmp/diff_new_pack.xOayMt/_old  2012-05-22 08:18:08.000000000 +0200
+++ /var/tmp/diff_new_pack.xOayMt/_new  2012-05-22 08:18:08.000000000 +0200
@@ -47,8 +47,9 @@
 Patch0:         protobuf-setuptools-2.4.1.patch
 BuildRoot:      %{_tmppath}/%{name}-%{version}-build
 # Needed to rebootstrap with gtest 1.5.0
-BuildRequires:  libtool
 BuildRequires:  gcc-c++
+BuildRequires:  libtool
+BuildRequires:  zlib-devel
 %if 0%{?suse_version} > 1010
 BuildRequires:  fdupes
 %endif
@@ -96,8 +97,11 @@
 %package devel
 Summary:        Header files, libraries and development documentation for 
%{name}
 Group:          Development/Libraries/C and C++
-Requires:       gcc-c++ libprotobuf%{soname} = %version 
libprotobuf-lite%{soname}
+Requires:       gcc-c++
+Requires:       libprotobuf%{soname} = %version
+Requires:       libprotobuf-lite%{soname}
 Provides:       libprotobuf-devel = %version
+Requires:       zlib-devel
 BuildRequires:  pkg-config
 
 %description devel

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

Reply via email to