[Debian-ha-maintainers] Bug#741813: fence-agents: FTBFS: /bin/bash: line 3: xmllint: command not found

[David Suárez]

Source: fence-agents
Version: 4.0.7.1-2
Severity: serious
Tags: jessie sid
User: debian-qa at lists.debian.org
Usertags: qa-ftbfs-20140315 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[5]: Entering directory `/«PKGBUILDDIR»/fence/agents/xenapi'
> bash ../../../scripts/fenceparse \
> 		../../../make/copyright.cf REDHAT_COPYRIGHT \
> 		UNKNOWN \
> 		/«PKGBUILDDIR»/fence/agents/xenapi fence_xenapi | \
> 	sed \
> 		-e 's#@''FENCEAGENTSLIBDIR@#/usr/share/fence#g' \
> 		-e 's#@''SNMPBIN@#/usr/bin#g' \
> 		-e 's#@''LOGDIR@#/var/log/cluster#g' \
> 		-e 's#@''SBINDIR@#/usr/sbin#g' \
> 		-e 's#@''LIBEXECDIR@#/usr/lib/fence-agents#g' \
> 		-e 's#@''IPMITOOL_PATH@#/usr/bin/ipmitool#g' \
> 		-e 's#@''AMTTOOL_PATH@#/usr/bin/amttool#g' \
> 		-e 's#@''GNUTLSCLI_PATH@#/usr/bin/gnutls-cli#g' \
> 	> fence_xenapi
> if [ 0 -eq `echo "fence_xenapi.py" | grep fence_ &> /dev/null; echo $?` ]; then \
> 		PYTHONPATH=/«PKGBUILDDIR»/fence/agents/xenapi/../lib:/«PKGBUILDDIR»/fence/agents/xenapi/../lib ../../../fence/agents/lib/check_used_options.py fence_xenapi; \
> 	else true ; fi
> set -e && \
> 	PYTHONPATH=/«PKGBUILDDIR»/fence/agents/xenapi/../lib:/«PKGBUILDDIR»/fence/agents/xenapi/../lib \
> 		python fence_xenapi ../../../fence/agents/lib/fence2man.xsl -o metadata > .fence_xenapi.8.tmp && \
> 	xmllint --noout --relaxng /«PKGBUILDDIR»/fence/agents/xenapi/../lib/metadata.rng .fence_xenapi.8.tmp && \
> 	xsltproc ../../../fence/agents/lib/fence2man.xsl .fence_xenapi.8.tmp > fence_xenapi.8
> /bin/bash: line 3: xmllint: command not found
> make[5]: *** [fence_xenapi.8] Error 127

The full build log is available from:
   http://aws-logs.debian.net/ftbfs-logs/2014/03/15/fence-agents_4.0.7.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.