Well, it does appear to be the problem with that particular package, and a few of the others. I am still digging around getting all the info together on which packages this is the problem--and which ones have valid PPD's but still error out (some still seem to).

On the plus side, I did figure out where it's getting the version information from: There were a couple XML and PPM files amongst all the PPDs.. The XML includes what looks like each of the full SOFTPKG entries for the entire repository (this is what normally goes in each PPD, right?), and the PPM files have summary information (I'm guessing to aid in searching).

I am starting to wonder if maybe this particular package problem is related to how and when the trouchelle repository (and possibly others) update their stores; The information seems disjoint between the XML and PPM files. For example, the ConfigReader-Simple package lists in one as version 1.24, and in another as 1.25. (The site seems to have the 1.23, 1.24 and 1.25 ZIP files, as well. Just no valid PPD file for them.)

Is there some perlmonk out there who can confirm this.. or better yet, suggest some solution? I am wary of fiddling with the internals of the PPM code--But it would certainly be nice if I could modify PPM to print the error, then continue processing the rest of the commands instead of dumping me back to the command-line with only half the packages processed. (Maybe it's even possible to "build" a valid PPD from the package.xml file? It looks like a complete SOFTPKG entry..)

One more last minute note, again as I'm writing this (I keep working in a command window as I write ;-)).. Some of the packages which previously processed OK are now showing this error, and some of the ones which previously had errors are now working OK. Just more reason I'm starting to think it's a problem with de-sync during the rep's update process..

In reply to Re^2: Problems with "PPM::PPD::init: not a PPD and not a file" by Casteele
in thread Problems with "PPM::PPD::init: not a PPD and not a file" by Casteele

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.