Closed cecton closed 2 years ago
Hi, @cecton! Your PR seems to update all the dependencies of vmm-reference to the latest version, and the build fails. I think there would be a few changes required to make the build pass, so if you just want to update vmm-sys-util
, you should change to vmm-sys-util = ">=0.8.0"
in all the Cargo.toml
s that have this dependency, and after that just cargo update -p vmm-sys-util
instead of cargo update
.
Otherwise we should fix all the build errors.
Ah there are more issues :disappointed: I wanted to use this repo's crates to avoid copying too much code. But if there are other things broken it might not help me much.
I guess I will fix all the dependencies first to be sure to be on the right versions of things.
Do you want to keep vmm-sys-util = ">=0.8.0"
on kvm-bindings btw? It's often preferable to keep things working in the "semver way" (so 0.8.0
or ~0.8.0
).
Do you want to keep
vmm-sys-util = ">=0.8.0"
on kvm-bindings btw? It's often preferable to keep things working in the "semver way" (so0.8.0
or~0.8.0
).
We can update that as well, but it's not going to help much with this PR because we would need to first publish a new version of kvm-bindings.
This PR is only for the option of fixing this on this side indeed. But if we fix it on kvm-bindings in patch then we can close this one.
We can fix it here temporarily so we can move forward. And we can also have a PR in kvm-bindings to fix it there, but that typically takes longer because you need to follow the release process which is not 0-cost.
Ok I'll do that hmm... "Soon" :tm:
Here is already this one. I just reverted the change on Cargo.lock. It will still fix things on my side, though tbh I don't really need this to be merged. I can use a path and do the small changes locally for myself for now.
The commit 'e2d6be7' should contain at least 3 lines: title, blank line and a sign-off one. Please check: https://www.midori-global.com/blog/2018/04/02/git-50-72-rule.
Alright I guess I need to rebase and squash and sign my commit xD
Should we though update the vmm-sys-util dependency in all crates?
I found some discordance in the dependencies:
This makes the update impossible because vm-vcpu keeps 0.8.0 while kvm-bindings updates to 0.9.
Either kvm-bindings needs to be set on
0.8.0
(which is equivalent to~0.8.0
or>=0.8.0 && <0.9.0
)oreither vm-vcpu needs to be set on>=0.8.0
. [edit: spelling]