Mailing List Archive: SpamAssassin: devel

3.3.0 plans

1 2 3

View All

Index | Next | Previous | View Threaded

wtogami at redhat

Jul 6, 2009, 12:13 PM

Post #51 of 60 (755 views)
Permalink

Re: 3.3.0 plans [In reply to]

On 07/03/2009 10:37 PM, Matt Kettler wrote:
> The public alpha release was announced yesterday on the users mailing list:
>
> http://mail-archives.apache.org/mod_mbox/spamassassin-users/200907.mbox/%3C6c399e450907021522k1678f0ffn454a1e670f064b40 [at] mail%3E

I'm having trouble getting it to run on Fedora 11.

[root [at] newcapric spamassassin]# sa-update
config: no configuration text or files found! do you need to run
'sa-update'?
check: no loaded plugin implements 'check_main': cannot scan!
Check the necessary '.pre' files are in the config directory.

*** spamassassin-3.2.5 ***

[root [at] newcapric ~]# cd /etc/mail/spamassassin/
[root [at] newcapric spamassassin]# ls
init.pre local.cf sa-update-keys spamassassin-default.rc
spamassassin-helper.sh spamassassin-spamc.rc v310.pre v312.pre v320.pre

*** spamassassin-3.3.0-alpha1 ***

[root [at] newcapric ~]# cd /etc/mail/spamassassin/
[root [at] newcapric spamassassin]# ls
local.cf sa-update-keys spamassassin-default.rc
spamassassin-helper.sh spamassassin-spamc.rc

All of the *.pre files are no longer being installed into our RPM. It
seems to pass the test suite though.

All tests successful.
Files=151, Tests=1938, 173 wallclock secs ( 1.05 usr 0.39 sys + 67.07
cusr 13.81 csys = 82.32 CPU)
Result: PASS

Still looking...

Warren Togami
wtogami [at] redhat

Mark.Martinec+sa at ijs

Jul 6, 2009, 1:00 PM

Post #52 of 60 (746 views)
Permalink

Re: 3.3.0 plans [In reply to]

Warren,

> On 07/03/2009 10:37 PM, Matt Kettler wrote:
> > The public alpha release was announced yesterday on the users mailing
> > list:
> >
> > http://mail-archives.apache.org/mod_mbox/spamassassin-users/200907.mbox/%
> >3C6c399e450907021522k1678f0ffn454a1e670f064b40 [at] mail%3E
>
> I'm having trouble getting it to run on Fedora 11.
>
> [root [at] newcapric spamassassin]#
> sa-update config: no configuration text or files found!
> do you need to run 'sa-update'?
> check: no loaded plugin implements 'check_main': cannot scan!
> Check the necessary '.pre' files are in the config directory.

Yes, and? Did you run sa-update???

The 3.3 no longer comes with rules in the same package.
These must be installed separately with 'sa-update',
which either fetches them from the net, or can install
them from a tar - which is in the same directory
as 3.3.0-alpha1 is.

Mark

wtogami at redhat

Jul 6, 2009, 1:05 PM

Post #53 of 60 (748 views)
Permalink

Re: 3.3.0 plans [In reply to]

On 07/06/2009 04:00 PM, Mark Martinec wrote:
> Warren,
>
>> On 07/03/2009 10:37 PM, Matt Kettler wrote:
>>> The public alpha release was announced yesterday on the users mailing
>>> list:
>>>
>>> http://mail-archives.apache.org/mod_mbox/spamassassin-users/200907.mbox/%
>>> 3C6c399e450907021522k1678f0ffn454a1e670f064b40 [at] mail%3E
>> I'm having trouble getting it to run on Fedora 11.
>>
>> [root [at] newcapric spamassassin]#
>> sa-update config: no configuration text or files found!
>> do you need to run 'sa-update'?
>> check: no loaded plugin implements 'check_main': cannot scan!
>> Check the necessary '.pre' files are in the config directory.
>
> Yes, and? Did you run sa-update???
>
> The 3.3 no longer comes with rules in the same package.
> These must be installed separately with 'sa-update',
> which either fetches them from the net, or can install
> them from a tar - which is in the same directory
> as 3.3.0-alpha1 is.
>
> Mark

