Source: flowscan
Version: 1.006-13.2
Severity: serious
Tags: wheezy sid
User: [email protected]
Usertags: qa-ftbfs-20120321 qa-ftbfs
Justification: FTBFS on amd64

Hi,

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

Relevant part:
>  debian/rules build
> test -f debian/rules
> cp -p /usr/share/misc/config.guess /usr/share/misc/config.sub .
> ./configure --prefix=/usr
> creating cache ./config.cache
> checking host system type... x86_64-unknown-linux-gnu
> checking for find... /usr/bin/find
> checking for gzip... /bin/gzip
> checking for ksh... /usr/bin/ksh
> checking for ln... /bin/ln
> checking for ls... /bin/ls
> checking for mkdir... /bin/mkdir
> checking for perl... /usr/bin/perl
> checking perl version... ok
> checking for rm... /bin/rm
> checking for rcs... no
> checking for rrdtool... /usr/bin/rrdtool
> checking for sed... /bin/sed
> checking for tar... /bin/tar
> checking for touch... /usr/bin/touch
> checking for xargs... /usr/bin/xargs
> checking for head... /usr/bin/head
> checking for grep... /bin/grep
> checking for mv... /bin/mv
> checking for rm... (cached) /bin/rm
> checking for cp... /bin/cp
> checking for RRDs... yes
> checking for Boulder::Stream... yes
> checking for Net::Patricia >= 1.010... yes
> checking for ConfigReader::DirectiveStyle... yes
> checking for Cflow >= 1.024... yes
> checking for HTML::Table... yes
> configure: error: Please change /etc/services so that the service name for 
> 80/tcp is http with alias www
> checking that service name for 80/tcp is http... no
> make: *** [build] Error 1

The full build log is available from:
   http://people.debian.org/~lucas/logs/2012/03/21/flowscan_1.006-13.2.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 about 50 AMD64 nodes
of the Grid'5000 platform, using a clean chroot.  Internet was not
accessible from the build systems.



-- 
To UNSUBSCRIBE, email to [email protected]
with a subject of "unsubscribe". Trouble? Contact [email protected]

Reply via email to