[MacPorts] #73711: py313-maturin @1.12.6_0: failed to parse manifest

[MacPorts]

#73711: py313-maturin @1.12.6_0: failed to parse manifest
-------------------------------------+-------------------------------------
  Reporter:  thetrial                |      Owner:  tobypeterson
      Type:  defect                  |     Status:  assigned
  Priority:  Normal                  |  Milestone:
 Component:  ports                   |    Version:  2.12.4
Resolution:                          |   Keywords:  legacy-os leopard
      Port:  py313-maturin,          |  snowleopard lion mountainlion
  py313-cryptography                 |  mavericks yosemite elcapitan sierra
-------------------------------------+-------------------------------------

Comment (by thetrial):

 I just got installed rust-1.98.0_0.darwin_16.x86_64. And then tried again.
 No.

 {{{
 :info:build error: failed to parse manifest at
 `/opt/local/var/macports/build/py313-maturin-
 8176722f/work/maturin-1.14.1/Cargo.toml`
 :info:build Caused by:
 :info:build   feature `edition2024` is required
 :info:build   The package requires the Cargo feature called `edition2024`,
 but that feature is not stabilized in this version of Cargo (1.78.0).
 :info:build   Consider adding `cargo-features = ["edition2024"]` to the
 top of Cargo.toml (above the [package] table) to tell Cargo you are opting
 in to use this unstable feature.
 :info:build   See https://doc.rust-
 lang.org/nightly/cargo/reference/unstable.html#edition-2024 for more
 information about the status of this feature.
 :info:build error: `cargo metadata --manifest-path Cargo.toml --format-
 version 1 --locked` failed with code 101
 :info:build -- Output captured from stdout:
 :info:build TIP pass --env-dir and --sdist-extract-dir to keep the build
 environment and sources, then see https://build.pypa.io/en/stable/how-
 to/troubleshooting.html#debug-a-failed-build for help debugging a failed
 build
 :info:build ERROR Backend subprocess exited when trying to invoke
 build_wheel
 :info:build Command failed:  cd "/opt/local/var/macports/build/py313
 -maturin-8176722f/work/maturin-1.14.1" &&
 /opt/local/Library/Frameworks/Python.framework/Versions/3.13/bin/python3.13
 -m build --no-isolation --wheel --outdir
 /opt/local/var/macports/build/py313-maturin-8176722f/work
 :info:build Exit code: 1
 :error:build Failed to build py313-maturin: command execution failed
 :debug:build Error code: CHILDSTATUS 11346 1
 }}}

 The main reason to stay with 10.12 is, that I use two machines that are in
 sync together. One of them could go further up to 10.15 out of the box.
 But the other one is already »hacked« with 10.12 as it would only go to
 10.11 out of the box. So even if I could hack the second one up to 10.13
 oder further … the next (big!) problem is, that lots of software would
 stop working. It’s a rattail. So I stay with it how it is until I make the
 next big step to new machines. Then with completely new architecture and
 blah.

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