[MacPorts] #70622: automake @1.17_0 fails to install on 10.4

[MacPorts]

#70622: automake @1.17_0 fails to install on 10.4
------------------------+--------------------
  Reporter:  fhgwright  |      Owner:  (none)
      Type:  defect     |     Status:  new
  Priority:  Normal     |  Milestone:
 Component:  base       |    Version:  2.10.1
Resolution:             |   Keywords:
      Port:             |
------------------------+--------------------

Comment (by ryandesign):

 Replying to [comment:2 fhgwright]:
 > > I'm not aware of any change in how our binary archives are
 constructed. It may always have been the case that some or all archives
 created on newer macOS versions cannot be extracted on 10.4's version of
 tar, but that this has only become a problem since it has become possible
 for archives to be shared amongst OS versions (MacPorts 2.9.0?). I don't
 know which version of macOS created the automake 1.17 archive now on our
 servers.
 >
 > Given that this issue just appeared between last Saturday and a little
 over a week earlier, it's probably whatever the buildbots are currently
 using.

 The point is, we have over a dozen different machines running macOS
 versions between 10.6 and 14, and I don't know which one of those created
 the current automake 1.17 archive. It looks like most of the machines
 attempted the build, probably because there were no other builds running
 at the time that the commit came through, but I don't know which of them
 finished first or last, and I'm not sure whether the one that finishes
 first or the one that finishes last is the one that ends up on the server.

 > > You could try creating any tar archive on macOS 14 or other newer OS
 versions and then try extracting it on 10.4. If it fails the same way, and
 if you can then find some flags or options that can be used to create an
 archive on newer macOS that can be extracted on older macOS, base can be
 updated to use those flags or options.
 >
 > If there's a read-side fix, that would be better, since it would be
 compatible with the existing archives. Though a write-side fix might be
 accompanied by a sweep to update the existing relevant archives (perhaps
 just by repackaging the existing tarballs, rather than rebuilding them).

 Sure, if you find a way to fix the problem at extract time, let us know
 that. It's obviously not as simple as just making all ports depend on
 MacPorts gnutar for extraction since that would introduce a dependency
 cycle for MacPorts gnutar and everything it depends on.

 To rebuild archives with an OS version whose tar version is compatible
 with Tiger, we would first have to be able to identify which archives are
 affected. If you can provide a method to do that, let us know.

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