Daily package recipe fails with build error; works fine locally and on Debian's buildds

Asked by Chris Conway

The recipe https://code.launchpad.net/~cconway/+recipe/cvc3-packaging-daily fails for both quantal and precise. The failure is due to the upstream configure script failing to detect libgmp even though libgmp-dev is installed as a build dependency. Here's a failed build log:

https://launchpadlibrarian.net/113299159/buildlog.txt.gz

And here's a successful build log for the exact same package from Debian unstable:

https://buildd.debian.org/status/fetch.php?pkg=cvc3&arch=i386&ver=2.4.1-4&stamp=1345317447

Is there something going on the -dev packages that would confuse the upstream build scripts?

Question information

Language:
English Edit question
Status:
Solved
For:
Launchpad itself Edit question
Assignee:
Jelmer Vernooij Edit question
Solved by:
Jelmer Vernooij
Solved:
Last query:
Last reply:
Revision history for this message
Jelmer Vernooij (jelmer) said :
#1

Hello,

This seems like it would be an issue with the archive rather than specifically in Launchpad.

Have you tried building the package locally on quantal or precise?

Revision history for this message
Chris Conway (cconway) said :
#2

I had tried building the package locally, but only on amd64. It fails for me (in the same way as on the buildds) when I use "pbuilder-dist precise i386". So apparently this is a bug in libgmp-dev on i386. The package version on precise/quantal is 2:5.0.2+dfsg-2ubuntu1 and in Debian testing/unstable it's 2:5.0.5+dfsg-2. I'm a bit curious how the versions of my package (cvc3) in the precise/quantal repos managed to get built!

Can you point me towards the right place to report this issue? It seems like it would be good to get the newer version of GMP from Debian testing into quantal before the release. The newer version of CVC3 would also be good. The version in quantal has release-critical bugs.

Revision history for this message
Best Jelmer Vernooij (jelmer) said :
#3

The ubuntu bug tracker for the cvc3 package is probably the right place.

https://bugs.launchpad.net/ubuntu/+source/cvc3/+filebug

Since the package is in universe, you might also have to ping a MOTU to look at the bug report.

Revision history for this message
Chris Conway (cconway) said :
#4

Thanks Jelmer Vernooij, that solved my question.