Hello community,

here is the log from the commit of package protobuf for openSUSE:Factory 
checked in at 2012-01-04 07:29:57
++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++
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        2011-09-23 
12:41:59.000000000 +0200
+++ /work/SRC/openSUSE:Factory/.protobuf.new/protobuf.changes   2012-01-04 
07:30:01.000000000 +0100
@@ -1,0 +2,26 @@
+Wed Dec 21 09:47:32 UTC 2011 - [email protected]
+
+- remove %release from requires
+
+-------------------------------------------------------------------
+Wed Oct 12 15:46:14 MSD 2011 - [email protected]
+
+- Update to Protobuf 2.4.1:
+ C++
+  * Fixed the frendship problem for old compilers to make the library now gcc 3
+    compatible again.
+  * Fixed vcprojects/extract_includes.bat to extract compiler/plugin.h.
+
+  Java
+  * Removed usages of JDK 1.6 only features to make the library now JDK 1.5
+    compatible again.
+  * Fixed a bug about negative enum values.
+  * serialVersionUID is now defined in generated messages for java serializing.
+  * Fixed protoc to use java.lang.Object, which makes "Object" now a valid
+    message name again.
+
+  Python
+  * Experimental C++ implementation now requires C++ protobuf library 
installed.
+    See the README.txt in the python directory for details.
+
+-------------------------------------------------------------------

Old:
----
  protobuf-2.3.0.tar.bz2
  protobuf-setuptools-2.2.0.patch

New:
----
  protobuf-2.4.1.tar.bz2
  protobuf-setuptools-2.4.1.patch

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

Other differences:
------------------
++++++ protobuf.spec ++++++
--- /var/tmp/diff_new_pack.TQoZ9m/_old  2012-01-04 07:30:02.000000000 +0100
+++ /var/tmp/diff_new_pack.TQoZ9m/_new  2012-01-04 07:30:02.000000000 +0100
@@ -15,9 +15,7 @@
 # Please submit bugfixes or comments via http://bugs.opensuse.org/
 #
 
-# norootforbuild
-
-%define soname 6
+%define soname 7
 
 %bcond_without check
 
@@ -35,14 +33,14 @@
 
 Name:           protobuf
 Summary:        Protocol Buffers - Google's data interchange format
-Version:        2.3.0
-Release:        9
-License:        New BSD License
+License:        BSD-3-Clause
 Group:          Development/Libraries/C and C++
+Version:        2.4.1
+Release:        0
 Url:            http://code.google.com/p/protobuf/ 
 Source0:        http://protobuf.googlecode.com/files/%{name}-%{version}.tar.bz2
 Source1:        manifest.txt.in
-Patch0:         protobuf-setuptools-2.2.0.patch
+Patch0:         protobuf-setuptools-2.4.1.patch
 BuildRoot:      %{_tmppath}/%{name}-%{version}-build
 BuildRequires:  gcc-c++
 %if 0%{?suse_version} > 1010
@@ -52,7 +50,9 @@
 BuildRequires:  java-devel >= 1.6.0
 %endif
 %if %{with protobuf_python}
-BuildRequires:  python python-devel python-setuptools
+BuildRequires:  python
+BuildRequires:  python-devel
+BuildRequires:  python-setuptools
 %endif
 
 %description
@@ -61,8 +61,6 @@
 RPC protocols and file formats. 
 
 %package -n libprotobuf%{soname}
-
-
 Summary:        Protocol Buffers - Google's data interchange format
 Group:          System/Libraries
 
@@ -72,8 +70,6 @@
 RPC protocols and file formats. 
 
 %package -n libprotoc%{soname}
-
-
 Summary:        Protocol Buffers - Google's data interchange format
 Group:          System/Libraries
 
@@ -83,8 +79,6 @@
 RPC protocols and file formats. 
 
 %package -n libprotobuf-lite%{soname}
-
-
 Summary:        Protocol Buffers - Google's data interchange format
 Group:          System/Libraries
 
@@ -94,12 +88,11 @@
 RPC protocols and file formats. 
 
 %package devel
-License:        New BSD License
-
 Summary:        Header files, libraries and development documentation for 
%{name}
 Group:          Development/Libraries/C and C++
-Requires:       gcc-c++
-Provides:       libprotobuf-devel = %version-%release
+Requires:       gcc-c++ libprotobuf%{soname} = %version 
libprotobuf-lite%{soname}
+Provides:       libprotobuf-devel = %version
+BuildRequires:  pkg-config
 
 %description devel
 Development files for Google Protocol Buffers
@@ -107,11 +100,9 @@
 %if %{with protobuf_java}
 
 %package -n %{name}-java
-
-
-Group:          Development/Libraries/Java
 Requires:       java >= 1.6.0
 Summary:        Java Bindings for Google Protocol Buffers
+Group:          Development/Libraries/Java
 
 %description -n %{name}-java
 This package contains the Java bindings for Google Protocol Buffers.
@@ -121,14 +112,13 @@
 
 %package -n python-%{name}
 
-
-Group:          Development/Libraries/Python
 %if 0%{?suse_version}
 %py_requires
 %else
 Requires:       python
 %endif
 Summary:        Python Bindings for Google Protocol Buffers
+Group:          Development/Libraries/Python
 
 %description -n python-%{name}
 This package contains the Python bindings for Google Protocol Buffers.

++++++ baselibs.conf ++++++
--- /var/tmp/diff_new_pack.TQoZ9m/_old  2012-01-04 07:30:02.000000000 +0100
+++ /var/tmp/diff_new_pack.TQoZ9m/_new  2012-01-04 07:30:02.000000000 +0100
@@ -1,3 +1,3 @@
-libprotobuf6
-libprotobuf-lite6
-libprotoc6
+libprotobuf7
+libprotobuf-lite7
+libprotoc7

++++++ protobuf-2.3.0.tar.bz2 -> protobuf-2.4.1.tar.bz2 ++++++
++++ 76519 lines of diff (skipped)

++++++ protobuf-setuptools-2.2.0.patch -> protobuf-setuptools-2.4.1.patch ++++++
--- /work/SRC/openSUSE:Factory/protobuf/protobuf-setuptools-2.2.0.patch 
2011-09-23 12:41:59.000000000 +0200
+++ /work/SRC/openSUSE:Factory/.protobuf.new/protobuf-setuptools-2.4.1.patch    
2012-01-04 07:30:01.000000000 +0100
@@ -5,7 +5,7 @@
  This file can also be run as a script to install or upgrade setuptools.
  """
  import sys
--DEFAULT_VERSION = "0.6c9"
+-DEFAULT_VERSION = "0.6c11"
 +DEFAULT_VERSION = "0.6c8"
  DEFAULT_URL     = "http://pypi.python.org/packages/%s/s/setuptools/"; % 
sys.version[:3]
  

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

Reply via email to