Bug#465434: qa.debian.org: Uscan Errors processing Watch File
On Sat, May 16, 2009 at 10:35:08PM -0500, Raphael Geissert wrote:
> Bart Martens wrote:
> >
> > But, there's more than "iat". For example, the package libnet-cidr-perl
> > is marked with "Error" on
> > http://qa.debian.org/developer.php?login=bartm@debian.org&ordering=1 and I
> > don't see why.
>
> Checking this too late, please attach the information provided by DEHS for
> that package when you notice an error.
Package with "Error": libclass-dbi-pager-perl
DEHS information:
| Uscan errors:
| uscan.pl warning: In watchfile /tmp/libclass-dbi-pager-perl_watchsC1Jtu, reading webpage
| http://search.cpan.org/CPAN/authors/id/M/MI/MIYAGAWA/ failed: 403 Forbidden
>
> > Maybe there were temporary network problems, or maybe
> > cpan.org doesn't like the scanning for multiple packages in a row
> > (hammering).
>
> cpan uses many many mirrors, and some are not up to date, not properly
> setup, or cause many sort of weird errors. Since there's no easy way to
> tell what mirror uscan connected to it is impossible for me to report them
> to cpan. Random example from no_upstream.html:
>
> uscan.pl warning: In watchfile /tmp/libclass-trigger-perl_watchyKgKAS,
> reading webpage http://search.cpan.org/CPAN/authors/id/M/MI/MIYAGAWA/
> failed: 403 Forbidden
> (there are many 403s)
Can you send me a list of those ?
>
> >
> > Possible approaches to solve this: Adding some sleep calls between
> > consecutive scans on the same website.
>
> Different watch files are checked on different days and times during the
> week; the archive hasn't changed enough to make that trick work again since
> the release (which made me freeze DEHS for over a week.)
>
> > Displaying the old version on the
> > qa-developer-pages until the next rescan is successful.
>
> Something similar is planned for DEHS2
Release in 2009 ?
>
> > Re-scanning selectively briefly (minutes/hours) after the failed scans to
> > deal with temporary errors.
>
> No, that won't happen as it would be easier to get alioth banned.
Isn't waiting an hour or 2 and try again exactly the approach to work around
such temporary ban ? Or do you fear a permanent ban ?
Regards,
Bart Martens
Reply to: