On Apr 6, 2018, at 07:15, Rainer Müller wrote:

> On 2018-04-06 07:54, Ryan Schmidt wrote:
> 
>> On Apr 5, 2018, at 20:54, MacPorts Wiki wrote:
>> 
>>> Page "ProblemHotlist" was changed by raimue
>>> Diff URL: 
>>> <https://trac.macports.org/wiki/ProblemHotlist?action=diff&version=138>
>>> Revision 138
>>> Comment: No longer hot, have not even heard of this problem
>>> Changes:
>>> -------8<------8<------8<------8<------8<------8<------8<------8<--------
>>> Index: ProblemHotlist
>>> =========================================================================
>>> --- ProblemHotlist (version: 137)
>>> +++ ProblemHotlist (version: 138)
>>> @@ -28,20 +28,6 @@
>>> 
>>> 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
>> 
>> It happens all the time:
>> 
>> https://trac.macports.org/query?summary=~no+destroot+found
>> 
>> As far as I know, we've changed nothing in MacPorts base to fix it.
> 
> Okay... I restored this section.


I believe what happens is that MacPorts gets far enough along the path of 
deciding that it wants to use a binary that it marks all the phases up to and 
including destroot as completed, but then for some reason can't actually 
install the archive it downloaded. So then it's left in a state where the 
statefile says the destroot phase was completed, but there's no destroot 
directory.


Reply via email to