Re: 3.1.1 Upgrade Problems [solved]

> > Replying to myself... I upgraded Archive::Tar and the error is gone now. > > To what version? > >From 1.00 to 1.29. Dale

Re: 3.1.1 Upgrade Problems [solved]

Dale Blount wrote: On Fri, Mar 17, 2006 at 08:18:35PM -0800, Dan Kohn wrote: Anything else to try? Nothing comes to mind. It looks like a bug in IO::Zlib or perl on your platform. Anyone else on FreeBSD having simliar problems? I'm having this problem on Arch Linux with IO::Zlib 1.0.4. Re

Re: 3.1.1 Upgrade Problems [solved]

> > On Fri, Mar 17, 2006 at 08:18:35PM -0800, Dan Kohn wrote: > >> Anything else to try? > > > > Nothing comes to mind. It looks like a bug in IO::Zlib or perl on > > your platform. > > > > Anyone else on FreeBSD having simliar problems? > > > I'm having this problem on Arch Linux with IO::Zlib

Re: 3.1.1 Upgrade Problems

something like: > > #!/usr/bin/perl > use IO::Zlib; > $tfh = IO::Zlib->new("file.gz", "rb"); > I don't. Running this script completes without error. -- View this message in context: http://www.nabble.com/Re%3A-3.1.1-Upgrade-Problems-t1301352.html#a3618437 Sent from the SpamAssassin - Users forum at Nabble.com.

Re: 3.1.1 Upgrade Problems

-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Theo Van Dinter wrote: > On Fri, Mar 17, 2006 at 08:18:35PM -0800, Dan Kohn wrote: >> Anything else to try? > > Nothing comes to mind. It looks like a bug in IO::Zlib or perl on > your platform. > > Anyone else on FreeBSD having simliar problems? F

Re: 3.1.1 Upgrade Problems

