Your message dated Mon, 23 Feb 2009 01:06:05 -0500
with message-id <bdd9d5220902222206g2a79fa86odb173acf92ea2...@mail.gmail.com>
and subject line Re: Bug#516619: libterm-readline-gnu-perl can't be used
has caused the Debian Bug report #516619,
regarding libterm-readline-gnu-perl can't be used
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 ow...@bugs.debian.org
immediately.)
--
516619: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=516619
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: libterm-readline-gnu-perl
Version: 1.17a-2+b1
Severity: grave
Justification: renders package unusable
Hi,
My perl application that depends on Term::ReadLine::Gnu behaves
strangely when using with the latest libterm-readline-gnu-perl
package (v1.17a-2+b1).
So I gave it some tests, using the Term::ReadLine::Gnu default test
suits:
r...@helios:/cpan/build/Term-ReadLine-Gnu-1.17a# perl t/callback.t
1..7
ok 1 loading
Cannot do `initialize' in Term::ReadLine::Gnu at t/callback.t line 31
"Cannot do `initialize' in Term::ReadLine::Gnu", that's the same
error that I get in my stripped down Term_ReadLine test code as
well.
r...@helios:/cpan/build/Term-ReadLine-Gnu-1.17a# PERL_DL_NONLAZY=1
/usr/bin/perl "-MExtUtils::Command::MM" "-e" "test_harness(0, '', '')"
t/callback.t
t/callback....Cannot do `initialize' in Term::ReadLine::Gnu at t/callback.t
line 31
t/callback....dubious
Test returned status 2 (wstat 512, 0x200)
DIED. FAILED tests 2-7
Failed 6/7 tests, 14.29% okay
Failed Test Stat Wstat Total Fail List of Failed
-------------------------------------------------------------------------------
t/callback.t 2 512 7 12 2-7
Failed 1/1 test scripts. 6/7 subtests failed.
Files=1, Tests=7, 0 wallclock secs ( 0.03 cusr + 0.00 csys = 0.03 CPU)
Failed 1/1 test programs. 6/7 subtests failed.
Using the "standard" harness test fails as well.
r...@helios:/cpan/build/Term-ReadLine-Gnu-1.17a# PERL_DL_NONLAZY=1
/usr/bin/perl "-MExtUtils::Command::MM" "-e" "test_harness(0, 'blib/lib',
'blib/arch')" t/*.t
t/callback....ok
t/history.....ok
t/readline....ok Try `/usr/bin/perl -Mblib t/readline.t verbose', if
you will.
t/readline....ok
All tests successful.
Files=3, Tests=193, 1 wallclock secs ( 0.15 cusr + 0.00 csys = 0.15 CPU)
Using the "standard" harness test with my local build libs works.
Based on above, I conclude that the latest libterm-readline-gnu-perl
package (v1.17a-2+b1) fails to behave normally.
Please comment.
Thanks
-- System Information:
Debian Release: 5.0
APT prefers stable
APT policy: (300, 'stable'), (50, 'unstable'), (20, 'experimental')
Architecture: i386 (i686)
Kernel: Linux 2.6.26-grml (SMP w/1 CPU core; PREEMPT)
Locale: LANG=C, LC_CTYPE=C (charmap=ANSI_X3.4-1968)
Shell: /bin/sh linked to /bin/bash
Versions of packages libterm-readline-gnu-perl depends on:
ii libc6 2.7-13 GNU C Library: Shared libraries
ii libncurses5 5.7+20081213-1 shared libraries for terminal hand
ii libreadline5 5.2-3.1 GNU readline and history libraries
ii perl 5.10.0-15 Larry Wall's Practical Extraction
ii perl-base [perlapi-5.10.0 5.10.0-15 minimal Perl system
libterm-readline-gnu-perl recommends no packages.
libterm-readline-gnu-perl suggests no packages.
-- no debconf information
--- End Message ---
--- Begin Message ---
On Sun, Feb 22, 2009 at 4:59 PM, Niko Tyni <nt...@debian.org> wrote:
> it seems to work here on lenny/x86. . .
Thanks for the swift reply, Niko.
My system is in some kind of weird stage because my recent upgrade
in lenny broke my alsa.
Everything is OK now.
Sorry for the bothering.
cheers
--- End Message ---
