Changes between Version 2 and Version 3 of Ticket #59445


Ignore:
Timestamp:
Oct 23, 2019, 1:22:06 AM (5 years ago)
Author:
ryandesign (Ryan Carsten Schmidt)
Comment:

Dependency cycles are not allowed in MacPorts and the behavior of MacPorts and any associated scripts is undefined if dependency cycles exist. Therefore, portfile authors must ensure that dependency cycles do not exist.

Legend:

Unmodified
Added
Removed
Modified

  • Ticket #59445 – Description

    v2 v3  
    1 I recently updated my macOS version from 10.11 El Capitan to macOS High Sierra 10.13.6. I am following the [https://trac.macports.org/wiki/Migration Migration instructions].
     1I recently updated my macOS version from 10.11 El Capitan to macOS High Sierra 10.13.6. I am following the [wiki:Migration Migration instructions].
    22
    33When I ran the `restore_ports.tcl` script, it failed with the error message:
    … …  
    1717My **workaround** was to edit my list of ports to restore. I looked at the ports involved in the cycle. One was clearly little used, I didn't even recognise it. I removed that from my list of ports. I also had hundreds of entries for old versions of ports which were no longer active; I removed all of them also. With this change, `restore_ports.tcl` was able to avoid the dependency cycle, and the restore is underway.
    1818
    19 This problem is similar to https://trac.macports.org/ticket/49210 'restore_ports.tcl script on fails on El Capitan with the error "infinite loop"'. That ticket did not come up with a clear solution to their problem, and it is closed and four years old. I think it's better to open a new ticket than to add this commentary on to that ticket. Hopefully others with this problem will find the workaround helpful, even before the underlying bug gets fixed.
     19This problem is similar to #49210 'restore_ports.tcl script on fails on El Capitan with the error "infinite loop"'. That ticket did not come up with a clear solution to their problem, and it is closed and four years old. I think it's better to open a new ticket than to add this commentary on to that ticket. Hopefully others with this problem will find the workaround helpful, even before the underlying bug gets fixed.
    2020
    2121**Versions**: \\