[MacPorts] #67336: BSD tar can create corrupted archives on Catalina, Big Sur, Monterey, Ventura
MacPorts
noreply at macports.org
Fri Oct 4 23:05:16 UTC 2024
#67336: BSD tar can create corrupted archives on Catalina, Big Sur, Monterey,
Ventura
-------------------------+-------------------------------------------------
Reporter: catap | Owner: (none)
Type: defect | Status: new
Priority: High | Milestone:
Component: base | Version: 2.8.1
Resolution: | Keywords: catalina, bigsur, monterey,
Port: | ventura, sonoma, sequoia
-------------------------+-------------------------------------------------
Comment (by jmroot):
Replying to [comment:39 ryandesign]:
> I'm not aware of a simplified test case. Per above comments, Kirill
found that the pari port always exhibits the problem on GitHub Actions, so
we did test builds in which we added code to the `pre-install` block, for
example tarring the destroot with BSD tar and GNU tar with various options
before and after running `purge` and checking the size of the resulting
archives as a way to measure whether the problem had occurred. Additional
tests could be run that way.
The macports-ports CI is not terribly suited to testing modifications to
base. Ideally we'd want something that can be added to base's test suite.
> `--no-read-sparse` is exactly the option added to `tar` in libarchive
3.6.0 that I was talking about, which is not available in any version of
macOS since it still uses an older version of libarchive.
Yes. We could use it if the libarchive port is installed and on future OS
versions.
--
Ticket URL: <https://trac.macports.org/ticket/67336#comment:40>
MacPorts <https://www.macports.org/>
Ports system for macOS
More information about the macports-tickets
mailing list