[MacPorts] #68658: bsdtar crashes with dyld missing symbol when upgrading a dependent port such as libxml2
MacPorts
noreply at macports.org
Mon Jun 30 07:32:31 UTC 2025
#68658: bsdtar crashes with dyld missing symbol when upgrading a dependent port
such as libxml2
-------------------------+----------------------
Reporter: PerMildner | Owner: (none)
Type: defect | Status: assigned
Priority: Normal | Milestone:
Component: base | Version:
Resolution: | Keywords:
Port: |
-------------------------+----------------------
Comment (by PerMildner):
About "we could first look at bsdtar's list of libraries": Since in my
scenario, the tested `bsdtar` (`/opt/local/bin/bsdtar`) crashes, adding a
test for its list of libraries would presumably conclude that the tested
`bsdtar` is unusable. This seems undesirable, since, in the common case
where `/usr/bin/bsdtar` is new enough to support HFS compression, this
sounds like MacPorts would needlessly decide that HFS compression is
unsupported. If MacPorts instead tested `/usr/bin/bsdtar`, which I assume
would never crash, it would discover that it _does_ support HFS
compression (if `/usr/bin/bsdtar` does not support HFS compression
MacPorts could either fall back to testing other locations, like
`/opt/local/bin/bsdtar`, or just fall back to a somewhat less optimal
format on those old platforms
PS. It is not clear to me whether "HFS+ compression" is relevant on
modern, i.e. APFS, file systems but #60230 indicates that perhaps it is
(user had problem with that option on an APFS system, running as non-
root).
--
Ticket URL: <https://trac.macports.org/ticket/68658#comment:37>
MacPorts <https://www.macports.org/>
Ports system for macOS
More information about the macports-tickets
mailing list