You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@spamassassin.apache.org by Justin Mason <jm...@jmason.org> on 2006/01/15 02:42:02 UTC
Re: updates being published
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
Warren Togami writes:
> Justin Mason wrote:
> > Using SVN trunk, this now works:
> >
> > sudo sa-update && sudo /etc/init.d/spamassassin reload
> >
>
> Cool. Is it in the plans for sa-update to be usable with the 3.1.1
> release too?
I think Theo was planning that.
However, I had to make a few changes -- bugfixes and enhancements both --
so it'd be entirely possible, but will require a patch.
- --j.
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.1 (GNU/Linux)
Comment: Exmh CVS
iD8DBQFDyahqMJF5cimLx9ARAkXWAJ9XrvUFQaaUq+rPnyLm8z4wToHrHwCfbOiQ
9F2Wd40KQi5m6fpGqL4+QpA=
=SDes
-----END PGP SIGNATURE-----
Re: updates being published
Posted by Warren Togami <wt...@redhat.com>.
Justin Mason wrote:
> -----BEGIN PGP SIGNED MESSAGE-----
> Hash: SHA1
>
>
> Warren Togami writes:
>> Justin Mason wrote:
>>> Using SVN trunk, this now works:
>>>
>>> sudo sa-update && sudo /etc/init.d/spamassassin reload
>>>
>> Cool. Is it in the plans for sa-update to be usable with the 3.1.1
>> release too?
>
> I think Theo was planning that.
>
> However, I had to make a few changes -- bugfixes and enhancements both --
> so it'd be entirely possible, but will require a patch.
>
Working sa-update more than anything else in 3.1.x would be extremely
valuable as I work to convince our management to upgrade spamassassin in
our next enterprise update. Please let me know what kind of help you
need to make this a supported part of 3.1.x, and I will try to help.
Warren Togami
wtogami@redhat.com