Re: RM: libwordpress-xmlrpc-perl/testing -- ROM; Based on recent source changes, we believe the quality of code is poor.
Please ignore this mail, I now know how to deal with the situation. I
messed up because of two things:
1. I didn't notice reportbug said "testing (NOT unstable)"
2. reportbug on ftp.debian.org didn't mention the things available on
the ftpmaster_Removals Wiki page.
I plan to file a bug against reportbug to have this clarified, so
hopefully this will reduce misfiled issues (from us ignorant non-DDs)
on your end.
I apologize for this noise, please carry on :)
Cheers!
Jonathan
On Tue, Dec 8, 2009 at 12:17 AM, Jonathan Yu <jawnsy@cpan.org> wrote:
> Here are some reasons why:
>
> 1. We discussed this in the ITP for libleocharre-perl [0]; the whole
> idea of the LEOCHARRE:: modules is flawed in many ways, and also
> exports random symbols to the 'main' namespace with no way of stopping
> it from doing so.
>
> 2. The overhead involved with patching in the needed LEOCHARRE::
> features is probably going to be big in the long term
>
> 3. There is a critical security issue due to inclusion of WordPress' XMLRPC [1]
>
> 4. Low popcon score
>
> 5. Not in stable (only unstable and testing)
>
> [0] http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=559524
> [1] http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=559770
> [2] http://qa.debian.org/popcon.php?package=libwordpress-xmlrpc-perl
>
Reply to: