Package: google-mock Version: 1.7.0-4 Severity: normal Tags: upstream Dear Maintainer,
The google-mock_1.7.0.orig.tar.bz2 differs significantly from official release of googlemock at code.google.com/p/googlemock I noticed this because a project I was building (which included it's own copy of google-mock) failed to find expected class declarations in header files. The problem was that the headers in /usr/include/gmock were being used, which currently differs from upstream. The google-mock_1.7.0.orig.tar.bz2 tarball seems to come from before 1.7.0 release, and some data structures have been changed. -- System Information: Debian Release: jessie/sid APT prefers trusty-updates APT policy: (500, 'trusty-updates'), (500, 'trusty-security'), (500, 'trusty') Architecture: amd64 (x86_64) Kernel: Linux 3.13.0-27-generic (SMP w/4 CPU cores) Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Versions of packages google-mock depends on: ii libgtest-dev 1.7.0-3~ubuntu14.04.1~ppa1 pn python:any <none> google-mock recommends no packages. google-mock suggests no packages. -- no debconf information -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
