[Rust] Re: Firecracker 1.8 crate updates

[Sergio Lopez Pascual]

David Michael  writes:
> On Thu, Jun 27, 2024 at 7:55 AM David Michael  wrote:
> > On Tue, Jun 4, 2024 at 7:26 PM David Michael  wrote:
> > > On Tue, Jun 4, 2024 at 9:15 AM Sergio Lopez Pascual  wrote:
> > > > Sergio Lopez Pascual  writes:
> > > > > David Michael  writes:
> > > > > > (CCing maintainers of virtiofsd and vhost-device-* packages that would
> > > > > > be affected when these dependency updates are ready.)
> > > > > >
> > > > > > On Mon, May 27, 2024 at 1:53 PM David Michael  wrote:
> > > > > > > It's been ~2 months since I last pestered about dependency updates, so
> > > > > > > it's that time again.  The 1.8 release branch was only created
> > > > > > > recently, and if it goes like the last release, there could be a few
> > > > > > > weeks of stabilization before it's actually tagged.  There's no rush,
> > > > > > > I'm just sending this list to get ahead of it.  These are the minimum
> > > > > > > versions in the 1.8 branch needing updates:
> > > > > >
> > > > > > > - kvm-bindings 0.8.0 (API change from 0.7.0, 0.8.1 available)
> > > > > > > - kvm-ioctls 0.17.0 (API change from 0.16.0)
> > > > > > > - vhost 0.11.0 (API change from 0.10.0)
> > > > > > > - vm-memory 0.14.1 (from 0.14.0)
> > > > > > > These are mostly API bumps.  It looks like users libkrun and sev have
> > > > > > > open-ended dependencies and won't be affected, and virtiofsd and
> > > > > > > vhost-device-* crates have bumped deps upstream but need new releases.
> > > > > >
> > > > > > They released kvm-bindings-0.8.2 yesterday with a performance fix, can
> > > > > > you make sure to include that one?
> > > > > >
> > > > > > Also let me know if you think this would be easier if I maintained the
> > > > > > latest versions of some of these crates due to Firecracker's faster
> > > > > > releases.  If you were to have API-stable versions for Red Hat's
> > > > > > rust-vmm-based projects, then they wouldn't be forced to update on
> > > > > > Firecracker's schedule every couple months.
> > > > >
> > > > > Hi David,
> > > > >
> > > > > We don't have plans to maintain API-stable versions. I'll start
> > > > > preparing another rust-vmm omnibus update on a side-tag tomorrow.
> > > > >
> > > > > Thanks,
> > > > > Sergio.
> > > >
> > > > Hi,
> > > >
> > > > Could you please push your updated packages to f41-build-side-90533 ?
> > >
> > > I've added the rust-vm-fdt update to it, but firecracker-1.8 itself
> > > still hasn't been tagged.  (I sent the original message early for time
> > > to prepare, when they created the release branch for stabilization
> > > with all the crate updates in place.)  A scratch build of the release
> > > branch looks good, though.
> > >
> > > https://koji.fedoraproject.org/koji/taskinfo?taskID=118579215
> >
> > It looks like that tag was deleted yesterday.
> >
> > https://koji.fedoraproject.org/koji/taginfo?tagID=90533
> >
> > Last I heard, Firecracker 1.8 will be released over the weekend.  Is
> > there another tag I should use for it?
>
> I haven't seen a new tag, do you want me to create it?  I could move
> the builds that are dependencies of Firecracker using what Fabio
> wrote, but I don't know if you had any additional updates in there
> (and I don't know how to list them after the tag was deleted).  The
> only update I added was rust-vm-fdt.

Hi,

I've just created side-tag f41-build-side-92243 and moved the packages
there. Please add rust-vm-fdt and firecracker there.

Thanks!
Sergio.