Debian Bug report logs - #716828
google-mock: incompatible with current libgtest-dev

Toggle useless messages

Message #5 received at submit@bugs.debian.org (full text, mbox, reply):

From: Andreas Barth <aba@ayous.org>

To: submit@bugs.debian.org

Subject: aptitude FTBFS with missing google-mock

Date: Sat, 13 Jul 2013 11:34:28 +0200

Package: aptitude
Version: 0.6.8.2-1
Severity: serious

Hi,

re-building aptitude in plain sid (both on mipsel and amd64) ends
with:

checking for boost/weak_ptr.hpp... yes
checking for boostlib >= 1.20.0... yes
checking whether the Boost::IOStreams library is available... yes
checking for main in -lboost_iostreams-mt... yes
checking the calling convertion of boost::fusion::fold... State first, then value
checking the name of the runtime library for Boost.Test... "-lboost_unit_test_framework"
configure: error: Can't figure out where Google Mock lives; either install the google-mock package or place the library in the link path
dh_auto_configure: ../configure --build=x86_64-linux-gnu --prefix=/usr --includedir=${prefix}/include --mandir=${prefix}/share/man --infodir=${prefix}/share/info --sysconfdir=/etc --localstatedir=/var --libdir=${prefix}/lib/x86_64-linux-gnu --libexecdir=${prefix}/lib/x86_64-linux-gnu --disable-maintainer-mode --disable-dependency-tracking --htmldir=${docdir}/html --program-transform=s&aptitude$&aptitude-curses& returned exit code 1
make[1]: *** [override_dh_auto_configure] Error 2
checking how to link gmock... make[1]: Leaving directory `/«PKGBUILDDIR»'
make: *** [build-arch] Error 2
dpkg-buildpackage: error: debian/rules build-arch gave error exit status 2
────────────────────────────────────────────────────────────────────────────────
Build finished at 20130713-0931



Andi

Message #14 received at 716828-quiet@bugs.debian.org (full text, mbox, reply):

From: Daniel Hartwig <mandyke@gmail.com>

To: Lifeng Sun <lifongsun@gmail.com>, 708812@bugs.debian.org

Cc: 716828-quiet@bugs.debian.org

Subject: Re: Bug#708812: [aptitude] aptitude segfaults upon being called.

Date: Thu, 25 Jul 2013 23:42:19 +0800

Control: block 716828 by 716944

On 24 July 2013 19:03, Lifeng Sun <lifongsun@gmail.com> wrote:
> [aptitude] suffers another FTBFS bug [6].

The current versions of google-mock and gtest in unstable are
incompatible with each other.  As google-mock relies on gtest,
aptitude will continue to FTBFS until that situation is resolved.  See
<http://bugs.debian.org/716944>.

There are also issues with gcc4.8 and boost that are fixed in git, but
waiting for boost1.54 to become the default (or patched boost1.49 and
boost1.53). <http://bugs.debian.org/701243>.

>
> Is there any plan to fix these bugs? I can help to fix it on mipsel.
>

Once the blocking issues are resolved it will be no problem to get
aptitude building again.

Message #19 received at 716828@bugs.debian.org (full text, mbox, reply):

From: Fredrik Hallenberg <megahallon@gmail.com>

To: Andreas Barth <aba@ayous.org>

Cc: hallon@debian.org, 716944@bugs.debian.org, 716828@bugs.debian.org, 708812@bugs.debian.org

Subject: Re: Bug#716944: google-mock: please upload r437 snapshot to syncronize with recent gtest snapshot

Date: Sat, 27 Jul 2013 17:47:29 +0200

[Message part 1 (text/plain, inline)]

Sorry for not responding on this, I had planned to take a look at it next
week. Feel free to upload your fixed package.


On Sat, Jul 27, 2013 at 5:41 PM, Andreas Barth <aba@ayous.org> wrote:

> severity 716944 serious
> tag 716828 + patch
> tag 708812 + patch
> thanks
>
> * Daniel Hartwig (mandyke@gmail.com) [130727 15:34]:
> > gtest is recently bumped to 1.7.0~svn20130629-2 [1].  The 1.6.0
> > release of googlemock is incompatible with this, though r437 [2] is.
> > Please upload that version to keep the packages functional.
> >
> > I appreciate that you do not use the embedded copy of gtest, so let us
> > keep these syncronized.
>
>
> I built a package of google-mock based on the current svn snapshot.
> Using that, I can confirm that aptitude builds again (with patches
> from head to build with gcc-4.8, which is the default now on most
> arches), and in turn this resolves the issue that aptitude segfaults
> on mips* (see #708812). Resolving that would allow us to re-enable
> building experimental on mips*.
>
> Because of that, I adjusted the severity of this bug report. Also, if
> you want I could upload the fixed google-mock package now (or if you
> don't disagree, I would upload it next weekend to allow us to get our
> infrastructure back working again).
>
>
>
> Andi
>

[Message part 2 (text/html, inline)]

Message #24 received at 716828@bugs.debian.org (full text, mbox, reply):

From: Andreas Barth <aba@ayous.org>

To: hallon@debian.org, 716944@bugs.debian.org, 716828@bugs.debian.org, 708812@bugs.debian.org

Subject: Re: Bug#716944: google-mock: please upload r437 snapshot to syncronize with recent gtest snapshot

Date: Sat, 27 Jul 2013 17:41:56 +0200

severity 716944 serious
tag 716828 + patch
tag 708812 + patch
thanks

* Daniel Hartwig (mandyke@gmail.com) [130727 15:34]:
> gtest is recently bumped to 1.7.0~svn20130629-2 [1].  The 1.6.0
> release of googlemock is incompatible with this, though r437 [2] is.
> Please upload that version to keep the packages functional.
> 
> I appreciate that you do not use the embedded copy of gtest, so let us
> keep these syncronized.


I built a package of google-mock based on the current svn snapshot.
Using that, I can confirm that aptitude builds again (with patches
from head to build with gcc-4.8, which is the default now on most
arches), and in turn this resolves the issue that aptitude segfaults
on mips* (see #708812). Resolving that would allow us to re-enable
building experimental on mips*.

Because of that, I adjusted the severity of this bug report. Also, if
you want I could upload the fixed google-mock package now (or if you
don't disagree, I would upload it next weekend to allow us to get our
infrastructure back working again).



Andi

Message #31 received at 716828@bugs.debian.org (full text, mbox, reply):

From: Andreas Barth <aba@ayous.org>

To: Fredrik Hallenberg <megahallon@gmail.com>

Cc: hallon@debian.org, 716944@bugs.debian.org, 716828@bugs.debian.org, 708812@bugs.debian.org

Subject: Re: Bug#716944: google-mock: please upload r437 snapshot to syncronize with recent gtest snapshot

Date: Sat, 27 Jul 2013 21:00:40 +0200

* Fredrik Hallenberg (megahallon@gmail.com) [130727 17:47]:
>    Sorry for not responding on this, I had planned to take a look at it
>    next week. Feel free to upload your fixed package.

Thanks for your fast answer and for your permission to upload.

I however would like to ask you to check I didn't mess up anything
when you have time - especially as there are different patches in
debian/patches/ which are according to series not applied (same in
1.6.0, so it doesn't stop me from uploading, but these patches should
IMHO either be removed or applied, whatever makes sense).



Thanks,
Andi

Message #36 received at 716828-quiet@bugs.debian.org (full text, mbox, reply):

From: Andreas Barth <aba@ayous.org>

To: Daniel Hartwig <mandyke@gmail.com>, 708812@bugs.debian.org

Cc: Lifeng Sun <lifongsun@gmail.com>, 716828-quiet@bugs.debian.org

Subject: Re: Bug#708812: [aptitude] aptitude segfaults upon being called.

Date: Sat, 27 Jul 2013 23:41:14 +0200

Hi Daniel,

* Daniel Hartwig (mandyke@gmail.com) [130727 21:38]:
> On 24 July 2013 19:03, Lifeng Sun <lifongsun@gmail.com> wrote:
> > [aptitude] suffers another FTBFS bug [6].
> 
> The current versions of google-mock and gtest in unstable are
> incompatible with each other.  As google-mock relies on gtest,
> aptitude will continue to FTBFS until that situation is resolved.  See
> <http://bugs.debian.org/716944>.
> 
> There are also issues with gcc4.8 and boost that are fixed in git, but
> waiting for boost1.54 to become the default (or patched boost1.49 and
> boost1.53). <http://bugs.debian.org/701243>.
> 
> >
> > Is there any plan to fix these bugs? I can help to fix it on mipsel.
> >
> 
> Once the blocking issues are resolved it will be no problem to get
> aptitude building again.

As google-mock is now uploaded (and should be built on all
architectures within the next hours - already built on most), could
you please upload a new version of aptitude to unstable soon (the
current version plus the gcc-4.8-patches worked for me, and produced a
working aptitude on mipsel)?


Thanks,
Andi

Message #65 received at 716828-quiet@bugs.debian.org (full text, mbox, reply):

From: Andreas Barth <aba@ayous.org>

To: Daniel Hartwig <mandyke@gmail.com>, 708812@bugs.debian.org

Cc: Lifeng Sun <lifongsun@gmail.com>, 716828-quiet@bugs.debian.org

Subject: Re: Bug#708812: [aptitude] aptitude segfaults upon being called.

Date: Thu, 15 Aug 2013 15:20:00 +0200

* Andreas Barth (aba@ayous.org) [130815 13:18]:
> As google-mock is now uploaded (and should be built on all
> architectures within the next hours - already built on most), could
> you please upload a new version of aptitude to unstable soon (the
> current version plus the gcc-4.8-patches worked for me, and produced a
> working aptitude on mipsel)?

Hi Daniel,

can you please upload a new aptitude version? Or should I just NMU
aptitude with the required patches for gcc-4.8?


Andi

Send a report that this bug log contains spam.