Re: possible mass bug filing: spamassassin 3
On Wed, Oct 06, 2004 at 11:52:04AM +0200, martin f krafft wrote:
> If you'd be so kind as to refer to #274993, I think we have
> a problem. A number of packages (see the bug report) depend on
> spamassassin, but some are not going to work with version 3, which
> changed the API considerably. The example here is spamass-milter,
> which simply does not work.
> The submitter of the bug report suggests to add a conflict to
> spamassassin. To me, this is coming at it from the wrong angle. I my
> well understand this all wrong, but if SA conflicts with
> spamass-milter, which is in testing, it is not going to be able to
> trickle into sarge until a new spamass-milter has been uploaded and
> has trickled to sarge first.
> Instead, I propose that the packages depending on spamassassin
> should be removed from sarge unless it is known that they work with
> spamassassin 3.
This is backwards. The conflicts must be added in spamassassin in order
that we don't forget to remove said other packages from sarge if
Colin Watson [firstname.lastname@example.org]