epiphany-extensions version 3.2.0-2 FTBFS on i386 in precise

[Andreas Moog]

This is a semi-automatic report based on the latest archive rebuild results [1].
Apologies if it reaches you in error.

Excerpt from the buildlog:

checking locale.h presence... yes
checking for locale.h... yes
checking for LC_MESSAGES... yes
checking libintl.h usability... yes
checking libintl.h presence... yes
checking for libintl.h... yes
checking for ngettext in libc... yes
checking for dgettext in libc... yes
checking for bind_textdomain_codeset... yes
checking for msgfmt... (cached) /usr/bin/msgfmt
checking for dcgettext... yes
checking if msgfmt accepts -c... yes
checking for gmsgfmt... (cached) /usr/bin/msgfmt
checking for xgettext... (cached) /usr/bin/xgettext
checking gnome-doc-utils >= 0.3.2... yes
checking whether epiphany-3.2 is available... no
configure: error: Epiphany API version 3.2 is required

This API version is used in the 3.2 stable series, and
the preceeding development series. Please ensure you have the appropriate
Epiphany version installed.
make: *** [debian/stamp-autotools] Error 1
dpkg-buildpackage: error: debian/rules build gave error exit status 2
******************************************************************************
Build finished at 20120205-0812
FAILED [dpkg-buildpackage died]

The full buidlog can be found at https://launchpad.net/ubuntu/+archive/test-rebuild-20120201/+build/3144629/+files/buildlog_ubuntu-precise-i386.epiphany-extensions_3.2.0-2_FAILEDTOBUILD.txt.gz.

[1] http://people.ubuntuwire.org/~wgrant/rebuild-ftbfs-test/test-rebuild-20120201-precise.html

[Launchpad Janitor (janitor)]

This bug was fixed in the package epiphany-extensions - 3.2.0-2ubuntu1

---------------
epiphany-extensions (3.2.0-2ubuntu1) precise; urgency=low

  * Bump epiphany version to 3.3 (LP: #935077).
 -- Leo Iannacone <email address hidden> Tue, 21 Feb 2012 02:15:35 +0100

[Jeremy Bícha (jbicha)]

This actually doesn't do much good since the current version of epiphany in precise doesn't really support extensions. For more info, see the explanation in bug 931296.