You are viewing a plain text version of this content. The canonical link for it is here.
Posted to users@spamassassin.apache.org by ji...@jidanni.org on 2010/02/14 01:02:10 UTC

spamassassin script is v3.003000, but using modules v3.004000

Help, I dared to update from SVN, and now spamassassin refuses to run:
$ svn update
$ make install
$ sa-update --install <by hand the newest files I could find on http://daryl.dostech.ca/sa-update/asf/>
$ spamassassin
spamassassin: spamassassin script is v3.003000, but using modules v3.004000

Re: spamassassin script is v3.003000, but using modules v3.004000

Posted by ji...@jidanni.org.
MM> The usual procedure is:
MM>   perl Makefile.PL; make; make test; make install
Ah, that now works only once! Now only
  set -e; perl Makefile.PL; make clean; perl Makefile.PL; make; make install
will work each time, even if a few months pass between one's upgrades.
Hmmm, they might want to document that.
I chucked your "make test" as it was taking too long.

Re: spamassassin script is v3.003000, but using modules v3.004000

Posted by Mark Martinec <Ma...@ijs.si>.
On Sunday February 14 2010 01:02:10 jidanni@jidanni.org wrote:
> Help, I dared to update from SVN, and now spamassassin refuses to run:
> $ svn update
> $ make install

The usual procedure is:
  perl Makefile.PL; make; make test; make install

> $ sa-update --install <by hand the newest files I could find on
>  http://daryl.dostech.ca/sa-update/asf/> $ spamassassin
> spamassassin: spamassassin script is v3.003000, but using modules v3.004000

It should be alright to use the SVN trunk version, I'm using it here.

> spamassassin: spamassassin script is v3.003000, but using modules v3.004000

Apparently you updated the modules but somehow the spamassassin program
was not updated, or was installed in a different location that your
old 3.3.0 spamassassin. Please check your paths, perhaps you have
the two versions installed at different locations, or perhaps the
'make install' failed to install the 'spamassassin' program.

  Mark

Re: spamassassin script is v3.003000, but using modules v3.004000

Posted by ji...@jidanni.org.
Maybe they changed something. In the past
perl Makefile.PL PREFIX=$HOME/.spamassassin-tree
also took care of where bin/spamassassin went. Now it seems left behind,
due to this suspicious commented out code?

# needs to be added to MY::install if used
#bin__install: $(INST_SCRIPT)/sa-filter
#        # $(RM_F) $(B_SCRIPTDIR)/spamassassin
#        # $(SYMLINK) $(INST_SCRIPT)/sa-filter $(B_SCRIPTDIR)/spamassassin

Re: spamassassin script is v3.003000, but using modules v3.004000

Posted by Robert Nicholson <ro...@gmail.com>.
How many spamassassin's do you have?

Isn't it saying the script in bin isn't matching the modules in lib

On Feb 13, 2010, at 6:02 PM, jidanni@jidanni.org wrote:

> Help, I dared to update from SVN, and now spamassassin refuses to run:
> $ svn update
> $ make install
> $ sa-update --install <by hand the newest files I could find on http://daryl.dostech.ca/sa-update/asf/>
> $ spamassassin
> spamassassin: spamassassin script is v3.003000, but using modules v3.004000