[MacPorts] #66918: MacOSX10.7.sdk and MacOSX10.9.sdk: Marked as broken by rev-upgrade (was: MacOSX10.7.sdk and MacOSX10.9.sdk & fail to install on 10.13 HighSierra)

MacPorts noreply at macports.org
Tue Mar 7 21:44:54 UTC 2023

#66918: MacOSX10.7.sdk and MacOSX10.9.sdk: Marked as broken by rev-upgrade
  Reporter:  rmottola    |      Owner:  ryandesign
      Type:  defect      |     Status:  assigned
  Priority:  Normal      |  Milestone:
 Component:  ports       |    Version:
Resolution:              |   Keywords:  highsierra
      Port:  MacOSX.sdk  |
Changes (by ryandesign):

 * keywords:  macosx sdk highsierra 10.7 => highsierra
 * port:  MacOSX10.9.sdk => MacOSX.sdk


 So they don't fail to install; they're just marked as broken by rev-

 I assume that if you use these SDK ports (i.e. specifying their paths with
 `-isysroot` and `-syslibroot` when building something) then the brokenness
 reported by rev-upgrade will not exist.

 Taking as an example the first problem in your log:

 Could not open
 Error opening or reading file (referenced from
 DEBUG: Marking
 as broken

 Yes, ContactsData.framework does not exist in
 /System/Library/PrivateFrameworks on High Sierra but it did exist there on
 Mavericks and should exist in

 My inclination would be to ignore the rev-upgrade message or disable the
 use of rev-upgrade. (I have it disabled on my system which is why I didn't
 notice this issue.) Maybe there should be a way for a port to tell rev-
 upgrade not to scan it.

Ticket URL: <https://trac.macports.org/ticket/66918#comment:1>
MacPorts <https://www.macports.org/>
Ports system for macOS

More information about the macports-tickets mailing list