problem with upgrading macport installed packages
ctreleaven at cogeco.ca
Tue Apr 17 00:33:23 UTC 2018
> On Apr 16, 2018, at 4:23 PM, Ryan Schmidt <ryandesign at macports.org> wrote:
> On Apr 16, 2018, at 08:37, pagani laurent wrote:
>> 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: /opt/local/Library/Frameworks/Python.framework/Versions/3.6/lib/python3.6/site-packages/__pycache__/six.cpython-36.pyc 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 /opt/local/var/macports/logs/_opt_local_var_macports_sources_rsync.macports.org_release_tarballs_ports_python_py-six/py36-six/main.log for details.
>> Error: Problem while installing py36-six
>> Error: Follow https://guide.macports.org/#project.tickets to report a bug.
> Only MacPorts should install software in /opt/local, but MacPorts states above that it did not install this file. So how did it get there? If you don't know, the safest thing to do is uninstall MacPorts and all ports, following the uninstallation instructions on the web site, and then reinstall MacPorts and the ports you want.
The unregistered files could possibly be from a badly-built installer package? Or the registry file got nuked at some point.
More information about the macports-users