| 4 | | |
| 5 | | == selfupdate fails and/or `port` command is killed by OS after using selfupdate == #selfupdate |
| 6 | | |
| 7 | | If selfupdate fails: |
| 8 | | |
| 9 | | {{{ |
| 10 | | $ sudo port selfupdate |
| 11 | | ---> Checking for newer releases of MacPorts |
| 12 | | MacPorts base version 2.11.0 installed, |
| 13 | | MacPorts base version 2.11.1 available. |
| 14 | | ---> MacPorts base is outdated, installing new version 2.11.1 |
| 15 | | ---> Attempting to fetch MacPorts 2.11.1 source code from https://github.com/macports/macports-base/releases/download/v2.11.1/MacPorts-2.11.1.tar.bz2 |
| 16 | | ---> Extracting MacPorts 2.11.1 |
| 17 | | ---> Installing new MacPorts release in /opt/local as root:wheel; permissions 0755 |
| 18 | | Error: Error installing new MacPorts base: command execution failed |
| 19 | | }}} |
| 20 | | |
| 21 | | and/or if the `port` command then no longer works and is killed by the OS: |
| 22 | | |
| 23 | | {{{ |
| 24 | | $ port |
| 25 | | Killed |
| 26 | | }}} |
| 27 | | |
| 28 | | Try running: |
| 29 | | |
| 30 | | {{{ |
| 31 | | cp -c /opt/local/libexec/macports/bin/tclsh8.6 /tmp |
| 32 | | }}} |
| 33 | | |
| 34 | | Then try using the `port` command again. |
| 35 | | |
| 36 | | If that doesn't work, try: |
| 37 | | |
| 38 | | {{{ |
| 39 | | sudo /usr/sbin/purge |
| 40 | | }}} |
| 41 | | |
| 42 | | Report your findings in #72689. Please let us know what MacPorts versions you were upgrading from and to. Also let us know what versions of macOS, Xcode, Xcode command line tools, and clang you have by showing the output of this command: |
| 43 | | |
| 44 | | {{{ |
| 45 | | sw_vers; xcodebuild -version; pkgutil --pkg-info=com.apple.pkg.CLTools_Executables; /usr/bin/clang --version |
| 46 | | }}} |
| | 239 | == selfupdate fails and/or `port` command is killed by OS after using selfupdate == #selfupdate |
| | 240 | |
| | 241 | MacPorts 2.11.2 and later have a workaround for this issue. |
| | 242 | |
| | 243 | If selfupdate fails: |
| | 244 | |
| | 245 | {{{ |
| | 246 | $ sudo port selfupdate |
| | 247 | ---> Checking for newer releases of MacPorts |
| | 248 | MacPorts base version 2.11.0 installed, |
| | 249 | MacPorts base version 2.11.1 available. |
| | 250 | ---> MacPorts base is outdated, installing new version 2.11.1 |
| | 251 | ---> Attempting to fetch MacPorts 2.11.1 source code from https://github.com/macports/macports-base/releases/download/v2.11.1/MacPorts-2.11.1.tar.bz2 |
| | 252 | ---> Extracting MacPorts 2.11.1 |
| | 253 | ---> Installing new MacPorts release in /opt/local as root:wheel; permissions 0755 |
| | 254 | Error: Error installing new MacPorts base: command execution failed |
| | 255 | }}} |
| | 256 | |
| | 257 | and/or if the `port` command then no longer works and is killed by the OS: |
| | 258 | |
| | 259 | {{{ |
| | 260 | $ port |
| | 261 | Killed |
| | 262 | }}} |
| | 263 | |
| | 264 | You may be affected by an apparent bug in the macOS filesystem cache. Completely flushing the cache is one way to make the symptom go away: |
| | 265 | |
| | 266 | {{{ |
| | 267 | sudo /usr/sbin/purge |
| | 268 | }}} |
| | 269 | |
| | 270 | Ticket: #72689. |
| | 271 | |
| | 272 | |