* Non-maintainer upload.
* The previous upload fixed google-mock for its own testsuite, but not for
client projects. Backport a patch from an upstream issue to modify some
functions to not return NULL, working around the problem caused for
google-mock itself and for its clients. (Closes: #833449) (LP: #1609793)
* This means we don't need -fno-delete-null-pointer-checks any more, so
remove that workaround.
-- Iain Lane <email address hidden> Thu, 04 Aug 2016 16:14:17 +0100
This bug was fixed in the package google-mock - 1.7.0-18092013- 2.1~build1
--------------- 18092013- 2.1~build1) yakkety; urgency=medium
google-mock (1.7.0-
* Upload NMU from DELAYED to Ubuntu (build1 to ensure this is autosynced the
next time)
google-mock (1.7.0- 18092013- 2.1) unstable; urgency=medium
* Non-maintainer upload. null-pointer- checks any more, so
* The previous upload fixed google-mock for its own testsuite, but not for
client projects. Backport a patch from an upstream issue to modify some
functions to not return NULL, working around the problem caused for
google-mock itself and for its clients. (Closes: #833449) (LP: #1609793)
* This means we don't need -fno-delete-
remove that workaround.
-- Iain Lane <email address hidden> Thu, 04 Aug 2016 16:14:17 +0100