[MacPorts] #73711: py313-maturin @1.12.6_0: failed to parse manifest
MacPorts
noreply at macports.org
Sun Aug 23 08:25:57 UTC 2026
#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):
Well, now it’s getting weird!
I updated cargo – 0.79.0_3 < 0.99.0_0. After that I retried.
Again:
{{{
:info:build running build_rust
: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.
}}}
I’ll ad the whole logfile.
Then I checked:
{{{
The following versions of cargo are currently installed:
1) cargo @0.79.0_3
2) cargo @0.99.0_0 (active)
}}}
So … what?!
Very strange. Maybe there is a deeper bug somewhere?
--
Ticket URL: <https://trac.macports.org/ticket/73711#comment:16>
MacPorts <https://www.macports.org/>
Ports system for macOS
More information about the macports-tickets
mailing list