You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@spamassassin.apache.org by Jari Fredriksson <ja...@iki.fi> on 2007/06/14 21:53:48 UTC

3.2.1 is a failure?

Was worried while reading complaints on users... but still tried to install.

I have two systems, one originally a Red Hat 7.3, but most things later compiled from source, including gcc 4.0.0 and perl from cpan

Another is a Debian Etch, perl from debian repo.

I tried to install SpamAssassin 3.2.1 to those, but they did not install. I had to install some prerequisities  as they complained, and those went find. My earlier version was 3.2.0 and it installed fine on both systems.

Both installation tries were via cpan, and here is the result. 


t/zz_cleanup................ok
Failed Test                Stat Wstat Total Fail  List of Failed
-------------------------------------------------------------------------------
t/spamc_optC.t                            9    4  2 4 6 8
t/spamc_optL.t                           16   16  1-16
t/spamd_allow_user_rules.t                5    1  4
t/spamd_plugin.t                          6    3  2 4 6
24 tests skipped.
Failed 4/129 test scripts. 24/1922 subtests failed.
Files=129, Tests=1922, 2646 wallclock secs (1217.93 cusr + 55.31 csys = 1273.24 CPU)
Failed 4/129 test programs. 24/1922 subtests failed.
make: *** [test_dynamic] Error 29
  JMASON/Mail-SpamAssassin-3.2.1.tar.gz
  /usr/bin/make test -- NOT OK
Running make install
  make test had returned bad status, won't install without force
Failed during this command:
 JMASON/Mail-SpamAssassin-3.2.1.tar.gz        : make_test NO



Re: 3.2.1 is a failure?

Posted by Sidney Markowitz <si...@sidney.com>.
Jari Fredriksson wrote, On 15/6/07 7:53 AM:
> Both installation tries were via cpan, and here is the result.

That looks like bug 5510, about failing tests when they are run s root,
which breaks CPAN installation in the common setup in which the build
and test are run as root. I think you can configure CPAN to allow you to
run it as user by configuring the installation step to be done with sudo
make install, which would allow a workaround. It's somewhat tricky to
change over to that from running CPAN itself as root as you may have to
change ownership of various CPAN build directories that have been
created owned by root.

http://issues.apache.org/SpamAssassin/show_bug.cgi?id=5510

See the comments there for details about what the bug is and what is
being done about it.

 -- sidney

Re: 3.2.1 is a failure?

Posted by Sidney Markowitz <si...@sidney.com>.
Jari Fredriksson wrote, On 15/6/07 7:53 AM:
> Both installation tries were via cpan, and here is the result.

That looks like bug 5510, about failing tests when they are run s root,
which breaks CPAN installation in the common setup in which the build
and test are run as root. I think you can configure CPAN to allow you to
run it as user by configuring the installation step to be done with sudo
make install, which would allow a workaround. It's somewhat tricky to
change over to that from running CPAN itself as root as you may have to
change ownership of various CPAN build directories that have been
created owned by root.

http://issues.apache.org/SpamAssassin/show_bug.cgi?id=5510

See the comments there for details about what the bug is and what is
being done about it.

 -- sidney