This bug was fixed in the package google-mock - 1.6.0+svn437-0ubuntu1

---------------
google-mock (1.6.0+svn437-0ubuntu1) saucy; urgency=low

  [ Matthias Klose ]
  * Merge with Debian, discard the Ubuntu changes.
  * Build using dh_python2.

  [ Didier Roche ]
  * New upstream snapshot (LP: #1185265)
  * Remove explicit build with external gtest (not anymore supported upstream)
  * Add debian/patches/include_system_path.patch to reinclude system path in
    mock
  * Include python build-dep as built with dh_python2
  * Add missing cmake build-dep
  * Ship CMakeLists.txt as a convenience for other packages using gmock and
    cmake and update debian/README.Debian with an example to use it
  * Ship gtest internal version with google-mock, as the snapshot doesn't work
    with the system old gtest, ignore during installation some project files
  * debian/patches/support_gcc_4.7.patch: support older gcc with C++11 (disabled
    for now)
 -- Didier Roche <[email protected]>   Thu, 04 Jul 2013 09:54:08 +0200

** Changed in: google-mock (Ubuntu)
       Status: In Progress => Fix Released

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to unity in Ubuntu.
Matching subscriptions: dp-unity
https://bugs.launchpad.net/bugs/1185265

Title:
  please stop shipping pre-build google-mock, instead all reverse-
  depends should compile their own google-mock

Status in Mir:
  In Progress
Status in “google-mock” package in Ubuntu:
  Fix Released
Status in “libusermetrics” package in Ubuntu:
  In Progress
Status in “location-service” package in Ubuntu:
  In Progress
Status in “nux” package in Ubuntu:
  In Progress
Status in “rlvm” package in Ubuntu:
  Invalid
Status in “unity” package in Ubuntu:
  In Progress

Bug description:
  Package: google-mock
  Version: 1.6.0-0ubuntu3

  This package represents significant and unwarranted deviation from the
  Debian package.  For example, it does cause FTBFS with aptitude.

  
  Use of precompiled libgmock
  ---------------------------

  The Google C++ Mocking Framework uses conditional compilation for some
  things.  Because of the C++ "One Definition Rule", gmock must be
  compiled with exactly the same flags as your C++ code under test.
  Because this is hard to manage, upstream no longer recommends using
  precompiled libraries.

  
  google-mock (1.6.0-1) unstable; urgency=low

    * New upstream release (closes: #631676)

      As of this version upstream does not recommend using precompiled libraries
      so the package now only contains sources and includes. See the
      README.Debian file for instructions on how to build your own gmock
      library.

To manage notifications about this bug go to:
https://bugs.launchpad.net/mir/+bug/1185265/+subscriptions

-- 
Mailing list: https://launchpad.net/~desktop-packages
Post to     : [email protected]
Unsubscribe : https://launchpad.net/~desktop-packages
More help   : https://help.launchpad.net/ListHelp

Reply via email to