Re: [MacPorts] ProblemHotlist modified

2018-04-06 Thread Ryan Schmidt

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: 
>>> 
>>> 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.




Re: [MacPorts] ProblemHotlist modified

2018-04-06 Thread Rainer Müller
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: 
>> 
>> 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.

Rainer


Re: [MacPorts] ProblemHotlist modified

2018-04-05 Thread Ryan Schmidt

On Apr 5, 2018, at 20:54, MacPorts Wiki wrote:

> Page "ProblemHotlist" was changed by raimue
> Diff URL: 
> 
> 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.




Re: [MacPorts] ProblemHotlist modified

2017-11-06 Thread Rainer Müller
On 2017-11-05 21:28, Ryan Schmidt wrote:
> 
> On Nov 5, 2017, at 14:10, MacPorts wrote:
> 
>> Page "ProblemHotlist" was changed by grimreaper
>> Diff URL: 
>> 
>> Revision 136
>> Comment: xcode 7.2 is old and people upgraded
> 
> Well, Xcode 7.2.1 is the last version of Xcode available for OS X Yosemite 
> 10.10; those users cannot upgrade to a fixed version.

In this case the entry could be kept on the YosemiteProblems wiki page
only? There is already a note, although I am not sure if this addresses
the same problem:

https://trac.macports.org/wiki/YosemiteProblems#iphonesimulator

Rainer


Re: [MacPorts] ProblemHotlist modified

2017-11-05 Thread Ryan Schmidt

On Nov 5, 2017, at 14:10, MacPorts wrote:

> Page "ProblemHotlist" was changed by grimreaper
> Diff URL: 
> 
> Revision 136
> Comment: xcode 7.2 is old and people upgraded

Well, Xcode 7.2.1 is the last version of Xcode available for OS X Yosemite 
10.10; those users cannot upgrade to a fixed version.


> -== Build failures after upgrading to Xcode 7.2 == #xcode7.2
> -
> -After installing the update to Xcode 7.2, port installations or upgrades 
> using `xcodebuild` may fail with the following error due to an error in the 
> Xcode installation. This has been fixed by Apple in Xcode 7.3.
> -
> -{{{
> -Could not find service "com.apple.CoreSimulator.CoreSimulatorService" in 
> domain for uid: 502
> -2015-12-10 17:21:27.407 xcodebuild[7363:75765] launchctl print returned an 
> error code: 28928
> -2015-12-10 17:21:27.407 xcodebuild[7363:75765] Failed to locate a valid 
> instance of CoreSimulatorService in the bootstrap.  Adding it now.
> -Could not find service "com.apple.CoreSimulator.CoreSimulatorService" in 
> domain for uid: 502
> -2015-12-10 17:21:27.431 xcodebuild[7363:75765] launchctl print returned an 
> error code: 28928
> -2015-12-10 17:21:27.431 xcodebuild[7363:75765] *** Assertion failure in 
> -[SimServiceContext reloadServiceIfMovedOrAbortIfWeAreInvalid], 
> /BuildRoot/Library/Caches/com.apple.xbs/Sources/CoreSimulator/CoreSimulator-201.3/CoreSimulator/SimServiceContext.m:451
> -** INTERNAL ERROR: Uncaught exception **
> -Exception: Unable to lookup com.apple.CoreSimulator.CoreSimulatorService in 
> the bootstrap.  This can happen if running with a sandbox profile.  When 
> running with a sandbox profile, make sure that 
> com.apple.CoreSimulator.CoreSimulatorService.xpc is owned by root, not group 
> writable, and not world writable.  See .
> -}}}
> -
> -'''Please update to Xcode 7.3 to fix the permissions.'''
> -
> -As an alternative, the immediate workaround is to manually fix the 
> permissions of the path mentioned in the error message. User should be 
> 'root', group should be 'wheel', and write permissions only granted for the 
> owner:
> -
> -{{{
> -sudo chmod -R g-w $(xcode-select 
> -p)/Library/PrivateFrameworks/CoreSimulator.framework/Versions/A/XPCServices/com.apple.CoreSimulator.CoreSimulatorService.xpc
> -sudo chown -R root:wheel $(xcode-select 
> -p)/Library/PrivateFrameworks/CoreSimulator.framework/Versions/A/XPCServices/com.apple.CoreSimulator.CoreSimulatorService.xpc
> -}}}