Hi Steffen, > Just an intermediate update: > > Some of the test reports I sent yesterday night are already visible, others > not (why?). > > In particular, I sent: > > # Generated by CPAN::Reporter 1.1708 > test PASS Carp-Clan-6.00 (perl-5.10.1) MSWin32-x86-multi-thread 5.1 > test PASS Bit-Vector-7.1 (perl-5.10.1) MSWin32-x86-multi-thread 5.1 > test PASS Date-Calc-6.0 (perl-5.10.1) MSWin32-x86-multi-thread 5.1 > test PASS Date-Pcalc-6.0 (perl-5.10.1) MSWin32-x86-multi-thread 5.1 > test PASS Data-Locations-5.5 (perl-5.10.1) MSWin32-x86-multi-thread 5.1 > test PASS Math-MatrixBool-5.8 (perl-5.10.1) MSWin32-x86-multi-thread 5.1 > test PASS Set-IntRange-5.2 (perl-5.10.1) MSWin32-x86-multi-thread 5.1 > test PASS Date-Calc-6.1 (perl-5.10.1) MSWin32-x86-multi-thread 5.1 > test PASS Date-Pcalc-6.1 (perl-5.10.1) MSWin32-x86-multi-thread 5.1
All these are in the system. However, as mentioned previously, it can take several days for some pages to be updated. > Certainly, if the software was able to extract the Perl version from > the two reports above, then it should have been able to do so also on > the others - presuming that the other reports would not be any > different in that respect, coming from exactly the same Perl, the > same CPAN::Reporter, and the very same CPAN.pm session! Not necessarily. If the report exceeds the byte limit it gets truncated. All the perl -V data is at the end, which is the primary source of discovery for the perl version. Note this is a limit of the NNTP mail server, and one reason why we want to move to a HTTP submission based system. When I get free time, I go through the oddities and try and improve the regex or hand edit the version if I can. But it's time consuming :) Cheers, Barbie. -- Birmingham Perl Mongers <http://birmingham.pm.org> Memoirs Of A Roadie <http://barbie.missbarbell.co.uk> CPAN Testers Blog <http://blog.cpantesters.org> YAPC Conference Surveys <http://yapc-surveys.org>
