Package: libdbi-perl
Version: 1.54-1
Severity: important

libdbi-perl fails to build from source on m68k (and arm?) due to a
self-test timeout. I bumped the t/85gofer.t timeout variable on line 34 
from 10 to 50 and that series of tests completed successfully.

Here are selected excerpts from the buildd log.


| Automatic build of libdbi-perl_1.54-1 on amiga1200.jt7336.tky.hut.fi by 
sbuild/m68k 98
| Build started at 20070402-0104
| ******************************************************************************

 [...]

| ** Using build dependencies supplied by package:
| Build-Depends: debhelper (>= 4.1.0), cdbs, perl-modules

 [...]

| Checking correctness of source dependencies...
| Toolchain package versions: libc6-dev_2.3.6.ds1-13 
linux-kernel-headers_2.6.18-7 gcc-4.1_4.1.1-21 g++-4.1_4.1.1-21 binutils_2.17-3 
libstdc++6-4.1-dev_4.1.1-21 libstdc++6_4.1.1-21

 [...]

| t/80proxy.................ok
| t/85gofer.................DBI 
connect('transport=pipeone;policy=pedantic;perl=/usr/bin/perl  
-Mblib=/build/buildd/libdbi-perl-1.54/blib;timeout=10;dsn=dbi:DBM:dbm_type=SDBM_File;lockfile=0','',...)
 failed: receive_response timed-out after 10 seconds at 
/build/buildd/libdbi-perl-1.54/blib/lib/DBD/Gofer/Transport/Base.pm line 48. at 
t/85gofer.t line 120
| 
| #   Failed test 'should connect to 
dbi:Gofer:transport=pipeone;policy=pedantic;perl=/usr/bin/perl  
-Mblib=/build/buildd/libdbi-perl-1.54/blib;timeout=10;dsn=dbi:DBM:dbm_type=SDBM_File;lockfile=0
 (receive_response timed-out after 10 seconds at 
/build/buildd/libdbi-perl-1.54/blib/lib/DBD/Gofer/Transport/Base.pm line 48.)'
| #   in t/85gofer.t at line 121.

 [...]

and so on ....


A full buildd log is available at 
<http://buildd.debian.org/build.php?pkg=libdbi-perl&ver=1.54-1&arch=m68k>

Other buildd logs may be available at 
<http://buildd.debian.org/build.php?arch=&pkg=libdbi-perl>

--
Stephen R. Marenka     If life's not fun, you're not doing it right!
<[EMAIL PROTECTED]>


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

Reply via email to