py27-futures @3.2.0_0, concurrent/__init__.py already exists, unable to activate

[johankytt]

When autoinstalling the py27-future port as a dependency the following error is thrown. I tried uninstalling and cleaning the port, but it made no difference. I'm not completely sure if it would be safe to force remove concurrent/__init__.py as suggested in the error report.

--->  Computing dependencies for py27-futures
--->  Fetching archive for py27-futures
--->  Attempting to fetch py27-futures-3.2.0_0.darwin_15.noarch.tbz2 from https://packages.macports.org/py27-futures
--->  Attempting to fetch py27-futures-3.2.0_0.darwin_15.noarch.tbz2.rmd160 from https://packages.macports.org/py27-futures
--->  Installing py27-futures @3.2.0_0
--->  Activating py27-futures @3.2.0_0
Error: Failed to activate py27-futures: Image error: /opt/local/Library/Frameworks/Python.framework/Versions/2.7/lib/python2.7/site-packages/concurrent/__init__.py already exists and does not belong to a registered port.  Unable to activate port py27-futures. Use 'port -f activate py27-futures' to force the activation.
Error: See /opt/local/var/macports/logs/_opt_local_var_macports_sources_rsync.macports.org_release_tarballs_ports_python_py-futures/py27-futures/main.log for details.
Error: Problem while installing py27-futures
Error: Follow https://guide.macports.org/#project.tickets to report a bug.

[mf2k (Frank Schima)]

There is nothing to fix here. You somehow got a contaminated Macports prefix directory. Use the suggested fix:

port -f activate py27-futures

[jmroot (Joshua Root)]

See also wiki:ProblemHotlist#xmlwf