Firecracker 1.8 crate updates

[David Michael]

Hi,

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:

decathorpe:
- itertools 0.13.0 (API change from 0.12.1)
- libc 0.2.155 (from 0.2.154)
- proc-macro2 1.0.83 (from 1.0.82, 1.0.84 available)
- serde 1.0.202 (from 1.0.200, 1.0.203 available)
- syn 2.0.65 (from 2.0.64, 2.0.66 available)
- thiserror 1.0.61 (from 1.0.60)
The first one will probably require a compat package, and there is
another app needing it in the itertools upgrade Bugzilla ticket.  I
could downgrade this with a patch if that's preferred, though.

slp:
- 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.

There is also a vm-fdt API bump which I can push along with
firecracker-1.8 since that's the only user (aside from libkrun's
unbound dependency).  Let me know if you want me to handle any of
these other updates, although I'd need to be added as a comaintainer.

Thanks.

David

[Fabio Valentini]

On Mon, May 27, 2024 at 7:53 PM David Michael  wrote:
> Hi,
>
> 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:
>
> decathorpe:
> itertools 0.13.0 (API change from 0.12.1)
> libc 0.2.155 (from 0.2.154)
> proc-macro2 1.0.83 (from 1.0.82, 1.0.84 available)
> serde 1.0.202 (from 1.0.200, 1.0.203 available)
> syn 2.0.65 (from 2.0.64, 2.0.66 available)
> thiserror 1.0.61 (from 1.0.60)
>
> The first one will probably require a compat package, and there is
> another app needing it in the itertools upgrade Bugzilla ticket.  I
> could downgrade this with a patch if that's preferred, though.

All of these should be taken care of:
https://bodhi.fedoraproject.org/updates/FEDORA-2024-592736f5db
https://bodhi.fedoraproject.org/updates/FEDORA-2024-27ee5aeda3

Except for itertools v0.13, where I am waiting for this ticket to get processed:
https://pagure.io/releng/fedora-scm-requests/issue/62659

Fabio

[David Michael]

On Tue, May 28, 2024 at 12:28 PM Fabio Valentini  wrote:
> On Mon, May 27, 2024 at 7:53 PM David Michael  wrote:
> > Hi,
> >
> > 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:
> >
> > decathorpe:
> > itertools 0.13.0 (API change from 0.12.1)
> > libc 0.2.155 (from 0.2.154)
> > proc-macro2 1.0.83 (from 1.0.82, 1.0.84 available)
> > serde 1.0.202 (from 1.0.200, 1.0.203 available)
> > syn 2.0.65 (from 2.0.64, 2.0.66 available)
> > thiserror 1.0.61 (from 1.0.60)
> >
> > The first one will probably require a compat package, and there is
> > another app needing it in the itertools upgrade Bugzilla ticket.  I
> > could downgrade this with a patch if that's preferred, though.
>
> All of these should be taken care of:
> https://bodhi.fedoraproject.org/updates/FEDORA-2024-592736f5db
> https://bodhi.fedoraproject.org/updates/FEDORA-2024-27ee5aeda3
>
> Except for itertools v0.13, where I am waiting for this ticket to get processed:
> https://pagure.io/releng/fedora-scm-requests/issue/62659

Looks good, thanks for getting this done so quickly again.

David

[David Michael]