sa-update is failing due to the lack of the /etc/mail/spamassassin/*.pre
files.

Warren Togami
wtogami [at] redhat

jm at jmason

Jul 6, 2009, 2:32 PM

Post #54 of 60 (752 views)
Permalink

Re: 3.3.0 plans [In reply to]

On Mon, Jul 6, 2009 at 21:05, Warren Togami<wtogami [at] redhat> wrote:
> On 07/06/2009 04:00 PM, Mark Martinec wrote:
>>
>> Warren,
>>
>>> On 07/03/2009 10:37 PM, Matt Kettler wrote:
>>>>
>>>> The public alpha release was announced yesterday on the users mailing
>>>> list:
>>>>
>>>>
>>>> http://mail-archives.apache.org/mod_mbox/spamassassin-users/200907.mbox/%
>>>> 3C6c399e450907021522k1678f0ffn454a1e670f064b40 [at] mail%3E
>>>
>>> I'm having trouble getting it to run on Fedora 11.
>>>
>>> [root [at] newcapric spamassassin]#
>>> sa-update config: no configuration text or files found!
>>> do you need to run 'sa-update'?
>>> check: no loaded plugin implements 'check_main': cannot scan!
>>> Check the necessary '.pre' files are in the config directory.
>>
>> Yes, and? Did you run sa-update???
>>
>> The 3.3 no longer comes with rules in the same package.
>> These must be installed separately with 'sa-update',
>> which either fetches them from the net, or can install
>> them from a tar - which is in the same directory
>> as 3.3.0-alpha1 is.
>>
>> Mark
>
> sa-update is failing due to the lack of the /etc/mail/spamassassin/*.pre
> files.
>

this sounds like our RPM spec file is buggy -- does it work if
installed from the tgz?

--j.

wtogami at redhat

Jul 6, 2009, 2:40 PM

Post #55 of 60 (745 views)
Permalink

Re: 3.3.0 plans [In reply to]

On 07/06/2009 05:32 PM, Justin Mason wrote:
> On Mon, Jul 6, 2009 at 21:05, Warren Togami<wtogami [at] redhat> wrote:
>> On 07/06/2009 04:00 PM, Mark Martinec wrote:
>>> Warren,
>>>
>>>> On 07/03/2009 10:37 PM, Matt Kettler wrote:
>>>>> The public alpha release was announced yesterday on the users mailing
>>>>> list:
>>>>>
>>>>>
>>>>> http://mail-archives.apache.org/mod_mbox/spamassassin-users/200907.mbox/%
>>>>> 3C6c399e450907021522k1678f0ffn454a1e670f064b40 [at] mail%3E
>>>> I'm having trouble getting it to run on Fedora 11.
>>>>
>>>> [root [at] newcapric spamassassin]#
>>>> sa-update config: no configuration text or files found!
>>>> do you need to run 'sa-update'?
>>>> check: no loaded plugin implements 'check_main': cannot scan!
>>>> Check the necessary '.pre' files are in the config directory.
>>> Yes, and? Did you run sa-update???
>>>
>>> The 3.3 no longer comes with rules in the same package.
>>> These must be installed separately with 'sa-update',
>>> which either fetches them from the net, or can install
>>> them from a tar - which is in the same directory
>>> as 3.3.0-alpha1 is.
>>>
>>> Mark
>> sa-update is failing due to the lack of the /etc/mail/spamassassin/*.pre
>> files.
>>
>
> this sounds like our RPM spec file is buggy -- does it work if
> installed from the tgz?
>
> --j.

This isn't the upstream RPM spec file. This is Fedora's spec file.

How can it copy the *.pre files into the RPM if the *.pre files do not
exist in the tarball's rules/ directory?

Warren

jm at jmason

Jul 6, 2009, 3:12 PM

Post #56 of 60 (747 views)
Permalink

Re: 3.3.0 plans [In reply to]

On Mon, Jul 6, 2009 at 22:40, Warren Togami<wtogami [at] redhat> wrote:
> On 07/06/2009 05:32 PM, Justin Mason wrote:
>>
>> On Mon, Jul 6, 2009 at 21:05, Warren Togami<wtogami [at] redhat> wrote:
>>>
>>> On 07/06/2009 04:00 PM, Mark Martinec wrote:
>>>>
>>>> Warren,
>>>>
>>>>> On 07/03/2009 10:37 PM, Matt Kettler wrote:
>>>>>>
>>>>>> The public alpha release was announced yesterday on the users mailing
>>>>>> list:
>>>>>>
>>>>>>
>>>>>>
>>>>>> http://mail-archives.apache.org/mod_mbox/spamassassin-users/200907.mbox/%
>>>>>> 3C6c399e450907021522k1678f0ffn454a1e670f064b40 [at] mail%3E
>>>>>
>>>>> I'm having trouble getting it to run on Fedora 11.
>>>>>
>>>>> [root [at] newcapric spamassassin]#
>>>>> sa-update config: no configuration text or files found!
>>>>> do you need to run 'sa-update'?
>>>>> check: no loaded plugin implements 'check_main': cannot scan!
>>>>> Check the necessary '.pre' files are in the config directory.
>>>>
>>>> Yes, and? Did you run sa-update???
>>>>
>>>> The 3.3 no longer comes with rules in the same package.
>>>> These must be installed separately with 'sa-update',
>>>> which either fetches them from the net, or can install
>>>> them from a tar - which is in the same directory
>>>> as 3.3.0-alpha1 is.
>>>>
>>>> Mark
>>>
>>> sa-update is failing due to the lack of the /etc/mail/spamassassin/*.pre
>>> files.
>>>
>>
>> this sounds like our RPM spec file is buggy -- does it work if
>> installed from the tgz?
>>
>> --j.
>
> This isn't the upstream RPM spec file. This is Fedora's spec file.
>
> How can it copy the *.pre files into the RPM if the *.pre files do not exist
> in the tarball's rules/ directory?

crap, you're right. :(
https://issues.apache.org/SpamAssassin/show_bug.cgi?id=6147

there's a patch there that appears to fix it. does it work for you?

--j.

wtogami at redhat

Jul 6, 2009, 3:36 PM

Post #57 of 60 (744 views)
Permalink

Re: 3.3.0 plans [In reply to]

On 07/06/2009 06:12 PM, Justin Mason wrote:
>
> crap, you're right. :(
> https://issues.apache.org/SpamAssassin/show_bug.cgi?id=6147
>
> there's a patch there that appears to fix it. does it work for you?
>
> --j.

A patch only for MANIFEST* going to copy *.pre files from the tarball,
when the tarball lacks those files?

It seems MANIFEST* only effects what goes from the SCM into tarball.

Anyhow, I'm adding the *.pre files manually for the initial package.

Warren Togami
wtogami [at] redhat

jm at jmason

Jul 7, 2009, 1:57 AM

Post #58 of 60 (736 views)
Permalink

Re: 3.3.0 plans [In reply to]

On Mon, Jul 6, 2009 at 23:36, Warren Togami<wtogami [at] redhat> wrote:
> On 07/06/2009 06:12 PM, Justin Mason wrote:
>>
>> crap, you're right. :(
>> https://issues.apache.org/SpamAssassin/show_bug.cgi?id=6147
>>
>> there's a patch there that appears to fix it. does it work for you?
>>
>> --j.
>
> A patch only for MANIFEST* going to copy *.pre files from the tarball, when
> the tarball lacks those files?
>
> It seems MANIFEST* only effects what goes from the SCM into tarball.

yep, you'd have to rebuild the tarball.

> Anyhow, I'm adding the *.pre files manually for the initial package.

ok

--j.

wtogami at redhat

Jul 7, 2009, 2:07 AM

Post #59 of 60 (737 views)
Permalink

Re: 3.3.0 plans [In reply to]

On 07/07/2009 04:57 AM, Justin Mason wrote:
> On Mon, Jul 6, 2009 at 23:36, Warren Togami<wtogami [at] redhat> wrote:
>> On 07/06/2009 06:12 PM, Justin Mason wrote:
>>> crap, you're right. :(
>>> https://issues.apache.org/SpamAssassin/show_bug.cgi?id=6147
>>>
>>> there's a patch there that appears to fix it. does it work for you?
>>>
>>> --j.
>> A patch only for MANIFEST* going to copy *.pre files from the tarball, when
>> the tarball lacks those files?
>>
>> It seems MANIFEST* only effects what goes from the SCM into tarball.
>
> yep, you'd have to rebuild the tarball.
>
>> Anyhow, I'm adding the *.pre files manually for the initial package.
>
> ok

But now I'm unable to push this packaged due to the tainting issue. Is
this is in fact a perl bug, not spamassassin's fault? This is the
latest version of upstream perl.

Warren Togami
wtogami [at] redhat

jm at jmason

Jul 7, 2009, 2:33 AM

Post #60 of 60 (726 views)
Permalink

Re: 3.3.0 plans [In reply to]

On Tue, Jul 7, 2009 at 10:07, Warren Togami<wtogami [at] redhat> wrote:
> On 07/07/2009 04:57 AM, Justin Mason wrote:
>>
>> On Mon, Jul 6, 2009 at 23:36, Warren Togami<wtogami [at] redhat> wrote:
>>>
>>> On 07/06/2009 06:12 PM, Justin Mason wrote:
>>>>
>>>> crap, you're right. :(
>>>> https://issues.apache.org/SpamAssassin/show_bug.cgi?id=6147
>>>>
>>>> there's a patch there that appears to fix it. does it work for you?
>>>>
>>>> --j.
>>>
>>> A patch only for MANIFEST* going to copy *.pre files from the tarball,
>>> when
>>> the tarball lacks those files?
>>>
>>> It seems MANIFEST* only effects what goes from the SCM into tarball.
>>
>> yep, you'd have to rebuild the tarball.
>>
>>> Anyhow, I'm adding the *.pre files manually for the initial package.
>>
>> ok
>
> But now I'm unable to push this packaged due to the tainting issue. Is this
> is in fact a perl bug, not spamassassin's fault? This is the latest version
> of upstream perl.

I haven't looked into it, but iirc, it's a perl bug. (at least a bug
in a module bundled with perl.) We trigger it due to our extensive
use of -T (taint mode). As Mark notes, we may be able to work around
it in our code though.

--j.

1 2 3

View All

Index | Next | Previous | View Threaded

Interested in having your list archived? Contact Gossamer Threads