[MacPorts] #60110: 10.8 buildbot worker is down

[MacPorts]

#60110: 10.8 buildbot worker is down
-----------------------------+---------------------
  Reporter:  ryandesign      |      Owner:  admin@…
      Type:  defect          |     Status:  new
  Priority:  Normal          |  Milestone:
 Component:  server/hosting  |    Version:
Resolution:                  |   Keywords:
      Port:                  |
-----------------------------+---------------------

Comment (by ryandesign):

 I have tried to boot to the 10.8 installer and restore from Time Machine
 backup. It says it can't because the backup was made on a different Mac
 model. This is a lie; I have created the new virtual machine the same way
 as I created the other VMs before.

 I tried to reinstall 10.8 which failed with an error message which
 suggested that the installer pkg certificate was invalid. Rather than
 wasting time downloading a fresh copy of the installer, I backdated the
 clock by a year, which allowed the installation to proceed. I restored
 from Time Machine backup, but apparently not everything gets backed up.
 Xcode got backed up, but the Xcode "additional components" didn't, because
 Xcode asked to install them when I opened it. Installing additional
 components failed. The dialog box told me to check install.log, but there
 was nothing there. system.log however pointed to the fact that it was
 accessing https://developer.apple.com but could not because the SSL
 certificate was issued by an unknown issuer. I opened that URL in Safari
 and told it always to trust the certificate. Then I retried installing
 additional components. This time it failed because it tried to access
 https://devimages.apple.com.edgekey.net but could not because it could not
 establish a secure connection. This suggests the server is configured to
 require newer TLS protocols than the networking libraries on Mountain Lion
 are capable of accommodating. I can't think of a good way of getting past
 this. I should report this to Apple but don't have high hopes that they
 will choose to resolve it by reenabling obsolete security protocols on
 their edge servers, but if they don't, it means that nobody can install a
 working Xcode on Mountain Lion anymore.

 An alternative could be that I make a clone of the 10.8-legacy VM we
 decommissioned some months ago, excluding the contents of /opt/local and
 maybe deleting and recreating the buildworker directory. Or I could just
 copy the additional components from that VM, if I knew where they get
 installed.

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