Skip Menu |

This queue is for tickets about the Catalyst-Runtime CPAN distribution.

Report information
The Basics
Id: 64730
Status: resolved
Priority: 0/
Queue: Catalyst-Runtime

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

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



Subject: Fails with Moose/Class::MOP 1.9902
Can you please let me know (if you know, that is), who should get reports about breakages like this. My impression is I could report a dozen or three of them but I have no idea how useful and/or welcome they would be. You are familiar with the Moose Population, can you shed some light, please? THX,
Lots of stuff fails with Moose 1.9902, because of bugs in that version. How's it looking with 1.9904?
JASONMAY/Term-VT102-Incremental-0.03.tar.gz currently has 5 fails with 1.9904 and no fails with other Moose versions.
On Thu Mar 10 22:18:39 2011, ANDK wrote: Show quoted text
> JASONMAY/Term-VT102-Incremental-0.03.tar.gz currently has 5 fails with > 1.9904 and no fails with other Moose versions.
JASONMAY/Term-VT102-Incremental-0.04.tar.gz now passes on 1.9904 (it is somewhat surprising it passed on 1.24)
If nobody objects discussing effects of Moose development versions to non-Catalyst modules in a Catalyst ticket... Indeed I don't see many modules negatively affected by 1.9904. BINGOS/POE-Component-Github-0.08.tar.gz seems to be a candidate but I'm not sure. On NOBODY/KinoSearchX-Simple-0.08.tar.gz I have one fail. These are just two easy picks, there may other candidates be hidden.
On Thu Jan 13 02:01:42 2011, ANDK wrote: Show quoted text
> Can you please let me know (if you know, that is), who should get > reports about breakages like this. My impression is I could report a > dozen or three of them but I have no idea how useful and/or welcome they > would be. > > You are familiar with the Moose Population, can you shed some light,
please? Theoretically, the Moose guys test a list of their downstream dependents (including Catalyst) as part of the release process, so this shouldn't happen. :/ As it's now fixed, I'm going to resolve this, thanks however for letting us know.