[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 fhgwright):

 Replying to [comment:4 berg-michael]:
 > I am not able to prove this definitively as I don't have a recent macOS
 machine to test.
 >
 > However, I think this might be caused by recent versions of bsdtar which
 default to the pax archive format. I see rumblings about these changes
 (https://www.undeadly.org/cgi?action=article;sid=20240417053301,
 https://bugs.python.org/issue36268) in other environments and suspect it
 happened on macOS as well.
 [...]

 I don't think that's the issue, for a couple of reasons:

 1. AFAIK the extract phase normally unpacks entire tarballs, not
 individual files.

 2. The error message (excerpted above) doesn't sound like it relates to
 this issue.

 > It should be possible to do a sweep of the existing tarballs and re-
 tarball them in the older format. This would not require rebuilding, just
 repackaging. The scope of the sweep probably could be narrowed by not
 considering files with a creation date before the default was changed to
 Pax, if such a date can be determined.

 Replying to [comment:6 ryandesign]:
 > Before we develop a script to identify and repack all affected archives,
 MacPorts base should be changed to ensure that new archives are made in
 the old format even on new versions of macOS. That's assuming there is a
 way to do so.

 Indeed.

 But something that could be done right away (as I suggested above) and
 hasn't been (unless it was done without referencing this ticket) is to
 make `always` the default for `build_from_source` on 10.4.  Then, if
 there's no better fix before the 2.10.2 release, it will at least have the
 workaround.

 On a somewhat related note, it doesn't appear that the buildbot framework
 has been updated to optimally handle the `darwin any` case.  Such ports
 still get unnecessarily built for all platforms.  I don't know what
 determines which result winds up on the archive servers.  In the most
 simple-minded treatment, it would probably be all of them, with the last
 one "winning".

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