Re: new releases of cpan-openbsd-smoker
[email protected] (James E Keenan)
| Newsgroups | perl.cpan.testers.discuss |
|---|---|
| Message-ID | <[email protected]> |
On 5/18/22 16:12, Slaven Rezic wrote: >> James E Keenan <[email protected] <mailto:[email protected]>> hat am >> 18.05.2022 16:26 geschrieben: >> > [...] >> The problem I've been encountering recently is that the >> Task-CPAN-Reporter stack includes IO-Socket-SSL, and the CPAN maintainer >> of IO-Socket-SSL has given up on trying to maintain that module on >> OpenBSD. See, for example, >> https://github.com/noxxi/p5-io-socket-ssl/issues/115 >> <https://github.com/noxxi/p5-io-socket-ssl/issues/115>. While the OpenBSD >> people do a good job of maintaining their *port* of IO-Socket-SSL via >> patches, that port is only intended to work with the *system* perl in a >> given version of OpenBSD. If you try to use 'cpan' or 'cpanm' to >> install something that has IO::Socket::SSL in its dependency chain >> (e.g., Task::CPAN::Reporter), you will get test failures. > Actually I think there's no need to use Task::CPAN::Reporter. Just > install plain CPAN::Reporter and make sure to use a http URL in your > .cpanreporter/config.ini. > Slaven to the rescue once again! Going back a decade or more, when I was first attempting to submit reports to CPANtesters, I found CPAN::Reporter very difficult to use consistently. Granted, that probably reflected my own ignorance more than the module. Nonetheless, I held off on CPANtesters for many years. In recent years, when I've had access to this FreeBSD server, I've installed quite a few VMs and -- on the FreeBSD servers in particular -- I found that Task::CPAN::Reporter Just Worked(TM). So that's why I tried it in my OpenBSD VMs as well, and for several years it Just Worked there, too. So I never had reason to think that I should "downgrade" from https to http in my .cpanreporter/config.ini. http://metabase.cpantesters.org/tail/log.txt is now being populated with reports from this OpenBSD-6.9 VM and a perl somewhere between 5.35.10 and 5.35.11. So I look forward to submitting several hundred CPANtester reports once perl-5.36.0-RC0 comes out. Thank you very much. Jim Keenan