I'm posting this as a follow-up to my original post as the original problem is listed there. Corion has got me past the first hurdle to the point where the modulino is indexed on CPAN and I have cleared up one minor issue. But the major issue of the test failures remains. The problem space has been narrowed down by Slaven Rezic (is he a Monk? If you read this, Slaven, many thanks) in issue 144972 (https://rt.cpan.org/Public/Bug/Display.html?id=144972). Excerpts:

The test suite is failing on systems where the perl used for the current build is not the first perl in path... Probably at some point $^X should be used to call the correct perl.
I'm pretty confident that it is something to do with the file in the bin directory, which is quite short:

#!/usr/bin/perl
use strict;
use warnings;
use FindBin qw($RealBin);
use File::Find;
use feature 'say';

find ({wanted =>\&wanted, follow => 1 }, ($RealBin . '/..', @INC));

sub wanted {
    if ($File::Find::name =~ m/App\/ipchgmon.pm$/) {
        # Changed from "perl" to "$^X" per Slaven Rezic's advice
        # in issue 144972. I wouldn't have got near this issue
        # on my own. Many thanks, Slaven.
        my $cmd = join " ", $^X, $File::Find::name, @ARGV;
        say qx($cmd 2>&1); 
        exit;
    }
}

[download]

Line 15, in the earlier versions, used perl instead of $^X and I hoped that this change would solve the missing modules problem. It doesn't. So I now have two problems. The first is how to use the "correct" perl. The second is how to test any solution on my machine. The only way I have is to upload and wait for the error reports, but this isn't the job of the CPAN testers. It's mine. Any advice on how to do that job would be greatly appreciated.

Regards,

John Davies

In reply to Re: Unable to release modulino to CPAN - still struggling by davies
in thread Unable to release modulino to CPAN by davies

Title:
Use:  <p> text here (a paragraph) </p>
and:  <code> code here </code>
to format your post, it's "PerlMonks-approved HTML":


  • Posts are HTML formatted. Put <p> </p> tags around your paragraphs. Put <code> </code> tags around your code and data!
  • Titles consisting of a single word are discouraged, and in most cases are disallowed outright.
  • Read Where should I post X? if you're not absolutely sure you're posting in the right place.
  • Please read these before you post! —
  • Posts may use any of the Perl Monks Approved HTML tags:
    a, abbr, b, big, blockquote, br, caption, center, col, colgroup, dd, del, details, div, dl, dt, em, font, h1, h2, h3, h4, h5, h6, hr, i, ins, li, ol, p, pre, readmore, small, span, spoiler, strike, strong, sub, summary, sup, table, tbody, td, tfoot, th, thead, tr, tt, u, ul, wbr
  • You may need to use entities for some characters, as follows. (Exception: Within code tags, you can put the characters literally.)
            For:     Use:
    & &amp;
    < &lt;
    > &gt;
    [ &#91;
    ] &#93;
  • Link using PerlMonks shortcuts! What shortcuts can I use for linking?
  • See Writeup Formatting Tips and other pages linked from there for more info.