Your message dated Sat, 12 Jul 2008 11:39:06 +0200
with message-id <[EMAIL PROTECTED]>
and subject line Re: Bug#489101: speedy-cgi-perl: FTBFS: kill: No such process
has caused the Debian Bug report #489101,
regarding speedy-cgi-perl: FTBFS: kill: No such process
to be marked as done.

This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.

(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact [EMAIL PROTECTED]
immediately.)


-- 
489101: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=489101
Debian Bug Tracking System
Contact [EMAIL PROTECTED] with problems
--- Begin Message ---
Package: speedy-cgi-perl
Version: 2.22-10
Severity: serious
User: [EMAIL PROTECTED]
Usertags: qa-ftbfs-20080702 qa-ftbfs
Justification: FTBFS on i386

Hi,

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

Relevant part:
> make[1]: Entering directory 
> `/build/user-speedy-cgi-perl_2.22-10-amd64-kE9own/speedy-cgi-perl-2.22-10/speedy'
> PERL_DL_NONLAZY=1 
> SPEEDY=/build/user-speedy-cgi-perl_2.22-10-amd64-kE9own/speedy-cgi-perl-2.22-10/speedy/speedy
>  
> SPEEDY_BACKENDPROG=/build/user-speedy-cgi-perl_2.22-10-amd64-kE9own/speedy-cgi-perl-2.22-10/speedy_backend/speedy_backend
>  
> SPEEDY_MODULE=/build/user-speedy-cgi-perl_2.22-10-amd64-kE9own/speedy-cgi-perl-2.22-10//
>  SPEEDY_TIMEOUT=300 /usr/bin/perl "-MExtUtils::Command::MM" "-e" 
> "test_harness(0, '../blib/lib', '../blib/arch')" t/*.t
> t/alarm...............ok
> t/argv................ok
> t/basic1..............ok
> t/basic2..............ok
> t/be_memleak..........ok
> t/begin_block.........ok
> t/begin_dup...........ok
> t/cgi_reset...........ok
> t/chdir...............ok
> t/detach..............ok
> t/eagain..............ok
> t/exit................ok
> t/group...............ok
> t/hold_stdio..........ok
> t/initial_eof.........ok
> t/killfe..............ok
> t/maxbackend..........ok
> t/maxruns.............ok
> t/misc................ok
> t/mungefds............ok
> t/register_cleanup....ok
> t/setopt..............ok
> t/sh_bang.............ok
> t/shutdown............ok
> t/signal..............ok
> t/stdin...............ok
> t/stdio...............ok
> t/stdio2..............ok
> t/stdio_close.........ok
> t/thread..............ok
> t/timeout.............ok
> t/touch...............ok
> t/wrongfd.............ok
> All tests successful.
> Files=33, Tests=73, 133 wallclock secs ( 0.72 cusr +  1.31 csys =  2.03 CPU)
> make[1]: Leaving directory 
> `/build/user-speedy-cgi-perl_2.22-10-amd64-kE9own/speedy-cgi-perl-2.22-10/speedy'
> touch build-stamp
> perl debian/list-backends 
> "/build/user-speedy-cgi-perl_2.22-10-amd64-kE9own/speedy-cgi-perl-2.22-10/speedy_backend/speedy_backend"
>  | \
>         xargs --no-run-if-empty --verbose kill
> kill 10204 10456 15976 15977 17105 17106 17110 17111 17115 17116 22975 22977 
> 23478 23479 25519 25530 25816 25824 26404 26405 26426 26427 26433 26434 27289 
> 27290 1951 2194 2198 4338 4355 7190 7207 9901 9902 12342 12792 12886 12887 
> 12925 12935 12939 12940 12948 12958 13111 13294 13489 13490 
> kill: No such process
> make: *** [kill-backends-stamp] Error 123

The full build log is available from:
   http://people.debian.org/~lucas/logs/2008/07/02

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 containing a sid i386
environment.  Internet was not accessible from the build systems.

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



--- End Message ---
--- Begin Message ---
not reproducible anymore.
-- 
| Lucas Nussbaum
| [EMAIL PROTECTED]   http://www.lucas-nussbaum.net/ |
| jabber: [EMAIL PROTECTED]             GPG: 1024D/023B3F4F |


--- End Message ---

Reply via email to