Skip Menu |

This queue is for tickets about the Type-Tiny CPAN distribution.

Report information
The Basics
Id: 91468
Status: resolved
Priority: 0/
Queue: Type-Tiny

People
Owner: Nobody in particular
Requestors: dsteinbrunner [...] pobox.com
Cc:
AdminCc:

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



Subject: test failure
Log attached. I have 0.026 currently installed but when I try to reinstall it now it fails in a similar fashion so I assume this is an issue related to working with a dependance that has been updated since.
Subject: build.log
Download build.log
application/octet-stream 6.2k

Message body not shown because it is not plain text.

People on CPAN testers seem to be having the same problem. Can I ask what versions of MooseX::Types and MooseX::Types::Common you have installed?
Subject: Re: [rt.cpan.org #91468] test failure
Date: Tue, 17 Dec 2013 16:52:01 -0500
To: <bug-Moops [...] rt.cpan.org>
From: David Steinbrunner <dsteinbrunner [...] pobox.com>
On 12/17/13 4:46 PM, "Toby Inkster via RT" <bug-Moops@rt.cpan.org> wrote: Show quoted text
><URL: https://rt.cpan.org/Ticket/Display.html?id=91468 > > >People on CPAN testers seem to be having the same problem. > >Can I ask what versions of MooseX::Types and MooseX::Types::Common you >have installed?
I keep the install reported this from on the bleading edge for modules so they are the latest sable versions. -- David Steinbrunner
It looks like in recent releases of MooseX::Types, one can no longer simply refer to a type by its full name: perl -MMooseX::Types::Common::String -E'say(MooseX::Types::Common::String::NonEmptyStr)' works with MooseX::Types 0.35, not not 0.39. This is possibly because of the switch to namespace::autoclean.
I think upgrading to Type-Tiny-0.035_01 ought to fix this. I'm going to move this ticket to Type-Tiny.
From: dsteinbrunner [...] pobox.com
On Tue Dec 17 18:06:20 2013, TOBYINK wrote: Show quoted text
> I think upgrading to Type-Tiny-0.035_01 ought to fix this. I'm going > to move this ticket to Type-Tiny.
upgraded to the dev release of Type-Tiny, but Moops is not happy yet.
Subject: build.log
Download build.log
application/octet-stream 6.3k

Message body not shown because it is not plain text.

I've the same test failure, subscribing to get notified about a fixed version.
OK, the key it seems is to avoid MooseX::Types::Common 0.001011. Either use an earlier version, or upgrade to 0.001012. The new release of Moops should now skip particular tests if it detects MooseX::Types::Common 0.001011 is installed. This version is also now listed as a conflict in Moops' META.json: https://metacpan.org/source/TOBYINK/Moops-0.028/META.json#L94 Type::Parser also includes workarounds for this issue.
Subject: Re: [rt.cpan.org #91468] test failure
Date: Wed, 18 Dec 2013 16:21:59 -0500
To: <bug-Type-Tiny [...] rt.cpan.org>
From: David Steinbrunner <dsteinbrunner [...] pobox.com>
On 12/18/13 3:58 PM, "Toby Inkster via RT" <bug-Type-Tiny@rt.cpan.org> wrote: Show quoted text
><URL: https://rt.cpan.org/Ticket/Display.html?id=91468 > > >OK, the key it seems is to avoid MooseX::Types::Common 0.001011. Either >use an earlier version, or upgrade to 0.001012. > >The new release of Moops should now skip particular tests if it detects >MooseX::Types::Common 0.001011 is installed. This version is also now >listed as a conflict in Moops' META.json: > >https://metacpan.org/source/TOBYINK/Moops-0.028/META.json#L94 > >Type::Parser also includes workarounds for this issue.
T/TO/TOBYINK/Moops-0.028.tar.gz now installs given that its dependancies are the now current releases. -- David Steinbrunner
I've released a new stable Type::Tiny, and I think this is sorted out now. I'll keep an eye on the issue though, as MooseX::Types and several key MooseX::Types-based type libraries have been seeing some new releases with changes around namespace::autoclean after I brought this issue to ETHER's attention.