in reply to PPM mis-identifying / failing to upgrade some module upgrade candidates
I see the same problem. One pattern that emerges is the following. The ppm utility comes configured with two ActiveState repositories: "ActiveState PPM2 Repository" and "Activestate Package Repository". The problem seems to lie in whether or not a given package is in one or both repositories:
As a poor workaround, if within the ppm shell you turn off the "Activestate Package Repository" using the rep off command, then, for example, CGI-Enurl would be reported as up-to-date. However, there may be packages within the "Activestate Package Repository" that are not in the "ActiveState PPM2 Repository", so doing this may result in some available packages not being found. As well, searches may be slower without the "Activestate Package Repository", as this uses a database lookup.
There's a ppm mailing list available which would be a good forum to report this (it's a low-volume list, and ActiveState developers regularly monitor it).
|
|---|
| Replies are listed 'Best First'. | |
|---|---|
|
Re^2: PPM mis-identifying / failing to upgrade some module upgrade candidates
by terra incognita (Pilgrim) on Oct 14, 2005 at 16:08 UTC | |
by randyk (Parson) on Oct 14, 2005 at 16:24 UTC |