unable to activate py36-google-pasta

[Antwnina (Antonina)]

MacBook-Pro:temp adpk$ sudo port install py36-tensorflow
Password:
--->  Computing dependencies for py36-tensorboard
--->  Fetching archive for py36-tensorboard
--->  Attempting to fetch py36-tensorboard-1.14.0_1.darwin_18.noarch.tbz2 from http://nue.de.packages.macports.org/py36-tensorboard
--->  Attempting to fetch py36-tensorboard-1.14.0_1.darwin_18.noarch.tbz2.rmd160 from http://nue.de.packages.macports.org/py36-tensorboard
--->  Installing py36-tensorboard @1.14.0_1
--->  Cleaning py36-tensorboard
--->  Computing dependencies for py36-tensorboard
--->  Deactivating py36-tensorboard @1.14.0_0
--->  Cleaning py36-tensorboard
--->  Activating py36-tensorboard @1.14.0_1
--->  Cleaning py36-tensorboard
--->  Computing dependencies for py36-tensorflow
The following dependencies will be installed: 
 py36-google-pasta
 py36-tensorflow_estimator
Continue? [Y/n]: y
--->  Fetching archive for py36-google-pasta
--->  Attempting to fetch py36-google-pasta-0.1.7_0.darwin_18.noarch.tbz2 from http://nue.de.packages.macports.org/py36-google-pasta
--->  Attempting to fetch py36-google-pasta-0.1.7_0.darwin_18.noarch.tbz2.rmd160 from http://nue.de.packages.macports.org/py36-google-pasta
--->  Installing py36-google-pasta @0.1.7_0
--->  Activating py36-google-pasta @0.1.7_0
Error: Failed to activate py36-google-pasta: Image error: /opt/local/Library/Frameworks/Python.framework/Versions/3.6/lib/python3.6/site-packages/pasta/__init__.py already exists and does not belong to a registered port.  Unable to activate port py36-google-pasta. Use 'port -f activate py36-google-pasta' to force the activation.
Error: See /opt/local/var/macports/logs/_opt_local_var_macports_sources_rsync.macports.org_macports_release_tarballs_ports_python_py-google-pasta/py36-google-pasta/main.log for details.
Error: Follow https://guide.macports.org/#project.tickets to report a bug.
Error: Processing of port py36-tensorflow failed

[jmroot (Joshua Root)]

As the message says, you have existing files (that weren't installed by any port MacPorts knows about) with the same names as those that this port is trying to install, creating a conflict. There is no bug in the port here, you just need to take care of the conflicting files.