in reply to PPM has module but BugZilla says it's missing

The official line from BugZilla is:

when PPM downloads several packages, and one of them is inaccessible (e.g. because the versions do not match), it immediately stops downloading remaining packages, and starts installing the ones already downloaded. What happens is that these packages are downloaded in a pretty random order, and so dependencies may not have been downloaded before the failure and PPM doesn't even notice that it forgot to install dependencies first.
The workaround got me further down the track, but then failed, with something else complaining about missing modules. However, following the official line wasn't getting me very far, either. The point is that I was not installing multiple modules at any time. I was following the instructions and adding the modules one by one from the command line. One of the problem modules, Template Toolkit, seems to my unskilled eye to have no dependencies.

Extensive Gargling has got me working. The problem seems to be with the Windows registry. Having updated Perl several times the various versions seem to have left confusing stuff behind in the registry. I therefore uninstalled all versions of Perl, and ran ERUNT and NTREGOPT to clean the registry. From this point, a clean install of Perl 5.12 (which I had tried unsuccessfully before) gave me a system that installed the essential modules and got Bugzilla running. However, some of the modules needed for optional features - SOAP-Lite, HTML-Scrubber, TheSchwartz, Daemon-Generic and mod_perl - display the same behaviour previously described - they are installed, but Bugzilla can't find them.

I report this in the hope that it may help anyone else experiencing the same problem or be of interest.

Regards & thanks to all who helped,

John Davies


Comment on Re: PPM has module but BugZilla says it's missing - redux
Re^2: PPM has module but BugZilla says it's missing - redux
by Anonymous Monk on Mar 17, 2011 at 10:25 UTC
    I have the same cant find any work around... How were u able to do it Davies. Sam Chughtai

      As I said,

      The problem seems to be with the Windows registry. Having updated Perl several times, the various versions seem to have left confusing stuff behind in the registry. I therefore uninstalled all versions of Perl, and ran ERUNT and NTREGOPT to clean the registry. From this point, a clean install of Perl 5.12 (which I had tried unsuccessfully before) gave me a system that installed the essential modules and got Bugzilla running.
      But this may not be your problem. If so, I can't help. You might also want to try other registry cleaners.

      Regards,

      John Davies