Releases retrieved: 5.0.1 Upstream release that is considered latest: 5.0.1 Current version/release in rawhide: 5.0.0-6.fc37 URL: https://github.com/suve/copydeps 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://fedoraproject.org/wiki/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/138245/ To change the monitoring settings for the project, please visit: https://src.fedoraproject.org/rpms/rust-copydeps
This will require an update to rust-goblin, which is currently on v0.2.3. rust-copydeps-5.0.1 expects rust-goblin >= 0.5.2.
It helps if you actually block on the bug in question, because I use this information to prioritize what crate updates to work on next. :) It looks like I should be able to update goblin to the latest version without too much trouble (I hope), given that - latest version of copydeps already needs >= 0.5.2 - libbpf-cargo only uses it for its test suite - latest version of remoteprocess already needs >= 0.5.2 I'll just need to figure out the scroll 0.10 vs. 0.11 dependency.
Sorry, it completely slipped my mind to check if there's an open "update plx" bug against rust-goblin. For what it's worth, rust-copydeps does not depend on any API or behaviour changes made to libgoblin between v0.2.3 and v0.5.2.
FEDORA-2022-604de7aa86 has been submitted as an update to Fedora 37. https://bodhi.fedoraproject.org/updates/FEDORA-2022-604de7aa86
FEDORA-2022-604de7aa86 has been pushed to the Fedora 37 stable repository. If problem still persists, please make note of it in this bug report.