[MacPorts] #63531: clang-7.0 @7.1.0_1 fails archivefetch

MacPorts noreply at macports.org
Thu Sep 23 20:47:09 UTC 2021


#63531: clang-7.0 @7.1.0_1 fails archivefetch
------------------------+--------------------------
  Reporter:  fhgwright  |      Owner:  (none)
      Type:  defect     |     Status:  new
  Priority:  Normal     |  Milestone:
 Component:  base       |    Version:  2.7.1
Resolution:             |   Keywords:  archivefetch
      Port:  clang-7.0  |
------------------------+--------------------------

Comment (by fhgwright):

 Replying to [comment:1 jmroot]:
 > If it's all ports and not just this one, then most likely your
 configuration is not compatible with the build server's. See the second-
 last bullet point in wiki:FAQ#fromsource.

 No, it's not that.

 > If clang-7.0 is in a separate ports tree, then it could be the same
 situation as #59463 (which is really a feature, not a bug). If you know
 it's safe to use the official archive sites with a custom ports tree, you
 can copy `_resources/port1.0/fetch/archive_sites.tcl` from the official
 ports tree to the custom one, as Rainer mentioned in the other ticket.

 Bingo!  But it had never occurred to me to create modified ports that
 aren't consistent with the published ones.  I.e.:

 1) If I've changed the installed content, I revbump it.  Archives matching
 the version/revision won't exist.

 2) If I've only fixed a broken build, I don't revbump it, but the archive
 won't exist since the buildbots couldn't build it either.

 In short, this behavior definitely violates the principle of least
 surprise.

 > Or it could be something as simple as clang-7.0 being installed with
 variants other than the default ones.

 Nope.  As I said in the original description, that case has a different
 symptom, where it makes a few attempts to fetch an archive with the
 requested variants before falling back to building from source.  Here, in
 the default case, it simply pretends not to know about installing from
 binaries, and with `-b` it gives an error message that doesn't explain the
 real issue.

 Hence, the absence of suitably informative messages is certainly a bug,
 even if the underlying behavior isn't.

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


More information about the macports-tickets mailing list