Mailing List Archive: SpamAssassin: devel

3.3.0-alpha1 working for anyone?

Index | Next | Previous | View Threaded

wtogami at redhat

Jul 6, 2009, 12:52 PM

Post #1 of 6 (405 views)
Permalink

3.3.0-alpha1 working for anyone?

On 07/06/2009 03:13 PM, Warren Togami wrote:
> 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.
>

spamassassin-3.2.5 rules/ contains the *.pre files.
spamassassin-3.3.0-alpha1 rules/ is missing *.pre files.

Was this intentional?

Is 3.3.0-alpha1 working for anybody?

Possibly a separate issue this is the %build section from our
spamassassin.spec file.

%build
CFLAGS="$RPM_OPT_FLAGS"; export CFLAGS
%{__perl} Makefile.PL PREFIX=%{_prefix} SYSCONFDIR=%{_sysconfdir}
DESTDIR=$RPM_BUILD_ROOT < /dev/null
%{__make}

Checking if your kit is complete...
Looks good
'ENABLE_SSL' is not a known MakeMaker parameter name.
'SYSCONFDIR' is not a known MakeMaker parameter name.
Writing Makefile for Mail::SpamAssassin
Makefile written by ExtUtils::MakeMaker 6.42
+ /usr/bin/make 'OPTIMIZE=-O2 -g' -j3

spamassassin-3.2.5 does not complain about ENABLE_SSL or SYSCONFDIR in
MakeMaker. What changed? Do we need to adapt?

Warren Togami
wtogami [at] redhat

parkerm at pobox

Jul 6, 2009, 12:59 PM

Post #2 of 6 (377 views)
Permalink

Re: 3.3.0-alpha1 working for anyone? [In reply to]

On Jul 6, 2009, at 2:52 PM, Warren Togami wrote:

> On 07/06/2009 03:13 PM, Warren Togami wrote:
>> 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.
>>
>
> spamassassin-3.2.5 rules/ contains the *.pre files.
> spamassassin-3.3.0-alpha1 rules/ is missing *.pre files.
>
> Was this intentional?

Yes. 3.3 requires that you run sa-update after installation to pick
up the latest rules release. I believe this is documented.

For packagers such as yourself, you'll probably want to have a
separate rules package for that initial install.

Michael

>
>
> Is 3.3.0-alpha1 working for anybody?
>
> Possibly a separate issue this is the %build section from our
> spamassassin.spec file.
>
> %build
> CFLAGS="$RPM_OPT_FLAGS"; export CFLAGS
> %{__perl} Makefile.PL PREFIX=%{_prefix} SYSCONFDIR=%{_sysconfdir}
> DESTDIR=$RPM_BUILD_ROOT < /dev/null
> %{__make}
>
> Checking if your kit is complete...
> Looks good
> 'ENABLE_SSL' is not a known MakeMaker parameter name.
> 'SYSCONFDIR' is not a known MakeMaker parameter name.
> Writing Makefile for Mail::SpamAssassin
> Makefile written by ExtUtils::MakeMaker 6.42
> + /usr/bin/make 'OPTIMIZE=-O2 -g' -j3
>
> spamassassin-3.2.5 does not complain about ENABLE_SSL or SYSCONFDIR
> in MakeMaker. What changed? Do we need to adapt?
>
> Warren Togami
> wtogami [at] redhat

wtogami at redhat

Jul 6, 2009, 1:02 PM

Post #3 of 6 (379 views)
Permalink

Re: 3.3.0-alpha1 working for anyone? [In reply to]

On 07/06/2009 03:59 PM, Michael Parker wrote:
>>
>> spamassassin-3.2.5 rules/ contains the *.pre files.
>> spamassassin-3.3.0-alpha1 rules/ is missing *.pre files.
>>
>> Was this intentional?
>
> Yes. 3.3 requires that you run sa-update after installation to pick up
> the latest rules release. I believe this is documented.
>
> For packagers such as yourself, you'll probably want to have a separate
> rules package for that initial install.
>

[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.

Isn't this a chicken and egg problem then?

Warren

wtogami at redhat

Jul 6, 2009, 1:46 PM

Post #4 of 6 (379 views)
Permalink

Re: 3.3.0-alpha1 working for anyone? [In reply to]

On 07/06/2009 03:59 PM, Michael Parker wrote:
> Yes. 3.3 requires that you run sa-update after installation to pick up
> the latest rules release. I believe this is documented.
>
> For packagers such as yourself, you'll probably want to have a separate
> rules package for that initial install.
>
> Michael

It appears that we were overzealous in removing the the rules from the
tarball? sa-update does not work all without the *.pre files.
Furthermore package upgrades expect the *.pre files to be installed in
the newer version of the package as they need to exist as config files.
They are gone from the alpha1 tarball.

Shouldn't the *.pre files be re-added to the tarball rules/ directory,
without the accompanying rules? I added them to my tarball and after
you install the resulting RPM binary package, sa-update works.

Warren Togami
wtogami [at] redhat

parkerm at pobox

Jul 6, 2009, 1:47 PM

Post #5 of 6 (379 views)
Permalink

Re: 3.3.0-alpha1 working for anyone? [In reply to]

On Jul 6, 2009, at 3:46 PM, Warren Togami wrote:

> On 07/06/2009 03:59 PM, Michael Parker wrote:
>> Yes. 3.3 requires that you run sa-update after installation to pick
>> up
>> the latest rules release. I believe this is documented.
>>
>> For packagers such as yourself, you'll probably want to have a
>> separate
>> rules package for that initial install.
>>
>> Michael
>
> It appears that we were overzealous in removing the the rules from
> the tarball? sa-update does not work all without the *.pre files.
> Furthermore package upgrades expect the *.pre files to be installed
> in the newer version of the package as they need to exist as config
> files. They are gone from the alpha1 tarball.
>
> Shouldn't the *.pre files be re-added to the tarball rules/
> directory, without the accompanying rules? I added them to my
> tarball and after you install the resulting RPM binary package, sa-
> update works.
>
>

Perhaps. Sounds like a bug, can you please file one.

Thanks
Michael

jm at jmason

Jul 6, 2009, 3:00 PM

Post #6 of 6 (373 views)
Permalink

Re: 3.3.0-alpha1 working for anyone? [In reply to]

> Checking if your kit is complete...
> Looks good
> 'ENABLE_SSL' is not a known MakeMaker parameter name.
> 'SYSCONFDIR' is not a known MakeMaker parameter name.
> Writing Makefile for Mail::SpamAssassin
> Makefile written by ExtUtils::MakeMaker 6.42
> + /usr/bin/make 'OPTIMIZE=-O2 -g' -j3
>
> spamassassin-3.2.5 does not complain about ENABLE_SSL or SYSCONFDIR in
> MakeMaker. What changed? Do we need to adapt?

no, that should be fine. (we should probably fix it ;)

btw, this should work --

perl Makefile.PL PREFIX=/tmp/sa
make
make install
/tmp/sa/bin/sa-update

does that work for you? even without an /etc/mail/spamassassin or
/usr/share/spamassassin? if so it's definitely the .spec file IMO.

--j.

Index | Next | Previous | View Threaded

Interested in having your list archived? Contact Gossamer Threads