Somehow you have Python2.7 files already present in /Application/MacPorts/Python2.7.
I'm mostly curious how that occurred, which is likely what Russell hinted: MacPorts was only partially removed at some point. But yes, I'd recommend letting MacPorts take over its own directory again via forcing activation. On Jul 3, 2015, at 10:46 AM, Floriane B wrote: > Error: org.macports.activate for port python27 returned: Image error: > /Applications/MacPorts/Python 2.7/IDLE.app/Contents/Info.plist already exists > and does not belong to a registered port. Unable to activate port python27. > Use 'port -f activate python27' to force the activation. > Error: Failed to install python27 > Please see the log file for port python27 for details: > > /opt/local/var/macports/logs/_opt_local_var_macports_sources_rsync.macports.org_release_tarballs_ports_lang_python27/python27/main.log > Error: The following dependencies were not installed: py27-setuptools python27 > To report a bug, follow the instructions in the guide: > http://guide.macports.org/#project.tickets > Error: Processing of port py27-igraph failed > > Do you think i should force the activation of port python27 ? > _______________________________________________ macports-users mailing list [email protected] https://lists.macosforge.org/mailman/listinfo/macports-users
