[MacPorts] #69873: transmission: Potential signing issue with libiconv
MacPorts
noreply at macports.org
Wed May 1 13:07:06 UTC 2024
#69873: transmission: Potential signing issue with libiconv
---------------------------+----------------------------
Reporter: Gandoon | Owner: kurthindenburg
Type: defect | Status: assigned
Priority: Normal | Milestone:
Component: ports | Version:
Resolution: | Keywords:
Port: transmission |
---------------------------+----------------------------
Comment (by Gandoon):
Replying to [comment:14 kencu]:
> Replying to [comment:13 ryandesign]:
>
> > Replying to [comment:12 kencu]:
> > > Turns out it gives this error if you don't have a full Xcode
installation.
> >
> > I do have a full Xcode installation.
>
> It also gives this same error if you don't have one, though.
It was interesting to see the recent input. Inspired by it, I tried
setting:
{{{
# Hardened Runtime on 10.14 is not compatible with AdHoc signing
if {${os.major} == 19} {
xcode.build.settings-append \
ENABLE_HARDENED_RUNTIME=NO
}
}}}
in the portfile to make it catch my MacOS 10.15. This threw the same "This
will fail" message before proceeding to building. After telling it to go
ahead anyway, it did build as expected and the application starts and
works as intended. The only thing is that one has to explicitly allow
network connections when starting the application.
So as for my issue, I consider this matter solved. For the port in
general, I expect the easiest solution is to extend the portfile to
include something along the lines of:
{{{
if {${os.major} == 18 || ${os.major} == 19}
}}}
Thank you all.
--
Ticket URL: <https://trac.macports.org/ticket/69873#comment:15>
MacPorts <https://www.macports.org/>
Ports system for macOS
More information about the macports-tickets
mailing list