Bug #107035 for System-Command: Failing to install System::Command on Win7/64bit

Fri Sep 11 05:38:56 2015 nstender [...] live.de - Ticket created

Subject:	Failing to install System::Command on Win7/64bit
Date:	Fri, 11 Sep 2015 11:38:46 +0200
To:	"bug-System-Command [...] rt.cpan.org" <bug-system-command [...] rt.cpan.org>
From:	Nicole Stender <nstender [...] live.de>

Hi there, I just made some new installations of different Perl software for Win7/64bit/SP1 (Strawberry Perl 5.20.1.1-32bit, 5.20.1.1-64bit, 5.22.0.1-64bit and ActivePerl 5.20.2.2002 64bit) and just tried to install the cpan module System::Command. In each case this installation failed with the following problem 'invalid argument opening stdin as win32 handle' and was followed by issues running the tests. I am a still a newbie to all this cpan stuff, so, maybe I missed something. I also tried the web for any help, but I couldn't find anything similar to it. I would appreciate any help. For more information don't hesitate to mail me. Kind regards,Nicole Stender

Wed Sep 23 05:01:24 2015 book [...] cpan.org - Correspondence added

On Fri Sep 11 05:38:56 2015, nstender@live.de wrote: Show quoted text

> I just made some new installations of different Perl software for > Win7/64bit/SP1 (Strawberry Perl 5.20.1.1-32bit, 5.20.1.1-64bit, > 5.22.0.1-64bit and ActivePerl 5.20.2.2002 64bit) and just tried to > install the cpan module System::Command. In each case this > installation failed with the following problem 'invalid argument > opening stdin as win32 handle' and was followed by issues running the > tests.

Thanks for reporting this issue, and sorry for taking so long to reply. I don't have a Windows machine, so it's a little hard for me to test on that platform. Could you send me the full failing test reports, so that I can get a better idea of what issues you're facing? Thanks, -- BooK

Wed Sep 23 05:01:24 2015 The RT System itself - Status changed from 'new' to 'open'

Sun Sep 27 08:20:41 2015 nstender [...] live.de - Correspondence added

