5 | | With that, I've solved the problem now, although i'm not sure what step fixed it. I removed {/opt/local/var/macports/sources/rsync.macports.org/macports/release/tarballs/ports/python/py-pytorch}, included only my local repo in {sources.conf}, ran {selfupdate}, and then {port info py-pytorch} yielded {Error: Port py-pytorch not found} (but it still could find other ports). Now I checked out local repo {py-pytorch/Portfile} and modified only the description and revision, did {selfupdate}, and now {port dir py37-pytorch} yields |
6 | | {/Users/webb/src/macports-ports/python/py-pytorch} as desired. It seems plausible that I had an error in my modified Portfile and {selfupdate} was falling back to the {rsync.macports.org} version. |
| 5 | With that, I've solved the problem now, although i'm not sure what step fixed it. I removed `/opt/local/var/macports/sources/rsync.macports.org/macports/release/tarballs/ports/python/py-pytorch`, included only my local repo in `sources.conf`, ran `selfupdate`, and then `port info py-pytorch` yielded `Error: Port py-pytorch not found` (but it still could find other ports). Now I checked out local repo `py-pytorch/Portfile` and modified only the description and revision, did `selfupdate`, and now `port dir py37-pytorch` yields |
| 6 | `/Users/webb/src/macports-ports/python/py-pytorch` as desired. It seems plausible that I had an error in my modified Portfile and `selfupdate` was falling back to the `rsync.macports.org` version. |