Package: libpoe-component-irc-perl
Version: 6.08+dfsg-1
Severity: serious
User: [email protected]
Usertags: qa-ftbfs-20090620 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[2]: Entering directory 
> `/build/user-libpoe-component-irc-perl_6.08+dfsg-1-amd64-oif9Ka/libpoe-component-irc-perl-6.08+dfsg'
> Makefile out-of-date with respect to /usr/lib/perl/5.10/Config.pm 
> /usr/lib/perl/5.10/CORE/config.h
> Cleaning current config before rebuilding Makefile...
> make -f Makefile.old clean > /dev/null 2>&1
> /usr/bin/perl "-Iinc" Makefile.PL 
> 
> ---------------------------------------------------------------
> A lot of the tests make use of the loopback interface. If this
> is firewalled then these tests will fail. 
> ---------------------------------------------------------------
> 
> Checking if your kit is complete...
> Warning: the following files are missing in your kit:
>       docs/ctcpspec.html
>       docs/dccspec.html
>       docs/isupport-draft.txt
>       docs/rfc1459.html
>       docs/rfc2810.html
>       docs/rfc2811.html
>       docs/rfc2812.html
>       docs/rfc2813.html
>       Makefile
> Please inform the author.
> Writing Makefile for POE::Component::IRC
> ==> Your Makefile has been rebuilt. <==
> ==> Please rerun the make command.  <==
> false
> make[2]: *** [Makefile] Error 1

The full build log is available from:
   
http://people.debian.org/~lucas/logs/2009/06/20/libpoe-component-irc-perl_6.08+dfsg-1_lsid64.buildlog

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.

-- 
| Lucas Nussbaum
| [email protected]   http://www.lucas-nussbaum.net/ |
| jabber: [email protected]             GPG: 1024D/023B3F4F |



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

Reply via email to