(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.

Thanks.

David

[Sergio Lopez Pascual]

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.

[Sergio Lopez Pascual]

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 ?

Thanks,
Sergio.

[David Michael]

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

Thanks.

David

[David Michael]

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?

Thanks.

David

[Fabio Valentini]

On Thu, Jun 27, 2024 at 3:44 PM 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?

You can request a new side-tag and move the builds into it (if they
haven't been submitted to bodhi yet) with "koji tag-build
f41-build-side-<number> <nvr> <nvr> ...".

Fabio

[David Michael]

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.

Thanks.

David

[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.

[David Michael]

On Wed, Jul 10, 2024 at 5:42 AM Sergio Lopez Pascual  wrote:
> 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.

Okay, it looks good.  I've added rust-vm-fdt and built firecracker for
it.  Thanks again.

David

[Sergio Lopez]

Hi David,

I've created side-tags for f39 and f40, could you please add your packages
there too:

Side tag 'f39-build-side-92706' (id 92706) created.
Use 'fedpkg build --target=f39-build-side-92706' to use it.
Use 'koji wait-repo f39-build-side-92706' to wait for the build repo to be
generated.

Side tag 'f40-build-side-92614' (id 92614) created.
Use 'fedpkg build --target=f40-build-side-92614' to use it.
Use 'koji wait-repo f40-build-side-92614' to wait for the build repo to be
generated.

Also, do you want to do f38 too?

Thanks,
Sergio.

On Wed, Jul 10, 2024 at 2:03 PM David Michael  wrote:
> On Wed, Jul 10, 2024 at 5:42 AM Sergio Lopez Pascual 
> wrote:
> > 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 <
>
> [e-mail]> 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.
>
> Okay, it looks good.  I've added rust-vm-fdt and built firecracker for
> it.  Thanks again.
> David
>
> Rust mailing list -- [e-mail]
> To unsubscribe send an email to [e-mail]
> Fedora Code of Conduct:
> https://docs.fedoraproject.org/en-US/project/code-of-conduct/
> List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
> List Archives:
> https://lists.fedoraproject.org/archives/list/[e-mail]
> Do not reply to spam, report it:
> https://pagure.io/fedora-infrastructure/new_issue

[David Michael]

On Wed, Jul 17, 2024 at 10:18 AM Sergio Lopez  wrote:
> Hi David,
>
> I've created side-tags for f39 and f40, could you please add your packages there too:

Okay, I've added my updates to those tags.
> Also, do you want to do f38 too?

I thought f38 was EOL for a while now and we can't push updates to it
anymore.  If you want to update it and have the ability to do so, I
can add my updates, but I wasn't planning on it otherwise.

Thanks.

David

[Fabio Valentini]

On Wed, Jul 17, 2024 at 10:05 PM David Michael  wrote:
> On Wed, Jul 17, 2024 at 10:18 AM Sergio Lopez  wrote:
> > Hi David,
> >
> > I've created side-tags for f39 and f40, could you please add your packages there too:
>
> Okay, I've added my updates to those tags.
> > Also, do you want to do f38 too?
>
> I thought f38 was EOL for a while now and we can't push updates to it
> anymore.  If you want to update it and have the ability to do so, I
> can add my updates, but I wasn't planning on it otherwise.

Yes, Fedora 38 is EOL. You wouldn't be able to update things there
even if you wanted :)

Side note:

Please take care of all the broken dependencies that this incomplete
update has already caused in rawhide.
At least the following packages now fail to build due to broken dependencies:

- rust-kvm-ioctls
- rust-vhost-device-scmi
- rust-vhost-device-sound
- rust-vhost-user-backend

If you also want to push your updates to stable branches, please avoid
introducing the same issues there, and ideally, fix them in rawhide
first and then merge the same changes to stable branches too.

Fabio

[Sergio Lopez Pascual]

Fabio Valentini  writes:
> On Wed, Jul 17, 2024 at 10:05 PM David Michael  wrote:
> > On Wed, Jul 17, 2024 at 10:18 AM Sergio Lopez  wrote:
> > > Hi David,
> > >
> > > I've created side-tags for f39 and f40, could you please add your packages there too:
> >
> > Okay, I've added my updates to those tags.
> > > Also, do you want to do f38 too?
> >
> > I thought f38 was EOL for a while now and we can't push updates to it
> > anymore.  If you want to update it and have the ability to do so, I
> > can add my updates, but I wasn't planning on it otherwise.
>
> Yes, Fedora 38 is EOL. You wouldn't be able to update things there
> even if you wanted :)
>
> Side note:
>
> Please take care of all the broken dependencies that this incomplete
> update has already caused in rawhide.
> At least the following packages now fail to build due to broken dependencies:
> rust-kvm-ioctls
> rust-vhost-device-scmi
> rust-vhost-device-sound
> rust-vhost-user-backend

That's weird. I've missed vhost-device-scmi and vhost-device-sound, but
kvm-ioctls and vhost-user-backend were part of the update. I only see a
BZ for vhost-device-sound, where can I find the failed build tasks for
the others?

Thanks,
Sergio.

[Fabio Valentini]

On Thu, Jul 18, 2024 at 12:03 PM Sergio Lopez Pascual  wrote:
> Fabio Valentini  writes:
> > On Wed, Jul 17, 2024 at 10:05 PM David Michael  wrote:
> > > On Wed, Jul 17, 2024 at 10:18 AM Sergio Lopez  wrote:
> > > > Hi David,
> > > >
> > > > I've created side-tags for f39 and f40, could you please add your packages there too:
> > >
> > > Okay, I've added my updates to those tags.
> > > > Also, do you want to do f38 too?
> > >
> > > I thought f38 was EOL for a while now and we can't push updates to it
> > > anymore.  If you want to update it and have the ability to do so, I
> > > can add my updates, but I wasn't planning on it otherwise.
> >
> > Yes, Fedora 38 is EOL. You wouldn't be able to update things there
> > even if you wanted :)
> >
> > Side note:
> >
> > Please take care of all the broken dependencies that this incomplete
> > update has already caused in rawhide.
> > At least the following packages now fail to build due to broken dependencies:
> > rust-kvm-ioctls
> > rust-vhost-device-scmi
> > rust-vhost-device-sound
> > rust-vhost-user-backend
>
> That's weird. I've missed vhost-device-scmi and vhost-device-sound, but
> kvm-ioctls and vhost-user-backend were part of the update. I only see a
> BZ for vhost-device-sound, where can I find the failed build tasks for
> the others?

In koschei:
https://koschei.fedoraproject.org/groups/rust-sig?collection=f41

Fabio