Changes between Initial Version and Version 1 of Ticket #63432


Ignore:
Timestamp:
Sep 1, 2021, 8:12:22 PM (3 years ago)
Author:
ryandesign (Ryan Carsten Schmidt)
Comment:

It seems unlikely that this is a bug in MacPorts base or in any MacPorts port. It seems more likely that something outside of MacPorts installed this file into the MacPorts prefix, thereby causing this problem for MacPorts. The solution would be to manually remove the file and to refrain from running whatever process put those files there in the first place.

Legend:

Unmodified
Added
Removed
Modified

  • Ticket #63432

    • Property Port py-six added
    • Property Milestone changed from MacPorts Future to
    • Property Summary changed from py39-six error when required by jupyter-notebook: six.cpython-39.pyc already exists and does not belong to a registered port to py39-six: six.cpython-39.pyc already exists and does not belong to a registered port

  • Ticket #63432 – Description

    initial v1  
    1414}}}
    1515
    16 I followed the  migration instructions [https://trac.macports.org/wiki/Migration] to start with a fresh installation. 
     16I followed the  migration instructions wiki:Migration to start with a fresh installation. 
    1717
    18 After uninstalling all of my ports and cleaning partial builds (steps c and d), I followed the instructions at [https://trac.macports.org/wiki/ProblemHotlist#reinstall-clt] to reinstall the command line tools.
     18After uninstalling all of my ports and cleaning partial builds (steps c and d), I followed the instructions at ProblemHotlist#reinstall-clt to reinstall the command line tools.
    1919
    2020After reinstalling the command line tools, I used the script restore_ports.tcl to re-install my previous ports and at first py39-six appeared to install correctly: