Skip Menu |

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

Report information
The Basics
Id: 91578
Status: open
Priority: 0/
Queue: Catalyst-Plugin-DefaultEnd

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

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



CC: JJNAPIORK [...] cpan.org
Subject: Fails with Catalyst-Runtime-5.90052
As per subject. Sample fail report: http://www.cpantesters.org/cpan/report/9929cb66-69bc-11e3-bdf9-a4690c5d3a7d Much too late I discover the DEPRECATED notice. So if the module has been deprecated 2009 and now got borken by Catalyst anyway, it's probably necessary to decide whether it has to stay on CPAN or not and how to deal with fail reports that trickle in. Anyway, I have verified that downgrading to Catalyst-Runtime-5.90051 "fixes" things, so that ->log is already working when the plugin is loaded. HTH && Thanks,
CC: "jjnapiork [...] cpan.org" <jjnapiork [...] cpan.org>
Subject: Re: [rt.cpan.org #91578] Fails with Catalyst-Runtime-5.90052
Date: Sun, 22 Dec 2013 08:17:32 -0800 (PST)
To: "bug-Catalyst-Plugin-DefaultEnd [...] rt.cpan.org" <bug-Catalyst-Plugin-DefaultEnd [...] rt.cpan.org>
From: John Napiorkowski <jjn1056 [...] yahoo.com>
Well, that plugin is deprecated but you did reveal a regression.  I can't vouch for how long that plugin will continue to work, but there's a new stable on the way to cpan with a fix.  Thanks for the report! John On Sunday, December 22, 2013 7:39 AM, Andreas Koenig via RT <bug-Catalyst-Plugin-DefaultEnd@rt.cpan.org> wrote: <URL: https://rt.cpan.org/Ticket/Display.html?id=91578 > As per subject. Sample fail report: http://www.cpantesters.org/cpan/report/9929cb66-69bc-11e3-bdf9-a4690c5d3a7d Much too late I discover the DEPRECATED notice. So if the module has been deprecated 2009 and now got borken by Catalyst anyway, it's probably necessary to decide whether it has to stay on CPAN or not and how to deal with fail reports that trickle in. Anyway, I have verified that downgrading to Catalyst-Runtime-5.90051 "fixes" things, so that ->log is already working when the plugin is loaded. HTH && Thanks,