On Sun, May 17, 2009 at 11:27:25AM -0500, Raphael Geissert wrote: > Bart Martens wrote: > > > On Sat, May 16, 2009 at 10:35:08PM -0500, Raphael Geissert wrote: > >> > >> 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 ? > > > SELECT name FROM pkgs WHERE watch_warn LIKE '%search.cpan%403%'; > name > -------------------------------------- > libcrypt-gpg-perl > libuniversal-moniker-perl > libimage-info-perl > libclass-dbi-plugin-retrieveall-perl > libclass-base-perl > libcgi-untaint-perl > libthreads-perl > libthreads-shared-perl > libnet-dpap-client-perl > libclass-dbi-pager-perl > libclass-dbi-loader-perl > libio-stty-perl > libclass-trigger-perl > dist > > (yes, that's a source package name)
1242398316 libcrypt-gpg-perl 1.52 1.63 outdated 1242414001 libuniversal-moniker-perl 0.08 0.08 OK 1242444931 libimage-info-perl 1.28 1.28 OK 1242444214 libclass-dbi-plugin-retrieveall-perl 1.04 1.04 OK 1242444183 libclass-base-perl 0.03 0.03 OK 1242408770 libcgi-untaint-perl 1.26 1.26 OK 1242446211 libthreads-perl 1.71 1.72 outdated 1242446213 libthreads-shared-perl 1.27 1.28 outdated 1242445508 libnet-dpap-client-perl 0.26 0.26 OK 1242400576 libclass-dbi-pager-perl 0.08 0.08 OK 1242444199 libclass-dbi-loader-perl 0.34 0.34 OK 1242410101 libio-stty-perl 0.02 0.02 OK 1242396578 libclass-trigger-perl 0.13 0.13 OK 1242405485 dist 3.5-29 3.5-29 OK Yes temporary problem. (The list above was produced with "watchupstream".) Can you modify the rescanning so that such 403's are rescanned sooner than with the next total rescan every 4 days ? Note that such 403's may (I'm guessing) repeat to be 403's as long as they're in the total rescan. Maybe semi-automatically/manually rescan selectively and inject the successful results at some convenient point in the data flow to the qa-developer-pages ? It could be an effectively working workaround until DEHS2 is released. > > >> > Displaying the old version on the > >> > qa-developer-pages until the next rescan is successful. > >> > >> Something similar is planned for DEHS2 > > > > Release in 2009 ? > > Of course; but some major work needs to be done in uscan first. I understand that major work may be required for DEHS2, but I don't think that uscan needs any changes to have the old rescan results displayed on the qa-developer-pages until the next rescan is successful. Any chance that this gets planned a bit earlier, so before the entire 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. > > > > 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 ? > > > > I'm not fearing a permanent ban, but for example berlios' ban lasts a day. So for Berlios re-scanning selectively briefly after the failed scans to deal with temporary errors could be done after one day, obviously. Regards, Bart Martens -- To UNSUBSCRIBE, email to debian-qa-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
