On Fri, Apr 19, 2002 at 01:14:07PM +0200, Robert van der Meulen wrote:
>
> Quoting Joey Hess ([EMAIL PROTECTED]):
> > Duncan Findlay wrote:
> > > Is there any way of keeping razor out of woody until spamassassin 2.2 can
> > > be
> > > uploaded? (I could file an RC bug, but is there a better solut
Quoting Joey Hess ([EMAIL PROTECTED]):
> Duncan Findlay wrote:
> > Is there any way of keeping razor out of woody until spamassassin 2.2 can be
> > uploaded? (I could file an RC bug, but is there a better solution?)
>
> You could simply make spamassassin conflict with the razor it doesn't
> work
Duncan Findlay wrote:
> Is there any way of keeping razor out of woody until spamassassin 2.2 can be
> uploaded? (I could file an RC bug, but is there a better solution?)
You could simply make spamassassin conflict with the razor it doesn't
work for, and somehow get it into woody first. Or coordin
Unfortunately, there is a conflict between spamassassin 2.11 and razor 1.20,
as some of you may know.
Spamassassin 2.2 will be released shortly by upstream, and that version
contains the fix for the issue. I do not wish to backport the fix, or upload
a CVS version, as 2.2 should be coming in the
4 matches
Mail list logo
