Bug #72845 for Module-Release: Distro version parsing fails with PBP-style three-part version numbers

Wed Nov 30 10:36:30 2011 WULEE [...] cpan.org - Ticket created

Subject:

Distro version parsing fails with PBP-style three-part version numbers

So, given a version declaration in a module Foo like this: use version; our $VERSION = qv('0.1.0'); # or even '1.0' Module::Build creates a distro tarball: Foo-v0.1.0.tar.gz Which Module::Release happily mis-parses as 1.0, and modules appear on CPAN with an unintended version. I've sent you a pull-request on github with a tentative fix and some extra tests. My fork is at https://github.com/wu-lee/module-release/

Wed Nov 30 13:33:48 2011 bdfoy [...] cpan.org - Correspondence added

This is patched in 2.05_07.

Wed Nov 30 13:33:49 2011 The RT System itself - Status changed from 'new' to 'open'

Wed Nov 30 13:33:49 2011 bdfoy [...] cpan.org - Status changed from 'open' to 'patched'

Mon Dec 19 11:24:06 2011 WULEE [...] cpan.org - Correspondence added

On Wed Nov 30 13:33:48 2011, BDFOY wrote: Show quoted text

> This is patched in 2.05_07.

Thanks, I tried the patched version and found that there is still code in the M::R::SVN/Git which thwarts my fix. Since it's obstructing my use of a git repo, and I don't use Subversion, I've made an initial attempt to fix M::R::Git here: https://github.com/wu-lee/module--release--git/tree/parse-three-part-versions However, the same problem exists in M::R::SVN, and the fix could be usefully pushed into M::R and shared. See also RT#73364 for Module::Release::Git.

Mon Dec 19 11:24:07 2011 The RT System itself - Status changed from 'patched' to 'open'

Mon Dec 19 11:41:48 2011 bdfoy [...] cpan.org - Status changed from 'open' to 'patched'