Skip Menu |

Preferred bug tracker

Please visit the preferred bug tracker to report your issue.

This queue is for tickets about the Dist-Zilla-Plugin-TaskWeaver CPAN distribution.

Report information
The Basics
Id: 85986
Status: rejected
Priority: 0/
Queue: Dist-Zilla-Plugin-TaskWeaver

People
Owner: Nobody in particular
Requestors: DOY [...] cpan.org
Cc:
AdminCc:

Bug Information
Severity: (no value)
Broken in: (no value)
Fixed in: (no value)



Subject: can't use three-part versions properly
Putting this in the task file: =pkg App::ForkProve 0.2.0 results in a warning from Makefile.PL: Unparsable version 'v0.2.0' for prerequisite App::ForkProve at Makefile.PL line 115. which I assume means that it just ignores the version.
Also, this doesn't work either: =pkg App::ForkProve 0.004005 which results in: Warning: prerequisite App::ForkProve 0.004005 not found. We have v0.4.7.
First off: I am rejecting this ticket in part because I can't reproduce it, but also because it's the only ticket in the RT queue and I want to switch to GitHub issues. *** If you can show me how to reproduce it, I would love it if you could do that by submitting a GH issue instead of re-opening this. Thanks! *** I tried to switch things in my task Pod to three-part versions and everything worked end to end. Can you still reproduce this? If so, does it go away if you update your EUMM? Thanks for the report. -- rjbs
Yeah, looks like this was an EUMM bug, fixed in 6.68 (5.18 ships with 6.66). Specifying versions like 0.004005 still doesn't work though, but I'm not sure if that should actually be a bug or not (and if it is, it's not a bug in TaskWeaver).
On Sat Jun 08 12:07:11 2013, DOY wrote: Show quoted text
> Putting this in the task file: > > =pkg App::ForkProve 0.2.0 > > results in a warning from Makefile.PL: > > Unparsable version 'v0.2.0' for prerequisite App::ForkProve at > Makefile.PL line 115. > > which I assume means that it just ignores the version.
The very latest version of ExtUtils::MakeMaker (6.72) has some fixes related to vstring versions. Does upgrading fix the issue? If so you may have to configure_require a more recent version of MakeMaker… Leon
FWIW, I have added in 981b7aeb168425b2b5f7ee470d1ae36cdf5aad0c a note that three-part versions may require a new EUMM in configure_requires. -- rjbs