Your message dated Sat, 26 Jan 2008 08:07:08 +0000
with message-id <[EMAIL PROTECTED]>
and subject line Bug#462282: ezmlm-browse: should this package be orphaned or 
possibly removed?
has caused the attached Bug report 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 I am
talking about this indicates a serious mail system misconfiguration
somewhere.  Please contact me immediately.)

Debian bug tracking system administrator
(administrator, Debian Bugs database)

--- Begin Message ---
Package: ezmlm-browse
Version: 0.10-2
Severity: serious
User: [EMAIL PROTECTED]
Usertags: proposed-orphan

Hi,

While reviewing some packages, your package came up as a package that
should maybe be orphaned by its maintainer, because:

* Hasn't been uploaded since Feb. 2006
* Seriously out of date standards and policy
* New upstream has been available since 2006 (0.10 is from 2004)
* Low popcon score (11 installs)
* Ships python modules but does not conform to new python policy (See BTS: 
#380790)

If you think that it should be removed from Debian instead of being
orphaned, please reply to this bug and tell so.

If you agree that it should be orphaned, sending the following commands
to [EMAIL PROTECTED] should do it (after replacing nnnnnn with
this bug's number):

severity nnnnnn normal
reassign nnnnnn wnpp
retitle nnnnnn O: <packagename> -- <short package description>
thanks

For more information, see
http://www.debian.org/doc/developers-reference/ch-pkgs.en.html#s-archive-manip
http://www.debian.org/devel/wnpp/

If you disagree and want to continue to maintain this package, please
close this bug, preferably in an upload also fixing the other issues.

Thank you,

Barry deFreese




--- End Message ---
--- Begin Message ---
On Wed, Jan 23, 2008 at 01:17:28PM -0500, Barry deFreese wrote:
> If you disagree and want to continue to maintain this package, please
> close this bug, preferably in an upload also fixing the other issues.

I still use the package, and it works just fine.  Concerning #380790, I
tagged it help, as, at least at that time, there was no other
documentation available on the python policy other than "use dh_python"
or so; the package doesn't use debhelper.

Regards, Gerrit.


--- End Message ---

Reply via email to