Re: Yum update of SA from 2.63 to 3.0x

2004-12-16 Thread Kenneth Porter
--On Wednesday, December 15, 2004 4:27 PM -0600 Chris Barnes 
[EMAIL PROTECTED] wrote:

warning: Installed (but unpackaged) file(s) found:
   /usr/lib/perl5/5.8.3/i386-linux-thread-multi/perllocal.pod
I'm guessing the make install step in the RPM spec file did this. It 
shouldn't touch the live system, though, so a bugzilla should be filed 
about this.




Re: Yum update of SA from 2.63 to 3.0x

2004-12-16 Thread Kenneth Porter
--On Wednesday, December 15, 2004 4:27 PM -0600 Chris Barnes 
[EMAIL PROTECTED] wrote:

No dice - downloaded and when I ran the:
rpmbuild -tb Mail-SpamAssassin-3.0.1.tar.gz
I got:
warning: Installed (but unpackaged) file(s) found:
   /usr/lib/perl5/5.8.3/i386-linux-thread-multi/perllocal.pod
Wrote: /usr/src/redhat/RPMS/i386/spamassassin-3.0.1-1.i386.rpm
SA isn't running at all now.
This sounds like you rebuilt the RPM as root and something in the rebuild 
procedure isn't root-safe and clobbered the live system. I only rebuild 
RPM's as a mortal.

To package as a mortal, create the file ~/.rpmmacros and put in it the 
lines:

%_topdir /home/buildmeister/rpm
%buildroot %{_topdir}/var/tmp
where buildmeister is the user who will be building RPM's. Create ~/rpm and 
under that create directories BUILD, RPMS, SOURCES, SPECS, SRPMS, and var.

Now run the rpmbuild command as user buildmeister and the process will be 
sandboxed in those directories.


Re: Yum update of SA from 2.63 to 3.0x

2004-12-16 Thread Chris Barnes
Kenneth Porter [EMAIL PROTECTED] wrote:
 --On Wednesday, December 15, 2004 4:27 PM -0600 Chris Barnes
 [EMAIL PROTECTED] wrote:

 warning: Installed (but unpackaged) file(s) found:
/usr/lib/perl5/5.8.3/i386-linux-thread-multi/perllocal.pod

 I'm guessing the make install step in the RPM spec file did this. It
 shouldn't touch the live system, though, so a bugzilla should be filed
 about this.

Ok, I haven't the foggiest idea how to do that.


-- 

+ + + + + + + + + + + + + + + + + + + + + + + + + + + + + +
Chris Barnes   AOL IM: CNBarnes
[EMAIL PROTECTED]Yahoo IM: chrisnbarnes





Re: Yum update of SA from 2.63 to 3.0x

2004-12-16 Thread Theo Van Dinter
On Thu, Dec 16, 2004 at 08:49:01AM -0600, Chris Barnes wrote:
  warning: Installed (but unpackaged) file(s) found:
 /usr/lib/perl5/5.8.3/i386-linux-thread-multi/perllocal.pod
 
  I'm guessing the make install step in the RPM spec file did this. It
  shouldn't touch the live system, though, so a bugzilla should be filed
  about this.

I don't think there's a way to avoid the perllocal.pod bit (if there is,
somebody tell me!)  The real lesson here is: don't build RPMs as root if you
want to make sure nothing on the system will be modified by the build.

-- 
Randomly Generated Tagline:
Windows 98 supports real multitasking - it can boot and crash
 simultaneously. - Bernhard Rosenkraenzer


pgpFV4Hyr37i2.pgp
Description: PGP signature


Yum update of SA from 2.63 to 3.0x

2004-12-16 Thread Ben Hanson
When SA 3.0 became available, I upgraded from the Redhat RPM's, and had 
various problems with versions and functionality.  I removed the RPM and 
upgraded via CPAN with absolutely no issues.
Ben Hanson
I.S. MGR
Transprint USA Inc.



Re: Yum update of SA from 2.63 to 3.0x

2004-12-16 Thread Kenneth Porter
--On Thursday, December 16, 2004 10:16 AM -0500 Theo Van Dinter 
[EMAIL PROTECTED] wrote:

I don't think there's a way to avoid the perllocal.pod bit (if there is,
somebody tell me!)  The real lesson here is: don't build RPMs as root if
you want to make sure nothing on the system will be modified by the build.
Even if that was modified, it shouldn't show up in the list of unpackaged 
files unless the build root was set to /. A check of files in /usr/lib/rpm 
suggests that it's not set by default, so unless the spec file suggests a 
default, you can hose the live system. It looks like spamassassin.spec sets 
it to /var/tmp/spamassassin-root which should be safe, so I don't see how a 
file in /usr/lib/perl5 is getting inspected.


Re: Yum update of SA from 2.63 to 3.0x

2004-12-16 Thread Chris Barnes
Chris Barnes [EMAIL PROTECTED] wrote:
 So how do I go about resurrecting SA so that it runs now?

Just for grins, I downloaded the CPAN version (which shows to be 3.0.2) 
and used the instructions there.  The install went off without any error 
messages, but I get the same results as before.

