[MacPorts] #67336: BSD tar can create corrupted archives on Catalina, Big Sur, Monterey, Ventura

[MacPorts]

#67336: BSD tar can create corrupted archives on Catalina, Big Sur, Monterey,
Ventura
---------------------+-------------------------------------------------
  Reporter:  catap   |      Owner:  (none)
      Type:  defect  |     Status:  new
  Priority:  Normal  |  Milestone:
 Component:  base    |    Version:  2.8.1
Resolution:          |   Keywords:  catalina, bigsur, monterey, ventura
      Port:          |
---------------------+-------------------------------------------------

Comment (by catap):

 Replying to [comment:22 ryandesign]:
 > On Monterey x86_64, reverting your change to `portarchivetype`, I tried
 destrooting pari and, every second or two, scanning the work directory for
 sparse files with Sparsity. (I scanned frequently since we know the
 problem fixes itself within 10 seconds.) Aside from a log file in the
 configure phase, I didn't see any sparse files. I also tried reverting
 your change that blacklists Xcode clang; no change. I haven't seen the
 problem with the pari tbz2 archive on my system. If you consistently see
 the problem on your system, you could try scanning with Sparsity to see if
 we can confirm the theory that the problem occurs when there are sparse
 files.

 Unfortunately I'm able to reproduce it via Github CI. I not able to
 reproduce it at any of my system. But the same port had the same issue on
 the same macOS 13 on build bots.

 I feel that this port / ability of reproduce the issue is good way for us
 to track it and fix it. Frankly speaking I don't like idea to flush
 caches. I feel that it covers the issue.

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