From: "Daniel P. Berrangé" <berrange@redhat.com>
To: Paolo Bonzini <pbonzini@redhat.com>
Cc: Manos Pitsidianakis <manos.pitsidianakis@linaro.org>,
qemu-devel@nongnu.org, Peter Maydell <peter.maydell@linaro.org>
Subject: Re: [PATCH] rust: suggest passing --locked to "cargo install"
Date: Wed, 18 Mar 2026 12:31:57 +0000 [thread overview]
Message-ID: <abqbPUmpiVkdXafC@redhat.com> (raw)
In-Reply-To: <2c5efc3d-8e36-4ca4-8593-9cf9e64c7982@redhat.com>
On Wed, Mar 18, 2026 at 01:27:35PM +0100, Paolo Bonzini wrote:
> On 3/18/26 10:43, Daniel P. Berrangé wrote:
> > On Wed, Mar 18, 2026 at 11:32:59AM +0200, Manos Pitsidianakis wrote:
> > > > The "cargo install bindgen-cli" command does not use QEMU's Cargo.lock,
> > >
> > > So what does `--locked` do here? As per `--help`: "--locked Assert
> > > that `Cargo.lock` will remain unchanged" What Cargo.lock does it not
> > > change?
> >
> > --locked ensures that cargo honours the Cargo.lock from the bindgen.git
> > repo, instead of pulling in arbitrarily newer dependencies. The
> > fixed versions of deps in bindgen's Cargo.lock are still compatible
> > with edition2021, but the latest deps are only compatible with edition2024,
> > and we need edition2021
>
> ... and that does mean that sooner or later bindgen might update to a
> version that requires 2024 and we're out of luck. So we could indeed add
> "--version" too, just like Manos suggested. (Separately because this issue
> was breaking the build and Peter speed-runned the merging).
>
> That said, support for 22.04 is going away soon and at that point "cargo
> install" will only be needed for the nightly job. So it's not super
> necessary, either.
Indeed, as soon as this pending release of QEMU is finalized, we can
bump the min Ubuntu to 24.04
With regards,
Daniel
--
|: https://berrange.com ~~ https://hachyderm.io/@berrange :|
|: https://libvirt.org ~~ https://entangle-photo.org :|
|: https://pixelfed.art/berrange ~~ https://fstop138.berrange.com :|
next prev parent reply other threads:[~2026-03-18 12:32 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-03-18 8:21 [PATCH] rust: suggest passing --locked to "cargo install" Paolo Bonzini
2026-03-18 8:51 ` Manos Pitsidianakis
2026-03-18 9:28 ` Paolo Bonzini
2026-03-18 9:32 ` Manos Pitsidianakis
2026-03-18 9:43 ` Daniel P. Berrangé
2026-03-18 12:27 ` Paolo Bonzini
2026-03-18 12:31 ` Daniel P. Berrangé [this message]
2026-03-18 8:54 ` Daniel P. Berrangé
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=abqbPUmpiVkdXafC@redhat.com \
--to=berrange@redhat.com \
--cc=manos.pitsidianakis@linaro.org \
--cc=pbonzini@redhat.com \
--cc=peter.maydell@linaro.org \
--cc=qemu-devel@nongnu.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox