[MacPorts] #53584: failed to activate ghostscript

[MacPorts]

#53584: failed to activate ghostscript
--------------------------+--------------------
  Reporter:  mrkapqa      |      Owner:  (none)
      Type:  defect       |     Status:  new
  Priority:  Normal       |  Milestone:
 Component:  ports        |    Version:  2.4.0
Resolution:               |   Keywords:
      Port:  ghostscript  |
--------------------------+--------------------

Comment (by ryandesign):

 Replying to [comment:3 victorp-sg]:
 > the excerpt from the relevant section of the log file is shown above
 with, what looks like, the reason of the failure.

 Unfortunately no; your log provides no additional information beyond what
 we already know: that fc-cache is being killed for some reason.

 > {{{
 > :debug:activate could not read "/opt/local/share/man/man1/wftopfa.1.gz":
 no such file or directory
 > }}}

 This is not relevant or accurate. MacPorts uses an internal global
 variable to store the last error message. Some types of errors occur
 normally while MacPorts does its thing and it ignores them and moves on to
 other tasks. In this case, that other task had an error but it did not
 store the new error message in the global variable, so that when the value
 of the variable was printed out, you saw this older irrelevant error
 instead of the correct one. Unfortunately MacPorts base code is complex
 and I do not know where in the code we have neglected to fill the global
 variable with the correct error message.

 > {{{
 > Warning: reinplace s|#!/usr/bin/perl|#!/opt/local/bin/perl| didn't
 change anything in
 /opt/local/var/macports/build/_opt_local_var_macports_sources_rsync.macports.org_release_tarballs_ports_print_ghostscript/ghostscript/work/ghostscript-9.19/freetype_local/src/tools/afblue.pl
 > }}}

 This is not relevant to this issue.

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