Releases retrieved: 0.4.0, 0.4.1 Upstream release that is considered latest: 0.4.1 Current version/release in rawhide: 0.3.2-4.fc39 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://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/188189/ To change the monitoring settings for the project, please visit: https://src.fedoraproject.org/rpms/rust-sevctl
Looks like this was pushed to rawhide? Note that there's a build failure that seems to be caused by sev v1.2.1, which apparently hid some previously public modules (which should almost certainly have been breaking release, i.e. 2.0.0, but wasn't): --> src/session.rs:11:5 | 11 | use ::sev::certs::sev::Certificate; | ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ no `Certificate` in `certs::sev` | help: consider importing one of these items instead | 11 | use crate::sev::ca::Certificate; | ~~~~~~~~~~~~~~~~~~~~~~~~~~~ 11 | use crate::sev::sev::Certificate; | ~~~~~~~~~~~~~~~~~~~~~~~~~~~~ 11 | use crate::snp::Certificate; | ~~~~~~~~~~~~~~~~~~~~~~~ 11 | use native_tls::Certificate; | ~~~~~~~~~~~~~~~~~~~~~~~ and 3 other candidates (and dozens more of similar failures) c.f. https://koschei.fedoraproject.org/package/rust-sevctl?collection=f39
When checking out Cargo.toml for the 0.4.1 build: [dependencies.sev] version = "1.1.0" features = ["openssl"] You're right, there were API-breaking changes in 1.2.0, but that's not the version that this build uses. I'll note that while version 1.1.0 is available in f38 + f37, I haven't built it for rawhide, and thus 1.2.0 might be the only build available. Would this be the problem?
Yes, only the latest version of a package is available for builds. > [dependencies.sev] > version = "1.1.0" > features = ["openssl"] This translates to "sev >= 1.1.0, < 2.0.0", and both RPM and cargo will resolve this to the highest version that's available (in this case, only 1.2.0 is available).
(In reply to Fabio Valentini from comment #3) > Yes, only the latest version of a package is available for builds. > > > [dependencies.sev] > > version = "1.1.0" > > features = ["openssl"] > > This translates to "sev >= 1.1.0, < 2.0.0", and both RPM and cargo will > resolve this to the highest version that's available (in this case, only > 1.2.0 is available). That is, if and only if 1.1.0 is not available, correct?
Releases retrieved: 0.4.2 Upstream release that is considered latest: 0.4.2 Current version/release in rawhide: 0.4.1-1.fc39 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://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/188189/ To change the monitoring settings for the project, please visit: https://src.fedoraproject.org/rpms/rust-sevctl
Releases retrieved: 0.4.3 Upstream release that is considered latest: 0.4.3 Current version/release in rawhide: 0.4.1-1.fc39 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://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/188189/ To change the monitoring settings for the project, please visit: https://src.fedoraproject.org/rpms/rust-sevctl
Marking as COMPLETED as I've addressed the sev library issue in a release for 0.4.3. Built here: https://koji.fedoraproject.org/koji/buildinfo?buildID=2270601