[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 JULWAL1):

 Replying to [comment:25 tobypeterson]:
 > Yes, I understand all the above. I don't think cargo/rust version is the
 issue - as I said above, and as you identified, it's security-framework
 3.7.0 and its use of SecTrustEvaluateWithError.
 >
 > There are basically three options here:
 > - add SecTrustEvaluateWithError to legacy support, adopt it here (imo
 the best approach, but more work)
 > - hack for this specific port
 > - downgrade this port for old operating system versions
 \\
 Yes, agreed - the first two options are preferable...


 I decided to manually download the following four crates, unpack them and
 then run diff on Cargo.toml, trust.rs (and Cargo.toml.orig on the last two
 crates) for the different versions:

 {{{
 cd /tmp

 curl -LO https://static.crates.io/crates/security-framework/security-
 framework-3.5.1.crate
 curl -LO https://static.crates.io/crates/security-framework/security-
 framework-3.7.0.crate
 curl -LO https://static.crates.io/crates/security-framework-sys/security-
 framework-sys-2.15.0.crate
 curl -LO https://static.crates.io/crates/security-framework-sys/security-
 framework-sys-2.17.0.crate

 mkdir sf-compare

 tar -xzf security-framework-3.5.1.crate -C ./sf-compare
 tar -xzf security-framework-3.7.0.crate -C ./sf-compare
 tar -xzf security-framework-sys-2.15.0.crate -C ./sf-compare
 tar -xzf security-framework-sys-2.17.0.crate -C ./sf-compare

 diff -u ./sf-compare/security-framework-3.5.1/Cargo.toml ./sf-compare
 /security-framework-3.7.0/Cargo.toml > sf-Cargo.toml-diff.txt

 diff -u ./sf-compare/security-framework-3.5.1/src/trust.rs ./sf-compare
 /security-framework-3.7.0/src/trust.rs > sfs-trust.rs-diff.txt

 diff -u ./sf-compare/security-framework-sys-2.15.0/Cargo.toml ./sf-compare
 /security-framework-sys-2.17.0/Cargo.toml > sfs-Cargo.toml-diff.txt

 diff -u ./sf-compare/security-framework-sys-2.15.0/src/trust.rs ./sf-
 compare/security-framework-sys-2.17.0/src/trust.rs > sfs-trust.rs-diff.txt

 diff -u ./sf-compare/security-framework-sys-2.15.0/Cargo.toml.orig ./sf-
 compare/security-framework-sys-2.17.0/Cargo.toml.orig > sfs-Cargo.toml
 .orig-diff.txt
 }}}


 They show some very interesting changes in the source code for the
 different versions of security-framework and security-framework-sys and
 have attached the five .txt files as they could be very helpful.

 I'm currently STILL attempting to build rust-1.98 and cargo 0.99 on my
 macOS Sierra machine (which is taking ages).\\

 I notice there are .tbz2 files for both packages in
 https://packages.macports.org/rust/?C=M;O=D and
 https://packages.macports.org/cargo/?C=M;O=D .

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