Debian broke Term::ReadKey

ethan on 2003-08-25T15:08:02

I just did some necessary upgrades on my Debian that I haven't used for a while, including the upgrade from perl5.6.1 to perl5.8.0 (I am running testing). After that I immediately re-installed all the modules that I usually use. Unfortunately, and I can't yet say why, Term::ReadKey doesn't work any longer. More precisely: it compiles and tests fine. I can switch the read-modes with no problem but ReadKey doesn't detect any key-strokes anymore in raw read-mode. When I eventually kill the program all the keys I entered are dumped to the console so I suspect they end up in some buffer.

This is more than annoying since my mp3-player relies on Term::ReadKey and I can't use it right now. I've no idea yet what could be causing this. :-(


Works for me

autarch on 2003-08-25T16:30:01

I run Debian unstable on my laptop and I just installed Term::ReadKey with the CPAN shell and it passed all its tests.

Re:Works for me

ethan on 2003-08-26T05:34:04

That might be because per default only the non-interactive tests are run. Those pass for me, too. But perl -Mblib test.pl interactive in the unpacked distribution directory wont.

One other thing, though, is bugging me right now. Before the upgrade I had 5.5.3 and 5.8.0 compiled myself. Now, after the upgrade of the vendor perl to 5.8.0, I somehow can't seem to find my old 5.8.0. Obviously it got overwritten. Which is odd because I can't imagine that I installed any custom perl with the /usr prefix. But maybe I did and the old installation has still some files around that the threaded Debian-perl now uses.