Releases retrieved: 0.3.0 Upstream release that is considered latest: 0.3.0 Current version/release in rawhide: 0.2.0-4.fc37 URL: https://crates.io/crates/sevctl 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/188189/ To change the monitoring settings for the project, please visit: https://src.fedoraproject.org/rpms/rust-sevctl
*** Bug 2109347 has been marked as a duplicate of this bug. ***
If sevctl 0.3.0 is broadly compatible with 0.2.0, please consider updating it on Fedora 36 and 35 as well. Keeping the versions of Rust crates consistent across Fedora releases makes my work to keep everything up-to-date and in working order much easier. If you have any questions regarding the Rust packaging side of things for the sev / sevctl 0.3.0 updates, feel free to ping me.
(In reply to Fabio Valentini from comment #2) > If sevctl 0.3.0 is broadly compatible with 0.2.0, please consider updating > it on Fedora 36 and 35 as well. > Keeping the versions of Rust crates consistent across Fedora releases makes > my work to keep everything up-to-date and in working order much easier. > > If you have any questions regarding the Rust packaging side of things for > the sev / sevctl 0.3.0 updates, feel free to ping me. Hi Fabio, thanks for the help. One question I have is that while updating the release of the sev library (rust-sev), the scratch-build has a dependency on a crate that couldn't be found by Fedora packaging (namely, the serde-big-array crate). Here is the root.log: https://kojipkgs.fedoraproject.org//work/tasks/5087/89875087/root.log What are the next steps here? Should I release a new version of serde-big-array?
> Problem: nothing provides requested (crate(serde-big-array/default) >= 0.4.1 with crate(serde-big-array/default) < 0.5.0~) When you see an error message like this, it means one of two things: - either serde-big-array crate is not packaged for Fedora yet, - or the version of the crate is not compatible what your build has requested. In this case, the crate is already packaged, but at version 0.3.2: https://src.fedoraproject.org/rpms/rust-serde-big-array In this case, serde-big-array 0.3.x is required by the "serde1" feature of average, so the way to handle this would be twofold: - update rust-serde-big-array to version 0.4.1 - introduce a compat package rust-serde-big-array0.3 for versions 0.3.x Any Rust SIG member should be able to handle these steps. But given that that's basically just me right now, I'll put it on top of my TODO list for after the ongoing mass rebuild. BTW: All Rust crates *should* be set up with release-monitoring. So if you encounter something that's not at a version that you need yet, find the corresponding release-monitoring bug at <https://bugz.fedoraproject.org/rust-$crate>, and mark it as blocking for whatever you're working on. I've done that just now for this case (marked serde-big-array 0.4.1 update as blocking sev 0.3.0).
FEDORA-2022-a140c130b4 has been submitted as an update to Fedora 38. https://bodhi.fedoraproject.org/updates/FEDORA-2022-a140c130b4
FEDORA-2022-a140c130b4 has been pushed to the Fedora 38 stable repository. If problem still persists, please make note of it in this bug report.