Skip Menu |

This queue is for tickets about the MooseX-Getopt CPAN distribution.

Report information
The Basics
Id: 88627
Status: resolved
Priority: 0/
Queue: MooseX-Getopt

People
Owner: ether [...] cpan.org
Requestors: ANDK [...] cpan.org
Cc:
AdminCc:

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



Subject: Fails with Moose 2.1100-TRAIL
As per subject. You probably know better than me but in case you didn't it's better I tell you than the other way round. Cheers,
On 2013-09-12 03:52:49, ANDK wrote: Show quoted text
> As per subject. > > You probably know better than me but in case you didn't it's better I > tell you than the other way round. > > Cheers,
Do you have a stack trace handy? The only issue with Moose-2.1100 that I'm aware of is due to a use of a new Class::MOP deprecation in MooseX::Role::Parameterized (which MXGO uses), and sartak has now released a fixed MXRP -- so other than bumping the dependency in MXGO, there isn't anything to do here. I'll leave this ticket open for now in case there is something else afoot.
Subject: Fails with Moose 2.1100-TRIAL
I can certainly update MXGO to not fail on upstream warnings -- I'll do that tonight.
CC: ANDK [...] cpan.org
Subject: Re: [rt.cpan.org #88627] Fails with Moose 2.1100-TRAIL
Date: Thu, 12 Sep 2013 21:06:09 +0200
To: bug-MooseX-Getopt [...] rt.cpan.org
From: Andreas Koenig <andreas.koenig.7os6VVqR [...] franz.ak.mind.de>
"Karen Etheridge via RT" <bug-MooseX-Getopt@rt.cpan.org> writes: Show quoted text
> Do you have a stack trace handy?
I had not checked, so now I'm surprised to find two different ones: Name "Config::Any::YAML::NO_YAML_XS_WARNING" used only once: possible typo at t/112_configfile_constructor_arg.t line 15. # Failed test 'no (unexpected) warnings (via END block)' # at t/112_configfile_constructor_arg.t line 0. # Looks like you failed 1 test of 3. t/112_configfile_constructor_arg.t .. Dubious, test returned 1 (wstat 256, 0x100) Failed 1/3 subtests Most reports skip this test when MooseX::SimpleConfig is not available. The other one I found on cpantesters as in http://www.cpantesters.org/cpan/report/34282381 -- andreas
These two failures should be resolved with 0.58.