Changes between Version 161 and Version 162 of ProblemHotlist

Timestamp:

Nov 8, 2022, 5:55:53 AM (18 months ago)

Author:

jmroot (Joshua Root)

Comment:

retire "no destroot found"

ProblemHotlist

@@ -65 +65 @@
 Note you might have an older version of the `xcode-select` tool in case you installed Xcode 4.2 after installing the Mac OS X 10.7.3 update. If the command `xcode-select -version` returns `version 2003`, this is from Xcode 4.2 and we recommend to install the update once again with the [http://support.apple.com/kb/DL1484 Mac OS X 10.7.3 combo updater]. The current `xcode-select` version that comes with Mac OS X 10.7.3 identifies itself as `version 2307`.
 
-
-== Port installation fails with "no destroot found" == #nodestrootfound
-
-Installing a port fails with the error message "no destroot found", for example:
-
-{{{
-:error:install org.macports.install for port libpixman returned: no destroot found at: /opt/local/var/macports/build/_opt_local_var_macports_sources_rsync.macports.org_release_tarballs_ports_graphics_libpixman/libpixman/work/destroot
-}}}
-
-This happens when you have existing files that conflict with the ones that a port wants to install, so the port fails to activate, and you then uninstall the port and try to install it again without cleaning it first. The workaround is to clean the affected port and try again. For example the above error shows libpixman is the port that failed, so to clean it you would run:
-
-{{{
-sudo port clean libpixman
-}}}
-
-Ticket tracking this issue: #55445
-
 == install_name_tool or strip reports "malformed object (unknown load command)" == #malformed-object
 
@@ -231 +214 @@
 The following problems are now solved, no longer apply to current MacPorts or should no longer be happening due to other circumstances. They are kept here for future reference and to avoid breaking existing links.
 }}}
+
+== Port installation fails with "no destroot found" == #nodestrootfound
+
+The most common reason for seeing this issue should be fixed as of MacPorts 2.8.0, but it would still be possible to get into the problematic state by more esoteric means like manually deleting the `destroot` directory in a port's work directory.
+
+Installing a port fails with the error message "no destroot found", for example:
+
+{{{
+:error:install org.macports.install for port libpixman returned: no destroot found at: /opt/local/var/macports/build/_opt_local_var_macports_sources_rsync.macports.org_release_tarballs_ports_graphics_libpixman/libpixman/work/destroot
+}}}
+
+This happens when you have existing files that conflict with the ones that a port wants to install, so the port fails to activate, and you then uninstall the port and try to install it again without cleaning it first. The workaround is to clean the affected port and try again. For example the above error shows libpixman is the port that failed, so to clean it you would run:
+
+{{{
+sudo port clean libpixman
+}}}
+
+Ticket tracking this issue: #55445
 
 == port fails with: Image error: /opt/local/bin/a2p... == #perl5-image-error