On Fri, Mar 17, 2006 at 09:30:47PM -0800, Dan Kohn wrote: > OK, but it would be really nice if sa-update failing didn't kill the > spamassassin installation. Feel free to open a BZ ticket about it. I'm not sure what/if things can be changed (the directory is created for temp usage during proces

Re: 3.1.1 Upgrade Problems

OK, but it would be really nice if sa-update failing didn't kill the spamassassin installation. - dan -- Dan Kohn On Mar 17, 2006, at 9:26 PM, Theo Van Dinter wrote: On Fri, Mar 17, 2006 at 08:18:35PM -0800, Dan Kohn wrote:

Re: 3.1.1 Upgrade Problems

On Fri, Mar 17, 2006 at 08:18:35PM -0800, Dan Kohn wrote: > Anything else to try? Nothing comes to mind. It looks like a bug in IO::Zlib or perl on your platform. Anyone else on FreeBSD having simliar problems? > [65993] dbg: channel: populating temp content file > [65993] dbg: gpg: populating

Re: 3.1.1 Upgrade Problems

[emlis:~/src/Mail-SpamAssassin-3.1.0]$ perl -MIO::Zlib -e 'print $IO::Zlib::VERSION,"\n"' 1.01 I then installed 1.04 off of $HOME and got the following output from sa-update. This also broke SpamAssassin again until I deleted $HOME/ var/spamassassin. I definitely think you're going to need

Re: 3.1.1 Upgrade Problems

On Fri, Mar 17, 2006 at 05:57:48PM -0800, Dan Kohn wrote: > [92376] dbg: channel: file verification passed, installing update > [92376] dbg: channel: cleaning out update directory > Not a GLOB reference at /usr/local/lib/perl5/site_perl/5.8.0/IO/ > Zlib.pm line 317. Hrm. What version of IO::Zlib

Re: 3.1.1 Upgrade Problems

Thanks, Theo. Here's 3.1.1 reinstalled and then a bug from sa- update. However, I got 3.1.1 working again with 'rm -rf var' (which only had spamassassin stuff in it). I would consider, for SA 3.2, not creating the var directories until after the sa-update has succeeded, as I suspect I won

Re: 3.1.1 Upgrade Problems

On Fri, Mar 17, 2006 at 05:34:02PM -0800, Dan Kohn wrote: > Guys, I'm seeing similar problems with my non-root install on a > FreeBSD hosting account, where prefix=$HOME. With SpamAssassin > 3.1.1, I only get this header added: Jason's problem, as far as I can tell, was related to permission

Re: 3.1.1 Upgrade Problems

[Frustrating. I had to resend this message after removing all GTUBE strings. - dan *] Guys, I'm seeing similar problems with my non-root install on a FreeBSD hosting account, where prefix=$HOME. With SpamAssassin 3.1.1, I only get this header added: X-Spam-Checker-Version: SpamAssassin

Re: 3.1.1 Upgrade Problems

On Wed, Mar 15, 2006 at 02:02:43PM -0800, Jason Self wrote: > I fed sample-spam.txt into SpamAssassin at the command line. It > correctly added things such as these into the message: > > X-Spam-Flag: YES > X-Spam-Checker-Version: SpamAssassin 3.1.1 (2006-03-10) on bluehome.net > X-Spam-Level:

Re: 3.1.1 Upgrade Problems

OK; All of the earlier stuff has been deleted along with: rm -fr /Library/Perl/5.8.7/darwin-2level/auto/Mail/SpamAssassin rm -fr /Library/Perl/5.8.7/Mail/SpamAssassin rm -fr /Library/Perl/5.8.7/Mail/SpamAssassin/Plugin/SpamCop.pm rm -fr /Library/Perl/5.8.7/Mail/SpamAssassin/SpamdForkScaling.pm rm

Re: 3.1.1 Upgrade Problems

On Wed, Mar 15, 2006 at 12:44:55PM -0800, Jason Self wrote: > /Library/Perl/5.8.1/Mail/SpamAssassin > /Library/Perl/5.8.1/Mail/SpamAssassin.pm > /Library/Perl/5.8.7/Mail/SpamAssassin > /Library/Perl/5.8.7/Mail/SpamAssassin.pm Ok, you have multiple versions of SA installed. Make sure to also remov

Re: 3.1.1 Upgrade Problems

OK; I ran find / -iname "*spamassassin*" to locate all of the SpamAssassin components. The following were deleted. Now I'm going to re-attempt to install 3.1.1. I'll let you know what happens. /Library/Perl/5.8.1/darwin-thread-multi-2level/auto/Mail/SpamAssassin /Library/Perl/5.8.1/Mail/SpamAssass

Re: 3.1.1 Upgrade Problems

On Wed, Mar 15, 2006 at 06:27:10PM +, Justin Mason wrote: > actually, the warnings in Node.pm give me an idea. Could it be something > to do with the new code that fixes CRLF-vs-LF line-ending issues -- Jason, > what OS/filesystems are you using? I don't see how line endings would be involved

Re: 3.1.1 Upgrade Problems

Using OS X Server 10.3.9. Filesystem is journaled HFS+. On 3/15/06, Justin Mason <[EMAIL PROTECTED]> wrote: > actually, the warnings in Node.pm give me an idea. Could it be something > to do with the new code that fixes CRLF-vs-LF line-ending issues -- Jason, > what OS/filesystems are you using?

Re: 3.1.1 Upgrade Problems

Theo Van Dinter writes: > On Wed, Mar 15, 2006 at 09:29:26AM -0800, Jason Self wrote: > > After upgrading to SpamAssassin 3.1.1 via CPAN, I've noticed that > > various headers such as X-Spam-Level and X-Spam-Status no longer > > appear in any messages. > > > > spamassassin --lint produces no erro

Re: 3.1.1 Upgrade Problems

On Wed, Mar 15, 2006 at 09:29:26AM -0800, Jason Self wrote: > After upgrading to SpamAssassin 3.1.1 via CPAN, I've noticed that > various headers such as X-Spam-Level and X-Spam-Status no longer > appear in any messages. > > spamassassin --lint produces no errors (no output at all, actually.) > >

3.1.1 Upgrade Problems

After upgrading to SpamAssassin 3.1.1 via CPAN, I've noticed that various headers such as X-Spam-Level and X-Spam-Status no longer appear in any messages. spamassassin --lint produces no errors (no output at all, actually.) SpamAssassin is invoked via Procmail. I turned on logging and found this