Closed celogeek closed 10 years ago
I'm about half-way through fixing this. Stay tuned :)
great ! I stay tuned :)
How's this one coming along? Still getting this for Dist::Zilla::PluginBundle::DAGOLDEN, among others.
This is fixed in the 0.097_01 development release I shipped yesterday. It includes has a lot of other changes too, so I'm being cautious about making it into a production release.
Yes, this problem is indeed gone now. Seem to be having a change in behavior problem with pintod in the 0.097_03 release, where if you start it for a particular stack, cpanm pointed at it still seems to look at the default stack.
Seem to be having a change in behavior problem with pintod in the 0.097_03 release, where if you start it for a particular stack, cpanm pointed at it still seems to look at the default stack.
I don't understand what you mean. Can you elaborate on that?
Pinto 0.099 has shipped to CPAN, so I'm going to close this. @gmarler, If there's a problem with pintod, can you please open a new issue for that? Thanks.
When I try to add Dist::Zilla::Plugin::Test::Compile,
We fall on this : Parsing Dist::Zilla::Plugin::Conflicts : >= 0.10, != 0.11 in /usr/local/perlbrew/perls/perl-5.18.1/lib/site_perl/5.18.1/Pinto/PackageExtractor.pm at line 115
Here the stack trace