Let's see what version.pm thinks:
$ perl -Mversion -e 'warn version->new("0.01") > version->new("v0.2.2")'
1 at -e line 1.
So 0.01 is newer than v0.2.2.
Why? If we numify things, then it's clear:
$ perl -Mversion -e 'warn version->new("0.01")->numify; warn version->new("v0.2.2")->numify'
0.010 at -e line 1.
0.002002 at -e line 1.
So what's the lesson here? Never switch from one-dot versions to two-dot versions, unless you're very careful or increment the major version. If you want to stick to two-dot versions in this case, then you have at least to increment to v0.10.1.
Regards,
Slaven
On 2016-08-02 05:38:48, oklaspec@gmail.com wrote:
Show quoted text> Hi Slaven!
>
> Do you know why this old (0.01) version is latest while new (v0.2.2)
> version is uploaded.
>
> Thanks
>
> Serguei Okladnikov
>
> 2016-08-01 22:49 GMT+04:00 Slaven_Rezic via RT <
> bug-JSON-RPC2-AnyEvent-Client@rt.cpan.org>:
>
> > Mon Aug 01 14:49:52 2016: Request 116643 was acted upon.
> > Transaction: Ticket created by SREZIC
> > Queue: JSON-RPC2-AnyEvent-Client
> > Subject: Generated Makefile incompatible with GNU make?
> > Broken in: v0.2.2
> > Severity: (no value)
> > Owner: Nobody
> > Requestors: SREZIC@cpan.org
> > Status: new
> > Ticket <URL:
https://rt.cpan.org/Ticket/Display.html?id=116643 >
> >
> >
> > On Linux systems building the module fails:
> >
> >
> > Output from '/usr/bin/make':
> >
> > Makefile:523: *** target pattern contains no '%'. Schluss.
> >
> >
> > Looking at
> >
http://matrix.cpantesters.org/?dist=JSON-RPC2-AnyEvent-Client%200.01
> > it
> > seems that there are pass reports for BSD systems (usually using a
> > BSD make
> > variant) and MSWin32 (usually using dmake).
> >
> >