Fwiw, issuing the command spamassassin -V gives me:
SpamAssassin version 3.0.2
  running on Perl version 5.8.3


--

+ + + + + + + + + + + + + + + + + + + + + + + + + + + + + +
Chris Barnes   AOL IM: CNBarnes
[EMAIL PROTECTED]Yahoo IM: chrisnbarnes





Re: Yum update of SA from 2.63 to 3.0x

2004-12-16 Thread Kenneth Porter
--On Thursday, December 16, 2004 11:19 AM -0600 Chris Barnes 
[EMAIL PROTECTED] wrote:

Just for grins, I downloaded the CPAN version (which shows to be 3.0.2)
and used the instructions there.  The install went off without any error
messages, but I get the same results as before.
IOW, sa-learn still fails? What about SA itself? Does it work against the 
sample messages?


Re: Yum update of SA from 2.63 to 3.0x

2004-12-16 Thread Chris Barnes
Kenneth Porter [EMAIL PROTECTED] wrote:
 IOW, sa-learn still fails? What about SA itself? Does it work against
 the sample messages?

Nope.


[EMAIL PROTECTED] Mail-SpamAssassin-3.0.2]# spamassassin 
sample-nonspam.txt
Created user preferences file: /root/.spamassassin/user_prefs
Use of uninitialized value in numeric eq (==) at 
/usr/lib/perl5/site_perl/5.8.3/Mail/SpamAssassin/Conf/Parser.pm line 
730.
Use of uninitialized value in numeric eq (==) at 
/usr/lib/perl5/site_perl/5.8.3/Mail/SpamAssassin/Conf/Parser.pm line 
730.
Use of uninitialized value in numeric eq (==) at 
/usr/lib/perl5/site_perl/5.8.3/Mail/SpamAssassin/Conf/Parser.pm line 
730.
Use of uninitialized value in numeric eq (==) at 
/usr/lib/perl5/site_perl/5.8.3/Mail/SpamAssassin/Conf/Parser.pm line 
730.
Use of uninitialized value in numeric eq (==) at 
/usr/lib/perl5/site_perl/5.8.3/Mail/SpamAssassin/Conf/Parser.pm line 
730.
Use of uninitialized value in numeric eq (==) at 
/usr/lib/perl5/site_perl/5.8.3/Mail/SpamAssassin/Conf/Parser.pm line 
730.
Use of uninitialized value in numeric eq (==) at 
/usr/lib/perl5/site_perl/5.8.3/Mail/SpamAssassin/Conf/Parser.pm line 
730.
Use of uninitialized value in numeric eq (==) at 
/usr/lib/perl5/site_perl/5.8.3/Mail/SpamAssassin/Conf/Parser.pm line 
730.
Use of uninitialized value in numeric eq (==) at 
/usr/lib/perl5/site_perl/5.8.3/Mail/SpamAssassin/Conf/Parser.pm line 
730.
Use of uninitialized value in numeric eq (==) at 
/usr/lib/perl5/site_perl/5.8.3/Mail/SpamAssassin/Conf/Parser.pm line 
730.
Use of uninitialized value in numeric eq (==) at 
/usr/lib/perl5/site_perl/5.8.3/Mail/SpamAssassin/Conf/Parser.pm line 
730.
Use of uninitialized value in numeric eq (==) at 
/usr/lib/perl5/site_perl/5.8.3/Mail/SpamAssassin/Conf/Parser.pm line 
730.
Use of uninitialized value in numeric eq (==) at 
/usr/lib/perl5/site_perl/5.8.3/Mail/SpamAssassin/Conf/Parser.pm line 
730.
Use of uninitialized value in numeric eq (==) at 
/usr/lib/perl5/site_perl/5.8.3/Mail/SpamAssassin/Conf/Parser.pm line 
730.
Use of uninitialized value in numeric eq (==) at 
/usr/lib/perl5/site_perl/5.8.3/Mail/SpamAssassin/Conf/Parser.pm line 
730.
Use of uninitialized value in bitwise and () at 
/usr/lib/perl5/site_perl/5.8.3/Mail/SpamAssassin/Conf/Parser.pm line 
640.
Use of uninitialized value in numeric eq (==) at 
/usr/lib/perl5/site_perl/5.8.3/Mail/SpamAssassin/Conf/Parser.pm line 
678.
Use of uninitialized value in numeric eq (==) at 
/usr/lib/perl5/site_perl/5.8.3/Mail/SpamAssassin/Conf/Parser.pm line 
678.
Use of uninitialized value in numeric eq (==) at 
/usr/lib/perl5/site_perl/5.8.3/Mail/SpamAssassin/Conf/Parser.pm line 
678.
Use of uninitialized value in numeric eq (==) at 
/usr/lib/perl5/site_perl/5.8.3/Mail/SpamAssassin/Conf/Parser.pm line 
678.
Use of uninitialized value in numeric eq (==) at 
/usr/lib/perl5/site_perl/5.8.3/Mail/SpamAssassin/Conf/Parser.pm line 
678.
Use of uninitialized value in numeric eq (==) at 
/usr/lib/perl5/site_perl/5.8.3/Mail/SpamAssassin/Conf/Parser.pm line 
678.
Use of uninitialized value in concatenation (.) or string at 
/usr/lib/perl5/site_perl/5.8.3/Mail/SpamAssassin/Conf/Parser.pm line 
707.
unknown type  for RCVD_IN_4: 18 at 
/usr/lib/perl5/site_perl/5.8.3/Mail/SpamAssassin.pm line 1682.