Subject:	RE: [rt.cpan.org #107035] Failing to install System::Command on Win7/64bit
Date:	Sun, 27 Sep 2015 14:20:22 +0200
To:	Philippe Bruhat BooK via RT <bug-system-command [...] rt.cpan.org>
From:	Nicole Stender <nstender [...] live.de>

Hi Book, thanks for your reply. In the meantime I was able to fix the problem for myself using a workaround. I'm going to explain what I did. For all installations I used the 'cpan App::Module' command or enabled the Perl CPAN environment with 'perl -MCPAN -e shell' and installed via 'install App::Module'. First of all, I needed this module for Git::Repository as requirement. Second, I installed the Git::Repository module on two different Win7/64bit/SP1 machines. The first installation of this module went pretty well with no issues. The System::Command version 1.112 was used at this point of time. A bit later I switched to another more powerful system for setting up VMs. I installed Git::Repository again - the installation failed as reported - using System::Command version 1.113. After a lot of researching and figuring out, that there was a new version available since my first install, I came up with the following solution: To manually install the old System::Command 1.112 version - worked with dmake - installed Git::Repository afterwards - set up Git 1.9.4 for Windows - as on my old system - it worked. I used this source http://www.thegeekstuff.com/2008/09/how-to-install-perl-modules-manually-and-using-cpan-command/ for manual installation. At this point I also have to remark, that I tried to force install System::Command 1.113. Everything seemed to be okay, but my test script failed. Sadly I can't remark if this was really a System::Command issue or caused by the newest Git version which disabled some features (or is just buggy) for Windows. The issues with the Git version came up later, so I didn't tested this again. You asked my to send you the full failing test reports which is a bit difficult right now, because I don't want to reset my Perl again (using it and the Git repo at work on daily base). My private Laptop and Desktop run with Ubuntu/OpenSuse. Anyway, my parents still got a Windows 7 Lap where I could retest all this. I'm going to visit them the next weekend, therefore it will still take a week until I can send you any reports or more infos about it. Best regards, Nicole Stender Show quoted text

> Subject: [rt.cpan.org #107035] Failing to install System::Command on Win7/64bit > From: bug-System-Command@rt.cpan.org > To: nstender@live.de > Date: Wed, 23 Sep 2015 05:01:24 -0400 > > <URL: https://rt.cpan.org/Ticket/Display.html?id=107035 > > > On Fri Sep 11 05:38:56 2015, nstender@live.de wrote:

> > I just made some new installations of different Perl software for > > Win7/64bit/SP1 (Strawberry Perl 5.20.1.1-32bit, 5.20.1.1-64bit, > > 5.22.0.1-64bit and ActivePerl 5.20.2.2002 64bit) and just tried to > > install the cpan module System::Command. In each case this > > installation failed with the following problem 'invalid argument > > opening stdin as win32 handle' and was followed by issues running the > > tests.

> > Thanks for reporting this issue, and sorry for taking so long to reply. > > I don't have a Windows machine, so it's a little hard for me to test on that platform. > > Could you send me the full failing test reports, so that I can get a better idea of what issues you're facing? > > Thanks, > > -- BooK >

Wed Sep 30 14:27:46 2015 book [...] cpan.org - Correspondence added

On Sun Sep 27 08:20:41 2015, nstender@live.de wrote: Show quoted text

> Hi Book, > > thanks for your reply. > > In the meantime I was able to fix the problem for myself using a > workaround. I'm going to explain what I did. For all installations I > used the 'cpan App::Module' command or enabled the Perl CPAN > environment with 'perl -MCPAN -e shell' and installed via 'install > App::Module'. > > First of all, I needed this module for Git::Repository as requirement. > Second, I installed the Git::Repository module on two different > Win7/64bit/SP1 machines. The first installation of this module went > pretty well with no issues. The System::Command version 1.112 was used > at this point of time. > A bit later I switched to another more powerful system for setting up > VMs. I installed Git::Repository again - the installation failed as > reported - using System::Command version 1.113.

It turns out I had made a stupid mistake in one of the test scripts, that only failed on Windows because of a mismatch in the number of tests planned versus the number of tests actually executed. This has been fixed with version 1.115. Show quoted text

> At this point I also have to remark, that I tried to force install > System::Command 1.113.

Force install would have worked, because the error in the test script was, a priori, due to the test count mismatch. Show quoted text

> Everything seemed to be okay, but my test > script failed. Sadly I can't remark if this was really a > System::Command issue or caused by the newest Git version which > disabled some features (or is just buggy) for Windows. The issues with > the Git version came up later, so I didn't tested this again.

Git::Repository is only a thin wrapper around Git. If System::Command works, it should probably work as weel. I'd be interested in seeing your Git test script, and the Git versions which passed and failed, in case there is something I can do about it in Git::Repository (very unlikely). Show quoted text

> You asked my to send you the full failing test reports which is a bit > difficult right now, because I don't want to reset my Perl again > (using it and the Git repo at work on daily base).

Don't worry about that, then. Show quoted text

> Anyway, my parents still got a > Windows 7 Lap where I could retest all this. I'm going to visit them > the next weekend, therefore it will still take a week until I can send > you any reports or more infos about it.

Many thanks. If you test with the latest version of System::Command, it's likely that the install will just work. I'll still be interested in the test report in case something goes wrong. :-) Regards, -- BooK

Sat Oct 03 09:21:32 2015 nstender [...] live.de - Correspondence added

Subject:	RE: [rt.cpan.org #107035] Failing to install System::Command on Win7/64bit
Date:	Sat, 3 Oct 2015 15:21:15 +0200
To:	Philippe Bruhat BooK via RT <bug-system-command [...] rt.cpan.org>
From:	Nicole Stender <nstender [...] live.de>

Hi Book, I just re-tested the System::Command module (version 1.115) with Strawberry Perl and no issues occured during the install, so everything works fine ;) - thanks very much for taking a look at this one. In case of the Git::Repository module. I wrote a similar script (without company costume module stuff), that simply tries to perform a clone action from a given repo. I will attach this script to this mail. I used to install Git/64bit versions 2.5.x and just right now 2.6.0 - both failing with following output: C:\Users\...>perl testGitRepository.pl -repo <repoUrl> -target testCloning into 'test'...bash: /dev/tty: No such device or addresserror: failed to execute prompt script (exit code 1)fatal: could not read Password for '<repoUrl>': Invalid argument at testGitRepository.pl line 21. I already took a look at this failure and found this post https://github.com/notatestuser/gift/issues/66. So I installed an older Git Version (1.9.4) and it worked again. This only occured on windows. Any installations on my CentOS machine worked right from the start - Git as well as Git::Repository. I don't think that this issue is related to the cpan module, but I can't tell for sure. Best regards,Nicole Stender Show quoted text

> Subject: [rt.cpan.org #107035] Failing to install System::Command on Win7/64bit > From: bug-System-Command@rt.cpan.org > To: nstender@live.de > Date: Wed, 30 Sep 2015 14:27:46 -0400 > > <URL: https://rt.cpan.org/Ticket/Display.html?id=107035 > > > On Sun Sep 27 08:20:41 2015, nstender@live.de wrote:

> > Hi Book, > > > > thanks for your reply. > > > > In the meantime I was able to fix the problem for myself using a > > workaround. I'm going to explain what I did. For all installations I > > used the 'cpan App::Module' command or enabled the Perl CPAN > > environment with 'perl -MCPAN -e shell' and installed via 'install > > App::Module'. > > > > First of all, I needed this module for Git::Repository as requirement. > > Second, I installed the Git::Repository module on two different > > Win7/64bit/SP1 machines. The first installation of this module went > > pretty well with no issues. The System::Command version 1.112 was used > > at this point of time. > > A bit later I switched to another more powerful system for setting up > > VMs. I installed Git::Repository again - the installation failed as > > reported - using System::Command version 1.113.

> > It turns out I had made a stupid mistake in one of the test scripts, > that only failed on Windows because of a mismatch in the number of > tests planned versus the number of tests actually executed. > > This has been fixed with version 1.115. >

> > At this point I also have to remark, that I tried to force install > > System::Command 1.113.

> > Force install would have worked, because the error in the test script > was, a priori, due to the test count mismatch. >

> > Everything seemed to be okay, but my test > > script failed. Sadly I can't remark if this was really a > > System::Command issue or caused by the newest Git version which > > disabled some features (or is just buggy) for Windows. The issues with > > the Git version came up later, so I didn't tested this again.

> > Git::Repository is only a thin wrapper around Git. If System::Command > works, it should probably work as weel. I'd be interested in seeing > your Git test script, and the Git versions which passed and failed, > in case there is something I can do about it in Git::Repository > (very unlikely). >

> > You asked my to send you the full failing test reports which is a bit > > difficult right now, because I don't want to reset my Perl again > > (using it and the Git repo at work on daily base).

> > Don't worry about that, then. >

> > Anyway, my parents still got a > > Windows 7 Lap where I could retest all this. I'm going to visit them > > the next weekend, therefore it will still take a week until I can send > > you any reports or more infos about it.

> > Many thanks. If you test with the latest version of System::Command, > it's likely that the install will just work. I'll still be interested > in the test report in case something goes wrong. :-) > > Regards, > > -- BooK > >

Message body is not shown because sender requested not to inline it.

Sun Jan 03 06:40:06 2016 book [...] cpan.org - Status changed from 'open' to 'resolved'