productreleasefinder is reporting ERRORs for cases we should accept as being perfectly normal, as we do not control the remote web sites or their contents:
2009-07-02 16:44:10 ERROR could not retrieve directory listing for /files/projects/uc_correios_quotes-6.x-1.x-dev.tar.gz/
-> http://launchpadlibrarian.net/28632704/bUt1BQGs6PMeL8PpvWzfeRGdQZ5.txt (HTTP Error 404: Not Found)
2009-07-02 18:02:09 ERROR Unable to parse version from http://alasal.be/bespinUpdates/0.1/backend.zip
2009-07-02 16:46:01 ERROR could not retrieve directory listing for /sourceforge/gsolaar/GSolaar-0.4.0.tar.gz/
-> http://launchpadlibrarian.net/28632750/bfMvmy3eqkPQgta7yjeBgYbRVJi.txt (HTTP Error 302: Moved Temporarily)
2009-07-02 18:02:27 ERROR could not retrieve directory listing for /svn/bzr/releases/
-> http://launchpadlibrarian.net/28634912/bnx1aGIoqZkSliVRYVYygLfiQW6.txt (HTTP Error 301: Moved Permanently)
2009-07-02 18:03:57 ERROR could not retrieve directory listing for /spycal/spycal-v1.1.zip/
-> http://launchpadlibrarian.net/28634927/3ubdUCEpZFhFR8fVGVlsu2dU81i.txt (HTTP Error 503: Service Unavailable)
Setting to high as this is an operational issue, and the sheer volume of output is causing genuine failures to be lost. In particular, buried in the output are errors where it looks like our version number checking is too strict or we are doing a bad job making version numbers sane. I mention this here, as perhaps we can't munge the version numbers which would also make these error messages just part of perfectly normal day to day operations:
2009-07-02 18:02:09 ERROR Unable to parse version from http://
2009-07-02 18:09:28 ERROR Unable to parse version from http://
2009-07-02 16:45:38 ERROR Could not successfully process URL http://
-> http://
)