Bug 2187983
| Summary: | rust-vm-memory-0.12.0 is available | ||
|---|---|---|---|
| Product: | [Fedora] Fedora | Reporter: | Upstream Release Monitoring <upstream-release-monitoring> |
| Component: | rust-vm-memory | Assignee: | Sergio Lopez <slopezpa> |
| Status: | CLOSED RAWHIDE | QA Contact: | |
| Severity: | unspecified | Docs Contact: | |
| Priority: | unspecified | ||
| Version: | rawhide | CC: | decathorpe, rust-sig, slopezpa |
| Target Milestone: | --- | Keywords: | FutureFeature, Triaged |
| Target Release: | --- | ||
| Hardware: | Unspecified | ||
| OS: | Unspecified | ||
| Whiteboard: | |||
| Fixed In Version: | Doc Type: | If docs needed, set a value | |
| Doc Text: | Story Points: | --- | |
| Clone Of: | Environment: | ||
| Last Closed: | 2023-08-04 11:19:14 UTC | Type: | --- |
| Regression: | --- | Mount Type: | --- |
| Documentation: | --- | CRM: | |
| Verified Versions: | Category: | --- | |
| oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | |
| Cloudforms Team: | --- | Target Upstream Version: | |
| Embargoed: | |||
| Bug Depends On: | |||
| Bug Blocks: | 2192920 | ||
|
Description
Upstream Release Monitoring
2023-04-19 10:56:18 UTC
Releases retrieved: 0.12.0 Upstream release that is considered latest: 0.12.0 Current version/release in rawhide: 0.10.0-2.fc39 URL: https://crates.io/crates/vm-memory 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/241786/ To change the monitoring settings for the project, please visit: https://src.fedoraproject.org/rpms/rust-vm-memory Looks like this update was pushed to Fedora 38+? Please remember that your packages are no longer the only ones depending on this crate, the uncoordinated update broke firecracker: https://koschei.fedoraproject.org/package/firecracker?collection=f39 (In reply to Fabio Valentini from comment #2) > Looks like this update was pushed to Fedora 38+? > > Please remember that your packages are no longer the only ones depending on > this crate, the uncoordinated update broke firecracker: > https://koschei.fedoraproject.org/package/firecracker?collection=f39 Sorry about that. I had libkrun and virtiofsd in mind, but forgot about firecracker. How do maintainers usually coordinate this kind of updates? Sharing a side-tag? Yep, usually a side tag that everybody builds their things into, so they can land together without causing broken dependencies. At least with Rust the problem doesn't propagate to runtime, so it's not *that* bad (except when broken dependencies block security rebuilds :)). Just keep this in mind next time you update these crates. You can use this script (or something similar) to check which packages are impacted by breaking updates: https://github.com/decathorpe/miscripts/blob/master/cratedeps rust-vm-memory-0.12.0 is now available on both rawhide and f38 |