Rust update

[MarcusCalhoun-Lopez]

Description

Type(s)

• bugfix
• enhancement
• security fix

Tested on

macOS x.y
Xcode x.y / Command Line Tools x.y.z

Verification

Have you

• followed our Commit Message Guidelines?
• squashed and minimized your commits?
• checked that there aren't other open pull requests for the same change?
• referenced existing tickets on Trac with full URL in commit message?
• checked your Portfile with port lint --nitpick?
• tried existing tests with sudo port test?
• tried a full install with sudo port -vst install?
• tested basic functionality of all binary files?
• checked that the Portfile's most important variants haven't been broken?

[MarcusCalhoun-Lopez]

This PR should probably not be merged until macports/macports-legacy-support#86 is resolved or else Ticket 68015 will continue to be an issue.

[pmetzger]

Apparently macports/macports-legacy-support#86 is merged, so I will merge this.

[MarcusCalhoun-Lopez]

Apparently macports/macports-legacy-support#86 is merged, so I will merge this.

@pmetzger, while macports/macports-legacy-support#86 has been merged upstream, it has not made it into the MacPorts version.
The upstream maintainers wanted to "allow a bit of time" before doing so.
It is not a big deal, but the new version of Rust from this PR will still be broken on 10.9 and 10.10.

I should have marked this PR as a draft to make it clear this PR was still on hold.

[pmetzger]

@MarcusCalhoun-Lopez Sorry. What should be done now, then?

[MarcusCalhoun-Lopez]

@MarcusCalhoun-Lopez Sorry. What should be done now, then?

I do not think it is a major problem.
Once we get the legacy-support situation worked out, it may be as simple as resubmitting the jobs to the 10.9 and 10.10 buildbots.