Releases retrieved: 1.0.0 Upstream release that is considered latest: 1.0.0 Current version/release in rawhide: 0.5.0-1.fc39 URL: https://crates.io/crates/archery Please consult the package updates policy before you issue an update to a stable branch: https://docs.fedoraproject.org/en-US/fesco/Updates_Policy/ More information about the service that created this bug can be found at: https://docs.fedoraproject.org/en-US/package-maintainers/Upstream_Release_Monitoring Please keep in mind that with any upstream change, there may also be packaging changes that need to be made. Specifically, please remember that it is your responsibility to review the new version to ensure that the licensing is still correct and that no non-free or legally problematic items have been added upstream. Based on the information from Anitya: https://release-monitoring.org/project/360976/ To change the monitoring settings for the project, please visit: https://src.fedoraproject.org/rpms/rust-archery
FEDORA-2023-4b7bca2c29 has been submitted as an update to Fedora 39. https://bodhi.fedoraproject.org/updates/FEDORA-2023-4b7bca2c29
FEDORA-2023-4b7bca2c29 has been pushed to the Fedora 39 stable repository. If problem still persists, please make note of it in this bug report.
Updating this to v1.0.0 was probably well-intentioned, but likely not with the outcome that what you wanted. Both python-rpds-py and rust-rpds depend on archery >=0.5, <0.6 (that's what "^0.5" or "0.5" version specifiers translate to), so they'll both both be broken in rawhide.
(In reply to Fabio Valentini from comment #3) > Updating this to v1.0.0 was probably well-intentioned, but likely not with > the outcome that what you wanted. > > Both python-rpds-py and rust-rpds depend on archery >=0.5, <0.6 (that's what > "^0.5" or "0.5" version specifiers translate to), so they'll both both be > broken in rawhide. Yep, I was misguided by archery release notes that says "No changes. It’s just time to commit to a stable release" and didn't consider that rpds pin dep version as "<0.6". I'll patch them to accept 1.0.0 as soon as possible