Your message dated Wed, 8 Nov 2006 22:16:44 -0800
with message-id <[EMAIL PROTECTED]>
and subject line libcvs-perl: FTBFS: Test failures
has caused the attached Bug report 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 I am
talking about this indicates a serious mail system misconfiguration
somewhere. Please contact me immediately.)
Debian bug tracking system administrator
(administrator, Debian Bugs database)
--- Begin Message ---
Package: libcvs-perl
Version: 0.07-1
Severity: serious
From my pbuilder build log:
...
# Add commands to install the package into debian/ACKAGE_NAME here
/usr/bin/make test
make[1]: Entering directory `/tmp/buildd/libcvs-perl-0.07'
PERL_DL_NONLAZY=1 /usr/bin/perl "-MExtUtils::Command::MM" "-e" "test_harness(0,
'blib/lib', 'blib/arch')" t/*.t
t/00checkout....ok
t/05commit......# Failed test 2 in t/05commit.t at line 12
# t/05commit.t line 12 is: ok($cvs);
Cannot open file `/tmp/buildd/libcvs-perl-0.07/cvs-test/test.txt': No such file
or directory at t/05commit.t line 14.
dubious
Test returned status 2 (wstat 512, 0x200)
DIED. FAILED tests 2-5
Failed 4/5 tests, 20.00% okay
...
Failed Test Stat Wstat Total Fail Failed List of Failed
-------------------------------------------------------------------------------
t/05commit.t 2 512 5 7 140.00% 2-5
t/10status.t 2 512 11 19 172.73% 2-11
t/20tag.t 2 512 6 9 150.00% 2-6
t/21rtag.t 2 512 6 7 116.67% 3-6
t/30update.t 2 512 6 9 150.00% 2-6
t/40diff.t 2 512 6 9 150.00% 2-6
t/90release.t 2 512 4 4 100.00% 3-4
Failed 7/9 test scripts, 22.22% okay. 35/50 subtests failed, 30.00% okay.
make[1]: *** [test_dynamic] Error 2
make[1]: Leaving directory `/tmp/buildd/libcvs-perl-0.07'
make: *** [install-stamp] Error 2
--
Daniel Schepler
--- End Message ---
--- Begin Message ---
The latest reopening of this bug points to a problem with the build
environment not having any pty interface available. This is a standard
feature of Unix systems, and it's fair to require that a environment support
ptys in order to be able to build Debian packages. I'm therefore closing
this bug.
Thanks,
--
Steve Langasek Give me a lever long enough and a Free OS
Debian Developer to set it on, and I can move the world.
[EMAIL PROTECTED] http://www.debian.org/
--- End Message ---
