So have you addressed the responder? That user is the one that had failures in the test. Working on one system (or even one set of systems) does not mean that it is a good patch. That is the reason for cpantesters and the like.

My point is this: the documentation that you have provided does not (IMO) justify taking over the distribution from the original author. Taking over the distribution is a very large mallet when a finishing hammer may be all that is necessary. A single instance of a patch not being applied is not (again, IMO) justification for taking over a distribution.

However, I am not saying that the module should not be taken over. Just that the information you have provided does not justify it, and that there may be a better, less confrontational way of addressing it. Perhaps you have already attempted one or more other methods, but just not demonstrated that you have.

Have you tried applying the patch and running the tests?

The responders error is as a result of running the current C::P::Log::Handler with the current Log::Handler. If he applies the patch his error message will go away, along with the Catalyst deprecation warning.

I have no wish to take over the module, and will gladly hand it over to whoever shows an interest in maintaining it. The author doesn't appear to be responding to RT tickets or emails via his CPAN address. As per the referenced instructions I've copied modules@perl.org on the last RT update (which demonstrates that I have attempted the required methods of contacting the author), and this is the public announcement.

I now wait in the hope that the module author is on holiday and will be back soon.