[MacPorts] #67597: Unable to upgrade rust to 1.70.0_0

[MacPorts]

#67597: Unable to upgrade rust to 1.70.0_0
---------------------+---------------------------------
  Reporter:  RobK88  |      Owner:  MarcusCalhoun-Lopez
      Type:  defect  |     Status:  accepted
  Priority:  Normal  |  Milestone:
 Component:  ports   |    Version:  2.8.1
Resolution:          |   Keywords:
      Port:  rust    |
---------------------+---------------------------------

Comment (by MarcusCalhoun-Lopez):

 The buildbot is using
 [https://build.macports.org/builders/ports-10.13_x86_64-builder/builds/194864/steps
 /install-port/logs/stdio Xcode 9.4.1, CLT 9.4.1.0.1.1528165917], so Rust's
 `compiler.cxx_standard 2017` causes MacPorts to use clang-16, which, as
 you note, works fine.\\
 Both your setup and mine use Xcode 10.1, CLT 10.1.0.0.1.1539992718.\\
 Why my setup works and yours does not is a bit of a mystery.

 From what I can tell in your build log, Rust was not downloaded as a
 binary because it was, at that time, unavailable.
 {{{
 :info:archivefetch --->  rust-1.70.0_0.darwin_17.x86_64.tbz2 doesn't seem
 to exist in /opt/local/var/macports/incoming/verified
 :msg:archivefetch --->  Attempting to fetch
 rust-1.70.0_0.darwin_17.x86_64.tbz2 from http://packages.macports.org/rust
 :debug:archivefetch Fetching archive failed: The requested URL returned
 error: 404 Not Found
 :msg:archivefetch --->  Attempting to fetch
 rust-1.70.0_0.darwin_17.x86_64.tbz2 from
 http://ywg.ca.packages.macports.org/mirror/macports/packages/rust
 :debug:archivefetch Fetching archive failed: The requested URL returned
 error: 404 Not Found
 :msg:archivefetch --->  Attempting to fetch
 rust-1.70.0_0.darwin_17.x86_64.tbz2 from
 http://mirror.fcix.net/macports/packages/rust
 }}}
 Why it is still a problem is also a bit of a mystery (at least to me).\\
 MacPorts will not attempt to download a binary archive if the user has
 [https://github.com/macports/macports-
 base/blob/1c483e276e41f88c0ccdd4f4defb412ad9591e06/src/package1.0/portarchivefetch.tcl#L99
 changed certain settings], such as `delete_la_files`.\\
 But, as you again note, there is indication of that.

 Now that the buildbots have done their job, is there any hint in the build
 logs as to why the `archivefetch` is failing?

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