You are viewing a plain text version of this content. The canonical link for it is here.
Posted to users@spamassassin.apache.org by Justin Mason <jm...@jmason.org> on 2007/06/12 13:45:13 UTC
Re: ANNOUNCE: Apache SpamAssassin 3.2.1 available
Daniel J McDonald writes:
> On Mon, 2007-06-11 at 21:09 -0400, Rose, Bobby wrote:
> > I'm seeing the same kind of messages mentioned after compiling from
> > source on Redhat ES4 and running make test.
>
> I'm wondering if this is the reason:
> + make FULLPERL=/usr/bin/perl test
> /usr/bin/perl5.8.7 build/mkrules --exit_on_no_src --src rulesrc --out
> rules --manifest MANIFEST --manifestskip MANIFEST.SKIP
> no source directory found: exiting
nope, that can be ignored.
> I don't see any other compilation errors. The build process complained
> about a few missing packages at the beginning Razor2, Mail::DKIM, and
> Encode::Detect. I was able to install all of those other than
> Encode::Detect (I can't get the perl-Encode-Detect srpm to recompile,
> and I can't figure out what pre-requisites it is missing, since it
> complained about not having ExtUtils::CBuilder, but installing that
> didn't seem to mollify it).
>
> I built 3.2.0 on this same box just a couple of weeks ago, and didn't
> see anything in the release notes, or the bugs that I read, telling me
> that I would need to make major changes, so I'm flummoxed.
There should be no major changes since 3.2.0 that'd require that...
can you post the log files from t/log/d.spamc_optC/* ?
--j.
> > -----Original Message-----
> > From: Daniel J McDonald [mailto:dan.mcdonald@austinenergy.com]
> > Sent: Monday, June 11, 2007 6:35 PM
> > To: users@spamassassin.apache.org
> > Subject: Re: ANNOUNCE: Apache SpamAssassin 3.2.1 available
> >
> > On Mon, 2007-06-11 at 21:14 +0100, Justin Mason wrote:
> > > Apache SpamAssassin 3.2.1 is now available! This is a maintenance and
> >
> > > security release of the 3.2.x branch. It is highly recommended that
> > > people upgrade to this version from 3.2.0.
> >
> >
> > Whilst compiling the RPM for mandriva corporate server 4:
> >
> > t/spamc_optC................ Not found: reported spam = Message
--j.
> > -----Original Message-----
> > From: Daniel J McDonald [mailto:dan.mcdonald@austinenergy.com]
> > Sent: Monday, June 11, 2007 6:35 PM
> > To: users@spamassassin.apache.org
> > Subject: Re: ANNOUNCE: Apache SpamAssassin 3.2.1 available
> >
> > On Mon, 2007-06-11 at 21:14 +0100, Justin Mason wrote:
> > > Apache SpamAssassin 3.2.1 is now available! This is a maintenance and
> >
> > > security release of the 3.2.x branch. It is highly recommended that
> > > people upgrade to this version from 3.2.0.
> >
> >
> > Whilst compiling the RPM for mandriva corporate server 4:
> >
> > t/spamc_optC................ Not found: reported spam = Message
> > successfully reported/revoked
> > # Failed test 2 in t/SATest.pm at line 635 Output can be examined in:
> > log/d.spamc_optC/out.1
> > t/spamc_optC................NOK 2 Not found: revoked ham = Message
> > successfully reported/revoked
> > # Failed test 4 in t/SATest.pm at line 635 fail #2 Output can be
> > examined in: log/d.spamc_optC/out.1 log/d.spamc_optC/out.3
> > t/spamc_optC................NOK 4 Not found: failed to report spam
> > = Unable to report/revoke message
> > [...]
> > Output can be examined in: log/d.spamc_optC/out.1 log/d.spamc_optC/out.3
> > log/d.spamc_optC/out.5 log/d.spamc_optC/out.7
> > t/spamc_optC................FAILED tests 2, 4, 6,
> > 8
> > Failed 4/9 tests, 55.56% okay
> > t/spamc_optL................# Failed test 1 in t/spamc_optL.t at line 20
> > Not found: learned spam = Message successfully un/learned [...]
> > t/spamc_optL................FAILED tests 1-16
> > Failed 16/16 tests, 0.00% okay
> >
> > Failed Test Stat Wstat Total Fail Failed List of Failed
> > ------------------------------------------------------------------------
> > -------
> > t/spamc_optC.t 9 4 44.44% 2 4 6 8
> > t/spamc_optL.t 16 16 100.00% 1-16
> > t/spamd_allow_user_rules.t 5 1 20.00% 4
> > t/spamd_plugin.t 6 2 33.33% 4 6
> > 17 tests skipped.
> > Failed 4/129 test scripts, 96.90% okay. 23/1981 subtests failed, 98.84%
> > okay.
> > make: *** [test_dynamic] Error 255
> > error: Bad exit status from /var/tmp/rpm-tmp.45769 (%check)
> >
> >
> > Any thoughts?
> > --
> > Daniel J McDonald, CCIE # 2495, CISSP # 78281, CNX Austin Energy
> > http://www.austinenergy.com
> >
> --
> Daniel J McDonald, CCIE # 2495, CISSP # 78281, CNX
> Austin Energy
> http://www.austinenergy.com
Re: ANNOUNCE: Apache SpamAssassin 3.2.1 available
Posted by "Tom Q. Citizen" <to...@bay-online-media.com>.
On Wed, June 13, 2007 9:38 am, Jake Richter wrote:
> Is the workaround y'all are suggesting that the SA make be done as a
> non-root
> user, but the install be done as root in my situation?
>
> In other words,
>
> As non-root user:
>
> perl Makefile.PL
> make
> make test
>
> As root:
>
> make install
Re: ANNOUNCE: Apache SpamAssassin 3.2.1 available
Posted by Jake Richter <ja...@richterscale.org>.
Jake Richter <jake <at> richterscale.org> writes:
> Is the workaround y'all are suggesting that the SA make be done as a non-root
> user, but the install be done as root in my situation?
>[snip]
To answer my own question: Yes. This works fine.
Jake
Re: ANNOUNCE: Apache SpamAssassin 3.2.1 available
Posted by Jake Richter <ja...@richterscale.org>.
Daniel J McDonald <dan.mcdonald <at> austinenergy.com> writes:
>
> On Tue, 2007-06-12 at 16:07 -0400, Rosenbaum, Larry M. wrote:
> > > From: Duncan Hill [mailto:spamassassin <at> cricalix.net]
> > >
> > > On Tue, June 12, 2007 13:33, Justin Mason wrote:
> > > > Daniel J McDonald writes:
> > > >> So, you can't build the RPM as root.
> > > >>
> > > >>
>
> > Very interesting, but I ran into this problem on a Solaris system and I
> > wasn't trying to build an RPM. I was just trying to build SA from
> > source with the usual
> >
> > perl Makefile.PL
> > make
> > make test (this step gave errors when run as root)
> >
> > Does the same logic apply when RPMs are not involved?
>
> Yes, unless your umask is 666. When it detects the root user, it tries
> to change to "nobody". since Nobody can't write in the t/log/*
> directories, the test fails.
>
Pardon my ignorance, but for those of us who have always installed SA as root,
this new behavior in 3.2.1 appears to be a bit of a bug (and I'm just using the
SA distribution the same way Larry is using - no RPM is being built).
Is the workaround y'all are suggesting that the SA make be done as a non-root
user, but the install be done as root in my situation?
In other words,
As non-root user:
perl Makefile.PL
make
make test
As root:
make install
Thanks,
Jake
RE: ANNOUNCE: Apache SpamAssassin 3.2.1 available
Posted by Daniel J McDonald <da...@austinenergy.com>.
On Tue, 2007-06-12 at 16:07 -0400, Rosenbaum, Larry M. wrote:
> > From: Duncan Hill [mailto:spamassassin@cricalix.net]
> >
> > On Tue, June 12, 2007 13:33, Justin Mason wrote:
> > > Daniel J McDonald writes:
> > >> So, you can't build the RPM as root.
> > >>
> > >>
> Very interesting, but I ran into this problem on a Solaris system and I
> wasn't trying to build an RPM. I was just trying to build SA from
> source with the usual
>
> perl Makefile.PL
> make
> make test (this step gave errors when run as root)
>
> Does the same logic apply when RPMs are not involved?
Yes, unless your umask is 666. When it detects the root user, it tries
to change to "nobody". since Nobody can't write in the t/log/*
directories, the test fails.
--
Daniel J McDonald, CCIE # 2495, CISSP # 78281, CNX
Austin Energy
http://www.austinenergy.com
RE: ANNOUNCE: Apache SpamAssassin 3.2.1 available
Posted by "Rosenbaum, Larry M." <ro...@ornl.gov>.
> From: Duncan Hill [mailto:spamassassin@cricalix.net]
>
> On Tue, June 12, 2007 13:33, Justin Mason wrote:
> > Daniel J McDonald writes:
> >> So, you can't build the RPM as root.
> >>
> >>
> >> I just added all of the various groups to my user, set up a user
> build
> >> directory tree, compiled it under my username and it tested fine,
at
> least to the point
> >> that it normally bombs
> >
> > aha, that's it alright. could you open a bug to get that fixed?
>
> One argument is that you shouldn't be building RPMs as root since you
> don't know if the
> spec file is perfect and won't break outside of the semi-jail that RPM
> sets up. I've
> had at least one such RPM build when working with qmail, and it went
> and buggered up the
> build server by actually installing itself outside of the jail when
> building. Doing it
> as a regular reason will limit that kind of activity.
Very interesting, but I ran into this problem on a Solaris system and I
wasn't trying to build an RPM. I was just trying to build SA from
source with the usual
perl Makefile.PL
make
make test (this step gave errors when run as root)
Does the same logic apply when RPMs are not involved?
Re: ANNOUNCE: Apache SpamAssassin 3.2.1 available
Posted by Duncan Hill <sp...@cricalix.net>.
On Tue, June 12, 2007 13:33, Justin Mason wrote:
> Daniel J McDonald writes:
>> So, you can't build the RPM as root.
>>
>>
>> I just added all of the various groups to my user, set up a user build
>> directory tree, compiled it under my username and it tested fine, at least to the point
>> that it normally bombs
>
> aha, that's it alright. could you open a bug to get that fixed?
One argument is that you shouldn't be building RPMs as root since you don't know if the
spec file is perfect and won't break outside of the semi-jail that RPM sets up. I've
had at least one such RPM build when working with qmail, and it went and buggered up the
build server by actually installing itself outside of the jail when building. Doing it
as a regular reason will limit that kind of activity.
Re: ANNOUNCE: Apache SpamAssassin 3.2.1 available
Posted by Daniel J McDonald <da...@austinenergy.com>.
On Tue, 2007-06-12 at 12:45 +0100, Justin Mason wrote:
> Daniel J McDonald writes:
> > On Mon, 2007-06-11 at 21:09 -0400, Rose, Bobby wrote:
> > > I'm seeing the same kind of messages mentioned after compiling from
> > > source on Redhat ES4 and running make test.
> >
> > I'm wondering if this is the reason:
> > + make FULLPERL=/usr/bin/perl test
> > /usr/bin/perl5.8.7 build/mkrules --exit_on_no_src --src rulesrc --out
> > rules --manifest MANIFEST --manifestskip MANIFEST.SKIP
> > no source directory found: exiting
>
> nope, that can be ignored.
>
> > I don't see any other compilation errors. The build process complained
> > about a few missing packages at the beginning Razor2, Mail::DKIM, and
> > Encode::Detect. I was able to install all of those other than
> > Encode::Detect (I can't get the perl-Encode-Detect srpm to recompile,
> > and I can't figure out what pre-requisites it is missing, since it
> > complained about not having ExtUtils::CBuilder, but installing that
> > didn't seem to mollify it).
> >
> > I built 3.2.0 on this same box just a couple of weeks ago, and didn't
> > see anything in the release notes, or the bugs that I read, telling me
> > that I would need to make major changes, so I'm flummoxed.
>
> There should be no major changes since 3.2.0 that'd require that...
> can you post the log files from t/log/d.spamc_optC/* ?
>
I think the major error in the log files is:
[27488] warn: spamd: still running as root: user not specified with -u,
not found, or set to root, falling back to nobody
[27488] warn: spamd: bayes: locker: safe_lock: cannot create tmp
lockfile ./log/user_state/bayes.lock.ldap.austin-energy.net.27488
for ./log/user_state/bayes.lock: Permission denied
So, you can't build the RPM as root.
I just added all of the various groups to my user, set up a user build
directory tree, compiled it under my username and it tested fine, at
least to the point that it normally bombs