[Pkg-nagios-devel] Bug#713220: icinga-web: FTBFS: configure: error: not found

[Lucas Nussbaum]

Source: icinga-web
Version: 1.9.0+dfsg1-1
Severity: serious
Tags: jessie sid
User: debian-qa at lists.debian.org
Usertags: qa-ftbfs-20130620 qa-ftbfs
Justification: FTBFS on amd64

Hi,

During a rebuild of all packages in sid, your package failed to build on
amd64.

Relevant part:
> make[1]: Entering directory `/«BUILDDIR»/icinga-web-1.9.0+dfsg1'
> ./configure --prefix=/usr/share/icinga-web \
> 	--bindir=/usr/lib/icinga-web/bin \
> 	--sysconfdir=/etc/icinga-web \
> 	--datarootdir=/usr/share/icinga-web \
> 	--docdir=/usr/share/doc/icinga-web \
> 	--libdir=/usr/lib/icinga-web \
> 	--with-web-absolute-path=/usr/share/icinga-web/pub \
> 	--with-web-apache-path="/etc/apache2/conf.d" \
> 	--with-web-user="www-data" --with-web-group="www-data" \
> 	--with-cache-dir=/var/cache/icinga-web \
> 	--with-log-dir=/var/log/icinga-web \
> 	--with-conf-dir=/etc/icinga-web/conf.d \
> 	--with-icinga-bin="/usr/sbin/icinga" \
> 	--with-icinga-cfg="/etc/icinga/icinga.cfg" \
> 	--with-icinga-objects-dir="/etc/icinga/objects" \
> 	--with-api-cmd-file="/var/lib/icinga/rw/icinga.cmd" \
> 	--with-reporting_tmp_dir="/var/cache/icinga-web/reporting"
> checking for a BSD-compatible install... /usr/bin/install -c
> checking for grep that handles long lines and -e... /bin/grep
> checking for a sed that does not truncate output... /bin/sed
> checking for php... /usr/bin/php
> checking for phing... not found
> configure: WARNING: binary phing not found in PATH
> checking if php has sockets module... found
> checking if php has xsl module... found
> checking if php has xml module... found
> configure: error: not found
> make[1]: *** [override_dh_auto_configure] Error 1

The full build log is available from:
   http://aws-logs.debian.net/ftbfs-logs/2013/06/20/icinga-web_1.9.0+dfsg1-1_unstable.log

A list of current common problems and possible solutions is available at 
http://wiki.debian.org/qa.debian.org/FTBFS . You're welcome to contribute!

About the archive rebuild: The rebuild was done on EC2 VM instances from
Amazon Web Services, using a clean, minimal and up-to-date chroot. Every
failed build was retried once to eliminate random failures.