You beat me to the punch, but I was near to sending a similar note.  As far as the Tiger buildbots, I think it's probably time to just shut them down.

Even if I fix the more recent git problem, I had already been looking at an OpenSSL 1.1.0 build issue, for which I had gotten a static build to work under 10.4, but not shared.  The installer builds had already been failing for the 3.7 and 3.x branches, and the regular workers  were not performing SSL testing for those branches.

I think we're in sync that the value proposition of 10.4 has been marginal for a while now; while it has surprisingly helped identify some real issues even recently, I think the effort to remain operational at this point is not worth the benefits.

-- David

On Tue, Feb 27, 2018 at 11:13 AM, Ned Deily <nad@python.org> wrote:
As of several days ago, github.com finally removed support for obsolete crypto standards:

https://github.com/blog/2507-weak-cryptographic-standards-removed

That appears to be the root cause of git failures on the macOS 10.4 Tiger buildbots.  David, you have been doing a great service over many years in setting up and keeping those buildbots running: thank you!  I know they have been a bit of a pain to other core-developers because the version of macOS is so old and its Posix compliance is "challenging" (e.g. Apple made big improvement in 10.5 and subsequent releases).  My take has been that, as long as someone is willing to keep the buildbots running and the work to fix failing tests isn't too much, continuing to test with such an older and stable system is a good thing.  But I dunno, perhaps it is time to retire 10.4 testing?  Another issue is that the dmg buildbots are fine for testing the installer build - assuming the third-party libs also still build on 10.4 - but the dmgs produced are no longer installable on current macOS systems since the macOS installer app dropped support for the old bundle installer format a few release ago and building the newer flat installer package format is not supported on 10.4 (AFAIK).

So I guess there are a couple of separate issues here:

1. David, if you are willing and able to put a newer version of git that links with a newer version of OpenSSL (or some such) so that github pulls work again, that would be swell but not mandatory.

2. We should look at moving the installer builds to a newer version of macOS.  I have a machine or two here that I have been intending to set up with some VMs for buildbots that could be used.  But I may not have time to do that for a bit.

3. I need to document the flat package build process; currently, it is a magic transformation and doesn't really fit well into the current build-installer.  I will track that along with Issue24502.

--
  Ned Deily
  nad@python.org -- []