Here one such example :

--->  Installing py36-six @1.11.0_0
--->  Activating py36-six @1.11.0_0
Error: Failed to activate py36-six: Image error: 
 already exists and does not belong to a registered port.  Unable to activate 
port py36-six. Use 'port -f activate py36-six' to force the activation.
Error: See 
 for details.
Error: Problem while installing py36-six
Error: Follow to report a bug.


sudo port -f activate py36-six
--->  Computing dependencies for py36-six
--->  Activating py36-six @1.11.0_0
Warning: File 
 already exists.  Moving to: 
--->  Cleaning py36-six

and then I relaunch upgrade outdated…


> Le 16 avr. 2018 à 15:14, Chris Jones <> a écrit :
> Please post examples of the warning/error messages you are getting...
> On 16/04/18 14:12, pagani laurent via macports-users wrote:
>> Hi all,
>> I just moved to the new 2.4.3 by running port selfupdate and tried to 
>> follow-up with a port upgrade outdated but it keeps stumbling on many ports 
>> claiming they were installed by third parties. Which is not the case and I 
>> did not uninstall Port either. So I don’t know why the upgrade keeps 
>> stumbling.
>> I can force the activation and restart the upgrade but it repeatedly 
>> stumble, so this becomes tiresome.
>> The webpage suggests to uninstall everything and reinstall them but this 
>> seems a bit violent with the risk to forget a number of packages. Can’t we 
>> just tell Macports to force installation each time it is needed ?
>> Laurent
>> There is a theory which states that if ever anybody discovers exactly what 
>> the Universe is for and why it is here, it will instantly disappear and be 
>> replaced by something even more bizarre and inexplicable. There is another 
>> theory which states that this has already happened.
>> Douglas Adams

Reply via email to