Date: Sun, 26 Mar 2006 08:30:04 -0500 From: "Michael P. Soulier" <msoulier@digitaltorque.ca> To: freebsd-questions@freebsd.org Subject: Re: spamassassin build failure Message-ID: <20060326133003.GN12075@tigger.digitaltorque.ca> In-Reply-To: <20060326081715.GA22633@happy-idiot-talk.infracaninophile.co.uk> References: <20060326031840.GC12075@tigger.digitaltorque.ca> <20060326081715.GA22633@happy-idiot-talk.infracaninophile.co.uk>
next in thread | previous in thread | raw e-mail | index | archive | help
[-- Attachment #1 --] On 26/03/06 Matthew Seaman said: > Did you run the perl-after-upgrade script with the '-f' flag so it > actually does anything? This symptom occurs when the pkg system > thinks a package is installed (because there's an entry in > /var/db/pkgs) but perl can't find the corresponding module, because > it's in /usr/local/lib/perl5/site_perl/5.8.X with X != 8. perl-after-upgrade -f seems to have fixed the problem. As I think I only went from perl 5.6 to 5.8, I'm surprised that so much would be out of date. Good to know though. Do the other scripting languages have this kind of support? Python? Mike -- Michael P. Soulier <msoulier@digitaltorque.ca> "Any intelligent fool can make things bigger and more complex... It takes a touch of genius - and a lot of courage to move in the opposite direction." --Albert Einstein [-- Attachment #2 --] -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.2 (GNU/Linux) iD8DBQFEJpdbKGqCc1vIvggRAshkAJ9Bnd9BdP8MsySEBwt8M9trXdHGmQCfUY0F JtJrvtsLuZHrsTTB/G2Sh+s= =v0vA -----END PGP SIGNATURE-----
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20060326133003.GN12075>