[Date Prev][Date Next] [Thread Prev][Thread Next] [Date Index] [Thread Index]

Bug#559524: marked as done (ITP: libleocharre-perl -- Bundle of several modules in the LEOCHARRE:: namespace)



Your message dated Wed, 16 Dec 2009 23:28:00 -0500
with message-id <d1b732a70912162028q6caa2789g7f465ac16ae7c7c9@mail.gmail.com>
and subject line Removal of libwordpress-xmlrpc-perl
has caused the Debian Bug report #559524,
regarding ITP: libleocharre-perl -- Bundle of several modules in the LEOCHARRE:: namespace
to be marked as done.

This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.

(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact owner@bugs.debian.org
immediately.)


-- 
559524: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=559524
Debian Bug Tracking System
Contact owner@bugs.debian.org with problems
--- Begin Message ---
Package: wnpp
Severity: wishlist
Owner: Jonathan Yu <jawnsy@cpan.org>


I hate the idea of this, but I have to do this because two LEOCHARRE
modules are required by the new version of Wordpress::XMLRPC (already
packaged; its upgrade has been blocked for a long time because of this)

* Package name    : libleocharre-perl
  Version         : Debian Native
  Upstream Author : Leo Charre <leocharre@cpan.org>
* URL             : http://search.cpan.org/~leocharre/
* License         : Perl (Artistic or GPL-1+)
  Programming Lang: Perl
  Description     : Bundle of several modules in the LEOCHARRE:: namespace

Basically, the author of Wordpress::XMLRPC requires his own helper
modules, which may be used in several distributions (since he produces
many of them). However, I'm hesitant to create multiple packages for
them because:

  1. These packages are probably only ever going to be used by Leo Charre
  2. These packages are coded poorly (they export random functions into
     the main namespace)
  3. The packages contain very small portions of code

I'd even consider patching Wordpress::XMLRPC with these functions; however,
I don't think the patch would be sustainable in the long term.

There was some discussion on the pkg-perl list:
http://lists.debian.org/debian-perl/2009/11/msg00065.html

Useful suggestions are gladly accepted and appreciated. Please give me a
less crappy alternative. I beg of you. PLEASE.



--- End Message ---
--- Begin Message ---
Hi:

Please note that these bugs are no longer valid because
libwordpress-xmlrpc-perl has been removed from Debian unstable. It
appears that it has also been removed from testing per the automated
process.

This will "resolve" the issues for now -- however, unfortunately the
package is no longer available as part of Debian and must be installed
manually via CPAN or another tool. Hopefully the issues will be
resolved upstream eventually.

If there is some serious need for this package (and I mean enough to
convince us to do the work this would entail), we can consider a
severe series of patches to get things in good working order (but we'd
pretty much be diverging from upstream and it would pretty much just
be a fork of the older version that did not use the LEOCHARRE::
modules). I'd rather not maintain a module like this as a Debian
native package.

Cheers,

Jonathan


--- End Message ---

Reply to: