On Mon May 27 03:05:34 2013, andreas.koenig.7os6VVqR@franz.ak.mind.de wrote: > My smokers, as you may know, are focussed on running blead against a > substantial part of the CPAN. > > *Often* I hit problems stemming from Module::CoreList. > > Today this one: BOOK/Devel-TraceUse-2.09.tar.gz fails with blead with > the diagnostics: > > # Module::CoreList 2.91 doesn't know about Perl 5.019001 > > Let's verify: > > /home/src/perl/repoperls/installed-perls/perl/v5.19.0-253- > gd4fe707/9980/bin/perl -MModule::CoreList -le 'print > Module::CoreList->find_version("5.019001") ? "ok" : "not ok"' > not ok > > > I suppose there must be some written guidelines somewhere what has to > happen before a blead version number may be bumped, right? > The relevant function in Module::CoreList is this: ##### sub find_version { my $v = shift; $v = shift if eval { $v->isa(__PACKAGE__) }; return $version{$v} if defined $version{$v}; return undef; } ##### (While we're at it, what's that 'return undef' doing there? Shouldn't 'return' be better practice?) What are the contents of %version at the relevant point? Running a program through the debugger, I call 'x [ sort {$a <=> $b} keys %version ]' and see that the last entries are: ##### 96 5.017011 97 5.018 98 5.018000 99 5.019000 100 5.019 ##### So there's no entry for 5.019001, which explains the error message. But it's not clear to me how %version gets populated. I tried adding entries for '5.019001' to %released and %delta in dist/Module-CoreList/lib/Module/CoreList.pm, but that did not clear up the problem. Does anyone see how %version in CoreList.pm gets populated? If we knew that, then we could probably locate a place in the release procedures to bump the version appropriately. Thank you very much. Jim Keenan --- via perlbug: queue: perl5 status: new https://rt.perl.org:443/rt3/Ticket/Display.html?id=118195Thread Next