[Pkg-nagios-devel] Bug#852916: icinga-web: FTBFS: checking if php has xsl module... configure: error: not found

[Lucas Nussbaum]

Source: icinga-web
Version: 1.13.1-2
Severity: serious
Tags: stretch sid
User: debian-qa at lists.debian.org
Usertags: qa-ftbfs-20170128 qa-ftbfs
Justification: FTBFS on amd64

Hi,

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

Relevant part (hopefully):
> make[1]: Entering directory '/<<PKGBUILDDIR>>'
> ./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... configure: error: not found
> debian/rules:22: recipe for target 'override_dh_auto_configure' failed
> make[1]: *** [override_dh_auto_configure] Error 1

The full build log is available from:
   http://aws-logs.debian.net/2017/01/28/icinga-web_1.13.1-2_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.