desktop-packages team mailing list archive

[Hans Joachim Desserud <1436661@xxxxxxxxxxxxxxxxxx>]

Thanks for reporting.

I found a corresponding Debian bug report which might shed some light on
things. It looks like gtest must be compiled with the exact same flags
as when you build/run your tests. See http://bugs.debian.org/cgi-
bin/bugreport.cgi?bug=726021 for more information.

** Bug watch added: Debian Bug tracker #726021
   http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=726021

** Also affects: gtest (Debian) via
   http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=726021
   Importance: Unknown
       Status: Unknown

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

Title:
  Inconsistent with Ubuntu package management

Status in gtest package in Ubuntu:
  Confirmed
Status in gtest package in Debian:
  Unknown

Bug description:
  I appreciate that some people prefer the notion of compiling
  everything from source, like on Gentoo Linux, but on Ubuntu can we
  please follow the standard packaging practice and have binaries in
  binary packages?

  This seems to be the package creation workflow for this package:

  Compile Source Package => Binary Package => Source that must be
  compiled by the user

  If it is felt that it is absolutely mandatory to not provide binaries
  then why not provide a 'proper' source package that is consistent with
  other source packages. That is to say, one which allows you to
  actually build the real binary package.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gtest/+bug/1436661/+subscriptions