[MacPorts] #68869: Fetching archive for gperf fails

MacPorts noreply at macports.org
Mon Dec 11 23:28:34 UTC 2023


#68869: Fetching archive for gperf fails
--------------------------+--------------------
  Reporter:  ThoAppelsin  |      Owner:  (none)
      Type:  defect       |     Status:  new
  Priority:  Normal       |  Milestone:
 Component:  ports        |    Version:
Resolution:               |   Keywords:
      Port:  gperf        |
--------------------------+--------------------

Comment (by ryandesign):

 Replying to [comment:3 ThoAppelsin]:
 > But (and I believe that it's still on topic) the messages presented by
 MacPorts is definitely not giving me this information, making such
 inquiries a necessary/sensible next step.

 I agree that the output MacPorts display is less clear than it could be.
 We constantly get bug reports from people misreporting the reason for a
 failed installation as a missing binary archive, when binary archives are
 meant to be merely a convenience, and their absence is not considered a
 bug. I'm sure I have pointed this out numerous times and there may be a
 ticket about it, I don't remember. It could be as simple, as you say, as
 one summary line after failing to fetch archives. I don't think it needs
 to say how many hosts were attempted or failed since that's self-evident
 from the preceding lines, especially if we add some "not found" indication
 to each line as you suggested. I suggest the summary might say something
 like either "Pre-built archive not found; building from source" or "Error:
 Pre-built archive not found; not building from source because binary-only
 mode was requested".

 > 2. to continue attempting the next host after being unable to resolve
 one, giving only a warning instead of a full-blown error.

 MacPorts did continue to try all archive servers. It only presented an
 error after the last one, rather than trying a build from source, because
 you asked for it to do so by using the `-b` flag.

 > Slightly off-topic: Is `ema.uk.packages.macports.org` down for good or
 is there only a temporary problem?

 #68576

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


More information about the macports-tickets mailing list