Skip Menu |

This queue is for tickets about the CPANPLUS CPAN distribution.

Report information
The Basics
Id: 79064
Status: resolved
Priority: 0/
Queue: CPANPLUS

People
Owner: Nobody in particular
Requestors: shay [...] cpan.org
Cc:
AdminCc:

Bug Information
Severity: Critical
Broken in: 0.9130
Fixed in: (no value)



Subject: cpanp shell exits with error "No such module: Terminal>"
I have added my installed perl's bin\ folder to my PATH and am trying to start the cpanp shell by simply typing "cpanp" in a standard cmd.exe command prompt on Windows 7. The cpanp shell immediately exits with an error if I try to enter it with my current directory being on the C: drive: ########## C:\Temp>cpanp CPANPLUS::Shell::Default -- CPAN exploration and module installation (v0.9130) *** Please report bugs to <bug-cpanplus@rt.cpan.org>. *** Using CPANPLUS::Backend v0.9130. ReadLine support disabled. *** Type 'p' now to show start up log Did you know... You can turn off these tips using 's conf show_startup_tip 0' [ERROR] 'Terminal>' does not contain an author part [ERROR] Cannot find 'Terminal>' in the module tree No such module: Terminal> No modules found to operate on! Exiting CPANPLUS shell C:\Temp> ########## If I switch to seemingly any other drive letter then it works fine: ########## C:\Temp>K: K:\>cpanp CPANPLUS::Shell::Default -- CPAN exploration and module installation (v0.9130) *** Please report bugs to <bug-cpanplus@rt.cpan.org>. *** Using CPANPLUS::Backend v0.9130. ReadLine support disabled. *** Type 'p' now to show start up log Did you know... You can use wildcards like '*' and '2..5' on search results CPAN Terminal> ########## This is most unfortunate since I normally work on the C: drive :-( I have an identical problem with CPAN's cpan shell (see CPAN RT#79001), so the problem must lie elsewhere (Term::ReadLine?), but I'm reporting the bug here anyway because I guess if a fix is made elsewhere then you'll want to add a prerequisite minimum version on the updated dependent.
I would search through the C: partition whether there is a file inputrc or .inputrc or whether there is something enlightening in \Program Files\GnuWin\ Or, if you have something like strace on Windows, watch which files are being accessed when you start from C: comaring to when you start from E: What you describe looks much more than a misconfiguration than a program defect.
On Sat Aug 18 03:39:58 2012, ANDK wrote: Show quoted text
> I would search through the C: partition whether there is a file inputrc > or .inputrc or whether there is something enlightening in \Program > Files\GnuWin\ > > Or, if you have something like strace on Windows, watch which files are > being accessed when you start from C: comaring to when you start from E: > > What you describe looks much more than a misconfiguration than a program > defect.
I have a .inputrc file in my Cygwin HOME directory and an inputrc file in my Git etc directory, but neither Cygwin nor Git are on my PATH and renaming those files makes no difference. They are the only two sets of Unixy tools that I have installed. There is no GnuWin or UnxUtils anywhere, and setting my PATH to just C:\Windows\system32;C:\Windows;C:\perl\bin makes no difference either. I will look for some kind of strace tool, though. Perhaps the Sysinternals Suite will have something... (I've also tried deleting my C:\Users\Steve\.cpan and C:\Users\Steve\AppData\Roaming\.cpanplus folders and (auto-)reconfiguring them from scratch, but again to no avail.)
On Sat Aug 18 06:18:40 2012, SHAY wrote: Show quoted text
> On Sat Aug 18 03:39:58 2012, ANDK wrote:
> > I would search through the C: partition whether there is a file inputrc > > or .inputrc or whether there is something enlightening in \Program > > Files\GnuWin\ > > > > Or, if you have something like strace on Windows, watch which files are > > being accessed when you start from C: comaring to when you start from E: > > > > What you describe looks much more than a misconfiguration than a program > > defect.
> > I will look for some kind of strace tool, though. Perhaps the > Sysinternals Suite will have something...
Found it. Sysinternals Suite's ProcMon.exe utility helped me find that when starting cpan from the C: drive perl.exe was reading C:\Dev\tty, but not when starting from the K: drive. I have a folder in the root of my C: drive called C:\Dev (where I have various development things), and it somehow came to have a file called tty inside it. I have no idea how that file got there, but when (and only when) the current drive is C: then Term::ReadLine::findConsole()'s test for the existence of /dev/tty was returning true... If I delete that file then it all works :-) (And if I create a new *empty* C:\Dev\tty file again then it goes wrong again and something writes "CPAN Terminal> CPAN Terminal> " into that file. I see the same effect with the cpan shell, except that that writes "cpan[1]> cpan[2]> " into the file.) It is a puzzle what created the file in the first place, but I've fixed Term::ReadLine to no longer check for it on Windows since you'd surely never want to use such a file on Windows if it does happen to exist. I've pushed my fix as commit 4cc026083a (since UPSTREAM is 'blead' for Term::ReadLine), and will notify rafl so that he can roll a new CPAN release sometime. Thanks for your help. Please feel free to close this and #79001 now.
Just realized that I can 'resolve' it myself (presumably since I reported it in the first place!) :-)
Subject: Re: [rt.cpan.org #79064] cpanp shell exits with error "No such module: Terminal>"
Date: Sat, 18 Aug 2012 13:22:30 +0100
To: Steve Hay via RT <bug-CPANPLUS [...] rt.cpan.org>
From: "Chris 'BinGOs' Williams" <chris [...] bingosnet.co.uk>
On Sat, Aug 18, 2012 at 08:09:48AM -0400, Steve Hay via RT wrote: Show quoted text
> Queue: CPANPLUS > Ticket <URL: https://rt.cpan.org/Ticket/Display.html?id=79064 > > > On Sat Aug 18 06:18:40 2012, SHAY wrote:
> > On Sat Aug 18 03:39:58 2012, ANDK wrote:
> > > I would search through the C: partition whether there is a file inputrc > > > or .inputrc or whether there is something enlightening in \Program > > > Files\GnuWin\ > > > > > > Or, if you have something like strace on Windows, watch which files are > > > being accessed when you start from C: comaring to when you start from E: > > > > > > What you describe looks much more than a misconfiguration than a program > > > defect.
> > > > I will look for some kind of strace tool, though. Perhaps the > > Sysinternals Suite will have something...
> > Found it. Sysinternals Suite's ProcMon.exe utility helped me find that > when starting cpan from the C: drive perl.exe was reading C:\Dev\tty, > but not when starting from the K: drive. > > I have a folder in the root of my C: drive called C:\Dev (where I have > various development things), and it somehow came to have a file called > tty inside it. I have no idea how that file got there, but when (and > only when) the current drive is C: then Term::ReadLine::findConsole()'s > test for the existence of /dev/tty was returning true... > > If I delete that file then it all works :-) > > (And if I create a new *empty* C:\Dev\tty file again then it goes wrong > again and something writes "CPAN Terminal> CPAN Terminal> " into that > file. I see the same effect with the cpan shell, except that that writes > "cpan[1]> cpan[2]> " into the file.) > > It is a puzzle what created the file in the first place, but I've fixed > Term::ReadLine to no longer check for it on Windows since you'd surely > never want to use such a file on Windows if it does happen to exist. > I've pushed my fix as commit 4cc026083a (since UPSTREAM is 'blead' for > Term::ReadLine), and will notify rafl so that he can roll a new CPAN > release sometime. > > Thanks for your help. Please feel free to close this and #79001 now.
Thanks for finding where the rabbit-hole went. Show quoted text
>:)
-- Chris Williams aka BinGOs PGP ID 0x4658671F http://www.gumbynet.org.uk ==========================
Download (untitled)
application/pgp-signature 189b

Message body not shown because it is not plain text.

Show quoted text
CBW> Thanks for finding where the rabbit-hole went.
Seconded, very nice resolution:) I'll resolve the ticket a second time now. Thanks again,