--

+ + + + + + + + + + + + + + + + + + + + + + + + + + + + + +
Chris Barnes   AOL IM: CNBarnes
[EMAIL PROTECTED]Yahoo IM: chrisnbarnes





Re: Yum update of SA from 2.63 to 3.0x

2004-12-16 Thread Michael Parker
On Thu, Dec 16, 2004 at 11:42:29AM -0600, Chris Barnes wrote:
 Kenneth Porter [EMAIL PROTECTED] wrote:
  IOW, sa-learn still fails? What about SA itself? Does it work against
  the sample messages?
 
 Nope.
 
 
 [EMAIL PROTECTED] Mail-SpamAssassin-3.0.2]# spamassassin 
 sample-nonspam.txt
 Created user preferences file: /root/.spamassassin/user_prefs
 Use of uninitialized value in numeric eq (==) at 

Just checking, you did read UPGRADE right?

Run spamassassin --lint and fixed any problems?

Michael


pgpWLL7hfjnRS.pgp
Description: PGP signature


Re: Yum update of SA from 2.63 to 3.0x (SOLVED)

2004-12-16 Thread Chris Barnes
I went ahead and filed a bugzilla report and there Theo made the 
comment:
 At first glance, it looks like you have a bad configuration.

This was probably and off-handed remark, but for me it provided a good 
clue.  I renamed my old /etc/mail/spamassassin/local.cf to .old and 
copied the local.cf.rpmbuild to local.cf and used it 'as-is'.  Restarted 
SA and everything now works.

Perhaps something in the UPDATE file and website should be included to 
only re-used old custom rules only after the install/upgrade?


--

+ + + + + + + + + + + + + + + + + + + + + + + + + + + + + +
Chris Barnes   AOL IM: CNBarnes
[EMAIL PROTECTED]Yahoo IM: chrisnbarnes





Yum update of SA from 2.63 to 3.0x

2004-12-15 Thread Chris Barnes
Does anyone have a good yum update repository to upgrade SA to 3.x (from
2.63)?

Is an update like that recommended?



--

+ + + + + + + + + + + + + + + + + + + + + + + + + + + + + +
Chris Barnes   AOL IM: CNBarnes
[EMAIL PROTECTED]Yahoo IM: chrisnbarnes 





Re: Yum update of SA from 2.63 to 3.0x

2004-12-15 Thread Kenneth Porter
--On Wednesday, December 15, 2004 3:11 PM -0600 Chris Barnes 
[EMAIL PROTECTED] wrote:

Does anyone have a good yum update repository to upgrade SA to 3.x (from
2.63)?
Is an update like that recommended?
I haven't used Red Hat's SA packages for some time. Just grab the tarball 
from the SA site and rebuild it into an RPM with the command line provided 
on the download page. I've been using that from RH7.2 through FC2, now with 
SA 3.0. (Have to get around to upgrading to 3.0.1, but might wait for 
3.0.2.)




Re: Yum update of SA from 2.63 to 3.0x

2004-12-15 Thread Chris Barnes
Kenneth Porter [EMAIL PROTECTED] wrote:
 I haven't used Red Hat's SA packages for some time. Just grab the
 tarball from the SA site and rebuild it into an RPM with the command
 line provided on the download page. I've been using that from RH7.2
 through FC2, now with SA 3.0. (Have to get around to upgrading to
 3.0.1, but might wait for 3.0.2.)

No dice - downloaded and when I ran the:
rpmbuild -tb Mail-SpamAssassin-3.0.1.tar.gz

I got:
warning: Installed (but unpackaged) file(s) found:
   /usr/lib/perl5/5.8.3/i386-linux-thread-multi/perllocal.pod
Wrote: /usr/src/redhat/RPMS/i386/spamassassin-3.0.1-1.i386.rpm


SA isn't running at all now.

Just as a test I tried to issue a sa-learn --dump magic and got the 
following output:
Use of uninitialized value in numeric eq (==) at 
/usr/lib/perl5/site_perl/5.8.3/Mail/SpamAssassin/Conf/Parser.pm line 
678.
Use of uninitialized value in concatenation (.) or string at 
/usr/lib/perl5/site_perl/5.8.3/Mail/SpamAssassin/Conf/Parser.pm line 
707.
===   the above were repeated many times ===
unknown type  for RCVD_IN_4: 18 at 
/usr/lib/perl5/site_perl/5.8.3/Mail/SpamAssassin.pm line 1671.


--

+ + + + + + + + + + + + + + + + + + + + + + + + + + + + + +
Chris Barnes   AOL IM: CNBarnes
[EMAIL PROTECTED]Yahoo IM: chrisnbarnes