Yes, the problems all apply to 1.76_01.
Further testing has revealed that both at a NAT level and the inability
of the now-standard and default-enabled Windows firewall means that on
Win32, unless otherwise explicitly set _ALL_ FTP needs to be done passively.
So for the Perl installer stuff we are doing we are setting FTP_PASSIVE
on by default, and at a system level. At the very least CPAN.pm as found
in core perl needs to set FTP_PASSIVE=1 if not already.
Adam K
Nicholas Clark via RT wrote:
Tue, Jan 24, 2006 at 06:21:36AM -0800, Adam Kennedy wrote:

>In doing some Windows Perl stuff (for my Perl on Windows competition at
>http://use.perl.org/~Alias/journal/28427) I noticed a problem with the
>CPAN.pm included in ActivePerl 5.8.7, which I'm assuming at this point
>is the same as in stock 5.8.7.
I'm not personally in a position to test on Windows, so I hope that someone
else can help here.
CPAN.pm has been upgraded since 5.8.7. If I read the above correctly, so
far you've only been able to test for this problem on the CPAN.pm supplied
with 5.8.7? In stock 5.8.7 CPAN.pm's VERSIN is 1.76_01.
Nicholas Clark

The main reason I'd like to see this dealt with before 5.8.8 is that it
can be fixed very easily. Just make sure FTP_PASSIVE=1 when running
CPAN.pm on Win32. Either once, or lexically inside the fetch code.

It's one line of code in the appropriate place

local $ENV{FTP_PASSIVE} = 1 if $IS_WIN32;

line in the right place means we don't have to wait another 6 months
to fix the only real showstopper for getting CPAN client support on
Windows. (and not needing to rely solely on PPM repositories, which seem
to be getting more and more out of sync).

Adam K

Andreas J. Koenig wrote:
Wed, 25 Jan 2006 03:49:36 +1100, Adam Kennedy <adam (AT) phase-n (DOT) comsaid:

Yes, the problems all apply to 1.76_01.

I don't think we should declare a problem that exists since 2003 as a
showstopper for 5.8.8. In this area code has not been touched for
quite a while. If I understand correctly, 1.76_01 and 1.83 share the
bug, right? So 5.8.8 has no alternative except to say something about
it in the release notes, right?

Further testing has revealed that both at a NAT level and the
inability of the now-standard and default-enabled Windows firewall
means that on Win32, unless otherwise explicitly set _ALL_ FTP needs
to be done passively.

So for the Perl installer stuff we are doing we are setting
FTP_PASSIVE on by default, and at a system level. At the very least
CPAN.pm as found in core perl needs to set FTP_PASSIVE=1 if not
already.

I suggest you write something up for the release notes, then we go
through the bugreports in RT, so we get a better 1.84 for blead and
then Nick has something to integrate from blead when 5.8.9 is to be
released.

Especially, I should note, now that we have two good Perl distributions
for Windows that can compile and install direct from CPAN out of the box.

http://use.perl.org/~Alias/journal/

Adam K

Andreas J. Koenig wrote:
Wed, 25 Jan 2006 03:49:36 +1100, Adam Kennedy <adam (AT) phase-n (DOT) comsaid:

Yes, the problems all apply to 1.76_01.

I don't think we should declare a problem that exists since 2003 as a
showstopper for 5.8.8. In this area code has not been touched for
quite a while. If I understand correctly, 1.76_01 and 1.83 share the
bug, right? So 5.8.8 has no alternative except to say something about
it in the release notes, right?

Further testing has revealed that both at a NAT level and the
inability of the now-standard and default-enabled Windows firewall
means that on Win32, unless otherwise explicitly set _ALL_ FTP needs
to be done passively.

So for the Perl installer stuff we are doing we are setting
FTP_PASSIVE on by default, and at a system level. At the very least
CPAN.pm as found in core perl needs to set FTP_PASSIVE=1 if not
already.

I suggest you write something up for the release notes, then we go
through the bugreports in RT, so we get a better 1.84 for blead and
then Nick has something to integrate from blead when 5.8.9 is to be
released.

Adam Kennedy <adam (AT) phase-n (DOT) comwrites:

The main reason I'd like to see this dealt with before 5.8.8 is that
it can be fixed very easily. Just make sure FTP_PASSIVE=1 when running
CPAN.pm on Win32. Either once, or lexically inside the fetch code.

It's one line of code in the appropriate place

local $ENV{FTP_PASSIVE} = 1 if $IS_WIN32;

line in the right place means we don't have to wait another 6
months to fix the only real showstopper for getting CPAN client
support on Windows.

CPAN.pm on Windows works just fine for me with the lastest ActivePerl
and I don't have this line anywhere.

(and not needing to rely solely on PPM
repositories, which seem to be getting more and more out of sync).

My impression was certainly that the state of PPM was improving, not
the other way around. Do you have real data that shows this to be
true?