Date: Fri, 8 Jul 2011 09:39:24 -0400 From: Jerry <jerry@seibercom.net> To: FreeBSD <freebsd-questions@freebsd.org> Subject: Re: Perl Problem After Upgrade to 5.12.4 Message-ID: <20110708093924.51ce6916@scorpio> In-Reply-To: <4E170230.1070901@tundraware.com> References: <4E1478C1.3020302@tundraware.com> <80442ff8a0c0f582e6134bde1566a2e8@socruel.nu> <20110708075243.5493e0b1@scorpio> <4E170230.1070901@tundraware.com>
next in thread | previous in thread | raw e-mail | index | archive | help
On Fri, 08 Jul 2011 08:12:16 -0500
Tim Daneliuk articulated:
> I was able to work around this by:
>
> 1) Uninstalling spamassassin and perl 5.12
> 2) Upgrading to perl 5.14
> 3) Running perl-after-upgrade
> 4) Reinstalling spamassassin
That is not exactly the method prescribed in UPDATING:
<quote>
20110517:
AFFECTS: users of lang/perl*
AUTHOR: skv@FreeBSD.org
lang/perl5.14 is out. If you want to switch to it from, for example
lang/perl5.12, that is:
Portupgrade users:
0) Fix pkgdb.db (for safety):
pkgdb -Ff
1) Reinstall new version of Perl (5.14):
env DISABLE_CONFLICTS=1 portupgrade -o lang/perl5.14 -f perl-5.12.\*
2) Reinstall everything that depends on Perl:
portupgrade -fr perl
Portmaster users:
portmaster -o lang/perl5.14 lang/perl5.12
Conservative:
portmaster p5-
Comprehensive (but perhaps overkill):
portmaster -r perl-
Note: If the "perl-" glob matches more than one port you will need to
specify the name of the Perl directory in /var/db/pkg explicitly.
</quote>
I used the "portupgrade" method without incident. From what I have been
told, "perl-after-upgrade" != "env DISABLE_CONFLICTS=1 portupgrade -o lang/perl5.14 -f perl-5.12.\*"
As always, YMMV!
--
Jerry ✌
jerry+fbsd@seibercom.net
Disclaimer: off-list followups get on-list replies or ignored.
Do not CC this poster. Please do not ignore the "Reply-To" header.
http://www.catb.org/~esr/faqs/smart-questions.html
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20110708093924.51ce6916>