Hi,
The Firecracker 1.9 release branch was forked earlier, and these are its crate updates not in Fedora by maintainer:
decathorpe: clap-4.5.16 derive_more-1.0.0 (API update) libc-0.2.158 quote-1.0.37 serde-1.0.209 serde_json-1.0.127 syn-2.0.76
slp: kvm-bindings-0.9.0 (API update) kvm-ioctls-0.18.0 (API update)
The release wasn't tagged yet, so there's no rush. I'm just sending the list now that it won't get any more dependabot bumps. (Although the committed release date in docs is Monday, 2024-09-02, which would be much sooner than the previous few releases.) Let me know if you'd like me to handle any of these updates, but I'll need to be added as comaintainer.
Thanks.
David
On Fri, Aug 30, 2024 at 4:19 PM David Michael fedora.dm0@gmail.com wrote:
Hi,
The Firecracker 1.9 release branch was forked earlier, and these are its crate updates not in Fedora by maintainer:
decathorpe: clap-4.5.16 derive_more-1.0.0 (API update) libc-0.2.158 quote-1.0.37 serde-1.0.209 serde_json-1.0.127 syn-2.0.76
Hi!
Thanks for the advance notice. I'll handle these seven packages over the next few days, as time permits.
Fabio
On Fri, Aug 30, 2024 at 10:19 AM David Michael fedora.dm0@gmail.com wrote:
The Firecracker 1.9 release branch was forked earlier, and these are its crate updates not in Fedora by maintainer:
slp: kvm-bindings-0.9.0 (API update) kvm-ioctls-0.18.0 (API update)
Just checking on this since it's been a couple weeks.
Everything in Fedora that uses these seems to have open-ended dependencies except Firecracker, and these crates and Firecracker are maintained by the same people upstream with quick releases so they'll probably require updates every couple months. I can take care of these updates if you add me as co-maintainer, I'd run a scratch build of their users in a side tag to verify they build with the new APIs. Or should I be trying to go through the Rust SIG rather than direct co-maintainer?
Thanks.
David
On Mon, Sep 16, 2024 at 1:15 PM David Michael fedora.dm0@gmail.com wrote:
On Fri, Aug 30, 2024 at 10:19 AM David Michael fedora.dm0@gmail.com wrote:
The Firecracker 1.9 release branch was forked earlier, and these are its crate updates not in Fedora by maintainer:
slp: kvm-bindings-0.9.0 (API update) kvm-ioctls-0.18.0 (API update)
Just checking on this since it's been a couple weeks.
Everything in Fedora that uses these seems to have open-ended dependencies except Firecracker, and these crates and Firecracker are maintained by the same people upstream with quick releases so they'll probably require updates every couple months. I can take care of these updates if you add me as co-maintainer, I'd run a scratch build of their users in a side tag to verify they build with the new APIs. Or should I be trying to go through the Rust SIG rather than direct co-maintainer?
In this case I would recommend to work with the "main" maintainer directly instead of relying on SIG powers. I don't know these crates well enough to judge whether any "technically" breaking release would cause issues - open-ended dependencies are really not good here.
Fabio
On Wed, Sep 18, 2024 at 9:05 AM Fabio Valentini decathorpe@gmail.com wrote:
On Mon, Sep 16, 2024 at 1:15 PM David Michael fedora.dm0@gmail.com wrote:
On Fri, Aug 30, 2024 at 10:19 AM David Michael fedora.dm0@gmail.com wrote:
The Firecracker 1.9 release branch was forked earlier, and these are its crate updates not in Fedora by maintainer:
slp: kvm-bindings-0.9.0 (API update) kvm-ioctls-0.18.0 (API update)
Just checking on this since it's been a couple weeks.
Everything in Fedora that uses these seems to have open-ended dependencies except Firecracker, and these crates and Firecracker are maintained by the same people upstream with quick releases so they'll probably require updates every couple months. I can take care of these updates if you add me as co-maintainer, I'd run a scratch build of their users in a side tag to verify they build with the new APIs. Or should I be trying to go through the Rust SIG rather than direct co-maintainer?
In this case I would recommend to work with the "main" maintainer directly instead of relying on SIG powers. I don't know these crates well enough to judge whether any "technically" breaking release would cause issues - open-ended dependencies are really not good here.
Okay, I was given commit access earlier today. The dependent packages had no FTBFS related to these crates, so I pushed the updates. Thanks, everyone.
David