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

Lars Sonchocky-Helldorf lars.sonchocky-helldorf at hamburg.de
Tue Mar 22 16:08:32 PDT 2011


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.

Obviously 'a2p' (whatever port that is – I didn't request it by itself) is still depending on the old perl. What is the macports policy when upgrading tributary ports given the port depending on those isn't outdated? Is this a special case where manual interaction is mandatory or is the idea of 'port upgrade outdated' that it should be able to run unattended?

Btw. when I was hitting that bugger macports told me to file a bugreport. Should I go forward with this?



attached are the output of the command and the log for perl.

-------------- next part --------------
An embedded and charset-unspecified text was scrubbed...
Name: 'sudo port upgrade outdated' perl5.8->perl5.12 problem.txt
URL: <http://lists.macosforge.org/pipermail/macports-users/attachments/20110323/4ee36bbe/attachment.txt>
-------------- next part --------------

-------------- next part --------------
A non-text attachment was scrubbed...
Name: _opt_local_var_macports_sources_rsync.macports.org_release_ports_lang_perl5.zip
Type: application/zip
Size: 7264 bytes
Desc: not available
URL: <http://lists.macosforge.org/pipermail/macports-users/attachments/20110323/4ee36bbe/attachment.zip>
-------------- next part --------------

More information about the macports-users mailing list