[MacPorts] #67336: BSD tar can create corrupted archives on Catalina, Big Sur, Monterey, Ventura
MacPorts
noreply at macports.org
Thu May 18 11:23:45 UTC 2023
#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 ryandesign):
The command that MacPorts uses to extract an archive is determined by
base. It was never intended for ports to override it, and I don't think
it's possible for them to do so.
Yes, working around OS bugs sometimes requires hacks.
I wasn't sure how to test for this myself, but I understand now that I can
just go to my fork of macports-ports, make a branch, edit the pari
portfile to include the testing code, commit it, and GitHub Actions
automatically runs builds for me.
Armed with this knowledge, I did some tests of my own. I saw the problem
on macOS 12 and 13 but not on macOS 11.
I tested whether using GNU tar's `--sparse` flag caused it to experience
the bug too. In my test runs, it did. That confirms for me that it is an
OS filesystem bug, not a bug in libarchive.
I tested whether running `purge` before archiving fixed the problem. In my
test runs, it did.
I tested whether using `sleep 10` before archiving fixed the problem. In
my test runs, it didn't.
--
Ticket URL: <https://trac.macports.org/ticket/67336#comment:28>
MacPorts <https://www.macports.org/>
Ports system for macOS
More information about the macports-tickets
mailing list