some times not the module is bad - only the test suite has bugs

>  How do I force installation?

simply put the keyword 'force' in front of the cpan command

>cpan

cpan>force install Mail::SPF

if you use PPM, put the '--force' switch at the end of the command line

>  How do I get working versions of modules that do not build?

if the 'make' fails - read the error messages and module readme and try to 
fix the problem (missing env variables, missing Makefile.pl directives, 
missing includes and/or libraries, missing product installations ....)
for example:

to 'make' DBD::mysql, you need to install the mysql client binary package 
first
to 'make' BerkeleyDB, you need to install the product first
to 'make' File::Scan::ClamAV, you need to install and run clamd/freshclam 
first
to 'make' NetSNMP::agent, you need to install netsnmp first

ASSP_DCC requires dccifd 
ASSP_Razor requires Razor-agent

for the ASSP_OCR : OCR stuff, tesseract and ImageMagick is required - for 
the PDF stuff, a system package that includes a binary 'getpdftext' (like 
pdftk) is required

Simply installing the products (and possibly the perl modules) is a fault. 
Most of them require extended knowledge in configuration (schedules, 
firewall settings, word training, agent-X, backup, recover, repair, cache 
setting ................... )

look in to
http://sourceforge.net/projects/assp/files/ASSP%20V2%20multithreading/ASSP%20V2%20module%20installation/
there are several corrected module sources available (Crypt::GOST, 
Sys::MemInfo, Razor-agent)

Thomas




Von:    James Moe <[email protected]>
An:     For Users of ASSP <[email protected]>
Datum:  17.08.2015 18:42
Betreff:        Re: [Assp-user] Failed PERL module installs



-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

On 08/16/2015 10:30 PM, Thomas Eckardt wrote:

  How do I force installation?
  How do I get working versions of modules that do not build?

>>> Mail::SPF::Query
> this is the SPF module V1 - normaly not used by assp (assp uses per
>  default V2 of SPF - Mail::SPF 2.009) installation failes because
> of an POD (docu) collision with the V2 module
> 
  Hmm. Maybe because of this?

Mail::SPF
<...bunch o' stuff that worked...>
t/00.99-class-misc.t .......... ok
t/10.00-rfc4408.t ............. Bailout called.  Further testing
stopped:  Uncaught error: empty domain label at
/usr/lib/perl5/vendor_perl/5.20.1/Error.pm line 40.
FAILED--Further testing stopped: Uncaught error: empty domain label at
/usr/lib/perl5/vendor_perl/5.20.1/Error.pm line 40.
  JMEHNLE/mail-spf/Mail-SPF-v2.9.0.tar.gz


- -- 
James Moe
moe dot james at sohnen-moe dot com
520.743.3936
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v2

iEYEARECAAYFAlXSDncACgkQzTcr8Prq0ZO+zgCgqTdtOkyQx0d7gF/lvPDw2y4T
PucAoK67t6dHaYJ2HOA04hjBuT4vqJ/R
=4e1t
-----END PGP SIGNATURE-----

------------------------------------------------------------------------------
_______________________________________________
Assp-user mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/assp-user






DISCLAIMER:
*******************************************************
This email and any files transmitted with it may be confidential, legally 
privileged and protected in law and are intended solely for the use of the 

individual to whom it is addressed.
This email was multiple times scanned for viruses. There should be no 
known virus in this email!
*******************************************************

------------------------------------------------------------------------------
_______________________________________________
Assp-user mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/assp-user

Reply via email to