Thanks for your message.
I was one of many people that helped maintain that package, and if I
recall correctly, I was the one that decided to remove
Catalyst::Plugin::XMLRPC from the bundle, because it had problems
building. If I am correct, then that means that for quite some time
(in testing and unstable), the upgrade path for existing users has
already been broken (and I don't have enough time to check at the
moment, but hopefully I also noted that in Debian.NEWS).
So: I think it's best to package it seperately, and I will do so when
I have some free time (or perhaps another member of the group can pick
Thanks for letting us know. It always helps to coordinate these sorts
of things with upstream authors.
2010/7/14 Jose Luis Martínez Torres <firstname.lastname@example.org>:
> I'm Jose Luis Martinez (JLMARTIN from CPAN). I'm now co-maint for Catalyst::Plugin::XMLRPC. This plugin was in the Etch and Lenny libcatalyst-modules-perl, but not in squeeze, I suppose because it was broken with Catalyst 5.8.
> I wanted to inform that this plugin is now running under a devel environment with Debian squeeze, so feel free to repackage it in libcatalyst-modules-perl, or as I read in the bugs database, package it separately. I think it would be good to include it so users have a clean upgrade path when going from Lenny to Squeeze.
> Best Regards,
> Jose Luís Martínez
> pkg-perl-maintainers mailing list