TL;DR: It would be great if I could update maturin in epel10.0 to the version that is currently already available in epel10. This would allow me to resolve an FTBFS issue I accidentally caused - but it would also bring quite a lot of bug fixes and improvements, and also make it easier to merge potential future fixes from the epel10 branch, if needed.

I did not post something to the epel-devel list for this request since it's not an incompatible update - maturin itself is the only user-facing package, and it has no breaking changes. The only "breaking" changes according to current EPEL Policy are in the library-only / source-only Rust packages whose sole and only purpose in epel10.0 is to be available for building maturin.

• epel10 currently has maturin 1.8.3.
• epel10.0 currently has maturin 1.7.4.

There were no breaking changes between these two versions, and the new versions have not caused issues in either Fedora 40+ or EPEL 10.

Release notes for releases between 1.7.4 and 1.8.3:

• https://github.com/PyO3/maturin/releases/tag/v1.7.5
• https://github.com/PyO3/maturin/releases/tag/v1.7.6
• https://github.com/PyO3/maturin/releases/tag/v1.7.7
• https://github.com/PyO3/maturin/releases/tag/v1.7.8
• https://github.com/PyO3/maturin/releases/tag/v1.8.0
• https://github.com/PyO3/maturin/releases/tag/v1.8.1
• https://github.com/PyO3/maturin/releases/tag/v1.8.2
• https://github.com/PyO3/maturin/releases/tag/v1.8.3

Merging this update would require including updates for some source-only / library-only packages for Rust crates that are now against the Updates Policy for EPEL 10.0:

• rust-pep440_rs from v0.6 to v0.7
• rust-pep508_rs from v0.6 to v0.9
• rust-pyproject-toml from v0.11 to v0.13
• rust-version-ranges (new package)

As mentioned in the TL;DR, I had already accidentally merged an update for rust-minijinja from v1 to v2 (having temporarily suffered from the delusion that minijinja v2 was of course already in epel10.0 - when it was not), which is also required for building maturin 1.8.3.

Alternatively it should be possible to downgrade rust-minijinja from v2 to v1 in the epel10.0 branch, however, I would prefer to go forward in time instead of backwards. This would also make future changes (if needed) a lot easier, since backporting bugfixes is often difficult without being able to also do the corresponding dependency updates.