[MacPorts] #70890: openjdk21 @21.0.3_1+release+server : build fails on Sonoma 14.7 with "xattr: [Errno 13] Permission" denied error
MacPorts
noreply at macports.org
Sun Nov 17 02:24:19 UTC 2024
#70890: openjdk21 @21.0.3_1+release+server : build fails on Sonoma 14.7 with
"xattr: [Errno 13] Permission" denied error
-------------------------+----------------------
Reporter: lima-bravo | Owner: breun
Type: defect | Status: assigned
Priority: Normal | Milestone:
Component: ports | Version: 2.10.1
Resolution: | Keywords:
Port: openjdk21 |
-------------------------+----------------------
Comment (by jjstickel):
Replying to [comment:16 breun]:
> * Is the presence of the `com.apple.provenance` attribute the cause of
your build failing?
Yes.
> * Which `xattr` command is getting executed exactly and why does it
result in a '[Errno 13] Permission denied' error?
See https://trac.macports.org/ticket/70890#comment:2
> * Why can't you remove the attribute? (I believe this should be possible
when ` > System Preferences > Security & Privacy > Privacy > Full Disk
Access > Terminal` is on.)
See https://trac.macports.org/ticket/70890?replyto=16#comment:5 and the
next few comments. Terminal (for reporter) and iTerm2 (for me) have full
disk access.
> Maybe you could post on the MacPorts users mailinglist to find out
whether the presence of this attribute on those MacPorts folders is common
or not, and if so, if more users are experiencing issues due to this
attribute.
Sure, that could be a path forward. I've moved on at the moment and am not
using ports that require java.
I don't know the answers to your other questions about why this doesn't
happen on CI and why `com.apple.provenance` appears. I'll ask a question
of my own: is SIP enabled on the CI VM?
--
Ticket URL: <https://trac.macports.org/ticket/70890#comment:17>
MacPorts <https://www.macports.org/>
Ports system for macOS
More information about the macports-tickets
mailing list