#56900 closed defect (invalid)
mac OSX issue
Reported by: | shattars3d (testtestsp) | Owned by: | |
---|---|---|---|
Priority: | Normal | Milestone: | |
Component: | ports | Version: | |
Keywords: | Cc: | ||
Port: | python27 |
Description (last modified by mf2k (Frank Schima))
trying to compile FreeRDP open source client, which requires mac ports.
I am retrieving these errors in terminal, while compiling
Error: Failed to activate python27: 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: See /opt/local/var/macports/logs/_opt_local_var_macports_sources_rsync.macports.org_release_tarballs_ports_lang_python27/python27/main.log for details. Error: Follow https://guide.macports.org/#project.tickets to report a bug. Error: Processing of port FreeRDP failed
Change History (6)
comment:1 Changed 6 years ago by mf2k (Frank Schima)
Priority: | High → Normal |
---|
comment:2 Changed 6 years ago by mf2k (Frank Schima)
Keywords: | mac removed |
---|---|
Port: | python27 added |
In the future, please use WikiFormatting, fill in the Port field and add the port maintainer(s) to Cc (port info --maintainers python27
), if any.
comment:3 Changed 6 years ago by mf2k (Frank Schima)
Description: | modified (diff) |
---|
comment:4 Changed 6 years ago by mf2k (Frank Schima)
Resolution: | → invalid |
---|---|
Status: | new → closed |
Based on this:
Error: Failed to activate python27: 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.
Your Macports got corrupted somehow. Perhaps by a 3rd party installer. Since Trac is not for tech support, follow-up on the Macports Users mailing list instead.
comment:5 Changed 6 years ago by kencu (Ken)
Or I suppose you could just
Use 'port -f activate python27' to force the activation.
and then see if that fixes it for you.
comment:6 Changed 6 years ago by jmroot (Joshua Root)
Can happen if Migration Assistant doesn't migrate everything, or sometimes users try to uninstall MacPorts by just deleting /opt/local instead of following the full uninstall instructions. So not necessarily "corrupted". Deleting the existing app bundle from /Applications/MacPorts is a better idea than force-activation as the latter will leave the old files behind with different names.
The Priority field is for use by Macports team members only.