[Pkg-dspam-misc] Bug#577661: dspam: should this package be removed?

[Kurt B. Kaiser]

On Tue, 13 Apr 2010 15:09:04 +0200, "Jan Hauke Rahm"
<jhr at debian.org> said:
> Package: dspam 
> Version: 3.6.8-9.3 
> Severity: serious
> User: debian-qa at lists.debian.org
> Usertags: proposed-removal
>
> Dear Maintainers,
>
> while reviewing some packages, your package came up as a possible
> candidate for removal from Debian, because:
>
> * last maintainer upload 09/2008
> * RC buggy
> * outdated
> * uploaders not interested or MIA (?)
> * not part of squeeze anyways and no solution in sight
>
> If you think that it should be orphaned instead of being removed from
> Debian, please reply to this bug and tell so.
>
> If you disagree and want to continue to maintain this package, please
> just close this bug and do an upload also fixing the other issues.

Thank you for taking the time to review the dspam package status.  I
apologize for causing this extra work.

While the packages do not appear to have received adequate attention in
the last year and a half, Julien Valroff has in fact been working
diligently to prepare the new upstream release (from January) for upload
into experimental.  This is the first solid release upstream release
in several years.

I would like to request a stay of execution, and suggest the
following plan:

First, determine which of the uploaders still have an interest in dspam.
I think there are currently at least three people who would like to
contribute to maintaining official Debian dspam packages.

Second, continue with the development of the experimental upload.  I
think Julien is pretty close.  Since his work differs considerably from
the current package, I think experimental is still warranted.

Third, prepare an upload to unstable which takes the current package to
3.6.8-10, fixing the RC issues and bringing it back into policy
compliance.  I will work on that, if Julien has no objection.

DSPAM has been a Debian package for many years, and IMO it would be
unfortunate to remove it just when upstream finally got straightened
out and produced a new stable release.

-- 
KBK