You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I am currently upgrading a bunch of modules in my Perl installation (Debian stretch, 64 bit, Perl 5.24.1). I opened the CPAN shell (perl -MCPAN -e shell) and tried to install Net::Ping (install Net::Ping).
Download and make went well, but the tests failed, presumably due to the following line:
t/501_ping_icmpv6.t .... icmp socket error - Bad file descriptor at t/501_ping_icmpv6.t line 49.
t/501_ping_icmpv6.t .... Dubious, test returned 9 (wstat 2304, 0x900)
As a consequence, the module did not get installed. I circumvented the problem by typing fforce install Net::Ping in the CPAN shell, but this is not satisfactory because real errors then will not be detected either.
The source of the error: On this box, IPv6 is disabled (I am doing this regularly on many of our and our clients' machines).
While I perfectly understand that the IPv6 tests fail if IPv6 is globally disabled, I think that this should be no reason to refuse installation. It would be very nice if you could change this. And by the way, the problem probably exists the other way around as well (I did not test, though): What happens on a box where IPv4 is disabled and only IPv6 enabled?
Thank you very much for your great work, your time and effort!
Regards,
Binarus
The text was updated successfully, but these errors were encountered:
I am currently upgrading a bunch of modules in my Perl installation (Debian stretch, 64 bit, Perl 5.24.1). I opened the CPAN shell (
perl -MCPAN -e shell
) and tried to install Net::Ping (install Net::Ping
).Download and make went well, but the tests failed, presumably due to the following line:
As a consequence, the module did not get installed. I circumvented the problem by typing
fforce install Net::Ping
in the CPAN shell, but this is not satisfactory because real errors then will not be detected either.The source of the error: On this box, IPv6 is disabled (I am doing this regularly on many of our and our clients' machines).
While I perfectly understand that the IPv6 tests fail if IPv6 is globally disabled, I think that this should be no reason to refuse installation. It would be very nice if you could change this. And by the way, the problem probably exists the other way around as well (I did not test, though): What happens on a box where IPv4 is disabled and only IPv6 enabled?
Thank you very much for your great work, your time and effort!
Regards,
Binarus
The text was updated successfully, but these errors were encountered: