[MacPorts] #66511: Issue installing or upgrading ghostscript port

[MacPorts]

#66511: Issue installing or upgrading ghostscript port
-----------------------+--------------------
  Reporter:  Hardies1  |      Owner:  (none)
      Type:  defect    |     Status:  new
  Priority:  Normal    |  Milestone:
 Component:  ports     |    Version:  2.8.0
Resolution:            |   Keywords:
      Port:            |
-----------------------+--------------------

Comment (by ryandesign):

 In future please paste the text of error messages, not photos of them.
 Photos take up tons of space and are not searchable.

 The photo says:

 {{{
 $ sudo port install ghostscript
 Password:
 --->  Computing dependencies for ghostscript
 --->  Fetching archive for ghostscript
 --->  Attempting to fetch ghostscript-9.56.1_0+x11.darwin_19.x86_64.tbz2
 from
 https://ywg.ca.packages.macports.org/mirror/macports/packages/ghostscript
 --->  Attempting to fetch ghostscript-9.56.1_0+x11.darwin_19.x86_64.tbz2
 from https://packages.macports.org/ghostscript
 --->  Attempting to fetch ghostscript-9.56.1_0+x11.darwin_19.x86_64.tbz2
 from http://mirror.fcix.net/macports/packages/ghostscript
 --->  Fetching distfiles for ghostscript
 }}}

 This problem sounds like #60509 (which was experienced by me on 32-bit Mac
 OS X 10.6 and by another user on Mac OS X 10.7, and which we attempted to
 work around in MacPorts 2.7.0 by reducing the number of processes that get
 spawned simultaneously when determining which servers are closest to you)
 and #61683 (which was experienced by many users of macOS 11.0, 11.1, and
 11.2, and which was fixed by Apple in macOS 11.3). There are some details
 in those tickets about steps you can take to limit the number of processes
 even further, to see if that helps, and also mentions of some third-party
 software that may exacerbate the problem (which you could try disabling).

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