[MacPorts] #69873: Potential signing issue with libiconv

[MacPorts]

#69873: Potential signing issue with libiconv
----------------------+--------------------
  Reporter:  Gandoon  |      Owner:  (none)
      Type:  defect   |     Status:  new
  Priority:  Normal   |  Milestone:
 Component:  ports    |    Version:
Resolution:           |   Keywords:
      Port:           |
----------------------+--------------------

Comment (by Gandoon):

 Replying to [comment:1 ryandesign]:
 > There's nothing funny going on with libiconv. The files it installs are
 unsigned, just like almost all other ports.

 Then I am at a loss with respect to the `transmission @4.0.5_0` issue. It
 builds but refuses to run according to the above. I am beginning to think
 that it is a lost cause trying to get the MacPorts build to run on this
 system. The prior version, `@3.00_1` used to not complain about anything
 and run just fine but now it segfaults on start.

 I did a `port -v -n upgrade --force libiconv` ''and'' a `port -v -n
 upgrade --force transmission`, in that order (I have build from source set
 as a default) and the results are the same. I further did a `port -v
 uninstall libiconv && port -v clean --all libiconv` and subsequent rebuild
 – Transmission still suffers the same dyld crash.

 I can't see what else I could do easily. As I mentioned, I built
 Transmission, the originating issue, from the GitHub repository and it
 works just fine. Maybe I should just give up on the Transmission port?

-- 
Ticket URL: <https://trac.macports.org/ticket/69873#comment:3>
MacPorts <https://www.macports.org/>
Ports system for macOS