'sudo port upgrade outdated' perl5.8->perl5.12 problem

Ryan Schmidt ryandesign at macports.org
Tue Mar 22 18:12:19 PDT 2011

On Mar 22, 2011, at 18:12, Scott Webster wrote:

> On Tue, Mar 22, 2011 at 4:08 PM, Lars Sonchocky-Helldorf wrote:
>> Hi,
>> I've got the following problem with upgrading perl when doing an 'sudo port upgrade outdated':
>> --->  Activating perl5 @5.12.3_1+perl5_12
>> Error: Target org.macports.activate returned: Image error: /opt/local/bin/a2p is being used by the active perl5.8 port.  Please deactivate this port first, or use 'port -f activate perl5' to force the activation.
> Probably your perl5.8 installation got deactivated after this error
> happened, so you can now activate perl5 (without forcing) without
> problems.  This isn't the usual situation... there is a bunch of
> discussion in the list archives if you want to do some more reading :)
> Scott

It sounds like Lars' situation is that perl5.8 did *not* get deactivated. Unfortunately, with the way the upgrade to perl 5.12 was handled, this *is* normal (all users will experience this problem), and requires the user to manually deactivate perl5.8, before proceeding to activate the new perl5.

More information about the macports-users mailing list