[Date Prev][Date Next] [Thread Prev][Thread Next] [Date Index] [Thread Index]

Bug#465434: qa.debian.org: Uscan Errors processing Watch File



I though I had replied to this bug long time ago.

Dmitry E. Oboukhov wrote:
> Other packages are processed normally. Only 'iat' consistently shows
> error. Perhaps the problem with the firewall (OUTPUT to https)?

Actually, the problem is that berlios keeps on blocking alioth as soon as a
few requests are made (I guess they look for a U-A that looks like a
browser, and if it isn't then they are too sensitive to the number of
requests in a given period of time.)

FTR there are only 73 watch files that match the LIKE '%berlios%' query,
they aren't that many.

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.

> 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)

> 
> 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

> 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.

Regards,
-- 
Raphael Geissert - Debian Maintainer
www.debian.org - get.debian.net





Reply to: