lp:debian/experimental/protobuf

Related source package recipes

No recipes using this branch. (?)

Create packaging recipe

Related snap packages

Related bugs

Related blueprints

19. By Robert Edmonds on 2014-09-05

Compile the Java bindings only on architecture-independent builds.

18. By Robert Edmonds on 2014-09-02

* New upstream release.
* Upload to experimental.
* Switch to dh sequencer in debian/rules.
* Bump ABI version from 8 to 9.
* Drop all patches from debian/patches/:
  - arm_optimization.diff
      (Appears to be no longer needed.)
  - disable-setuptools-download.diff
      (Disable ez_setup entirely, rather than disabling the downloader
      component inside ez_setup.)
  - fix-ftbfs-gcc4.7-kfreebsd.patch
      (Fixed upstream.)
  - fix-ftbfs-upstream-issue-488.patch
      (Fixed upstream.)
  - revert_upstream_issue_388_about_rpath.diff
      (Fixed upstream.)
* Use dh-autoreconf. (Closes: #725976.)
* Enable the new C++-based Python extension module shipped in 2.6.0.
  See /usr/share/doc/python-protobuf/README.Debian for details.

17. By Robert Edmonds on 2014-02-03

* Revert debian/patches/fix-ftbfs-upstream-issue-488.patch to use the
  version of this patch from 2.5.0-5.
* Build-Depend on g++ >= 4:4.7 to ensure that the *default* compiler is new
  enough to support the gcc __atomic*() built-ins.

16. By Robert Edmonds on 2014-01-26

* Use a different approach to fixing the FTBFS caused by upstream bug #488.
* Revert the Build-Depends on a specific gcc/g++ version.

15. By Robert Edmonds on 2014-01-12

* Rewrite the platform detection logic in .../platform-macros.h to be more
  tolerant of all Debian architectures.
* Switch from autotools-dev to dh-autoreconf.

14. By Robert Edmonds on 2014-01-11

* Fix FTBFS on mips, due to missing detection of that architecture in
  .../platform-macros.h.
* Fix FTBFS on ia64, powerpc, and sparc, where the default gcc version is
  too old to compile the new __atomic*() intrinsics, by Build-Depending on
  gcc-4.8, g++-4.8.

13. By Robert Edmonds on 2013-10-19

* Fix FTBFS on "unsupported" architectures due to upstream issue 488:
  - https://code.google.com/p/protobuf/issues/detail?id=488
  Patch from Stanislav Ochotnicky (Red Hat).

12. By Robert Edmonds on 2013-10-12

[ Micah Anderson ]
* New upstream version. (Closes: #704731.)
* Update debian/watch.
* Refresh patches.

[ Colin Watson ]
* Use the autotools-dev dh addon to update config.guess/config.sub for
  arm64. (Closes: #725976.)

[ Steve Langasek ]
* Don't recommend protobuf-compiler from the bindings, it's not used and
  this doesn't need to be pulled in at runtime. (Closes: #703628.)
* Mark protobuf-compiler Multi-Arch: foreign; the output of this command
  is architecture-independent source, we don't need the version of the
  compiler to match the target arch.
* Bump to debhelper compat 9, so that our libs get installed to the
  multiarch locations.
* Mark the library packages Multi-Arch: same.
* Fix debian/rules to support cross-building of the python bindings.
* Build-depend on libpython-dev, not python-dev, for cross-build
  compatibility.
* (Closes: #726083.)

[ Robert S. Edmonds ]
* Upload to experimental.
* Bump ABI version from 7 to 8.
* Bump Standards-Version to 3.9.4.
* Convert from python-support to dh-python.
* Drop support for python2.6.
* python-protobuf: switch back to the pure Python implementation, as
  upstream appears to no longer be maintaining the current C++ based Python
  binding. See the following upstream issues for details:
  - https://code.google.com/p/protobuf/issues/detail?id=434
  - https://code.google.com/p/protobuf/issues/detail?id=503

11. By Iustin Pop on 2011-02-16

* New upstream version, uploading to experimental due to Python changes
* Fix "Missing depends on zlib1g-dev", thanks Fernando Tarlá Cardoso Lemos
  (Closes: #608670)
* Re-enable parallel builds, but only for the C++ sources/tests
* Enable the C++-based implementation for the Python bindings

10. By Iustin Pop on 2010-08-18

* Thanks to Peter Palfrader for finding the two bugs below:
* Disable setuptools auto-download in case of wrong dependencies, and
  fix the current dependency version (Closes: #593269)
* Fix the python cleanup rule, by always running the individual steps
  (Closes: #593268)