From: Peter Maydell <peter.maydell@linaro.org>
To: "Alex Bennée" <alex.bennee@linaro.org>
Cc: qemu-devel@nongnu.org, qemu-stable@nongnu.org,
"Yonggang Luo" <luoyonggang@gmail.com>,
"Philippe Mathieu-Daudé" <philmd@linaro.org>,
"Thomas Huth" <thuth@redhat.com>
Subject: Re: [PATCH] .gitlab-ci/windows.yml: Don't install libusb or spice packages on 32-bit
Date: Fri, 16 Feb 2024 13:19:54 +0000 [thread overview]
Message-ID: <CAFEAcA-7S7QOBzDBS0UmWDxK=2AWuX1QFZ-TCfvCOOhJpL-wng@mail.gmail.com> (raw)
In-Reply-To: <87y1bk4pfz.fsf@draig.linaro.org>
On Fri, 16 Feb 2024 at 11:29, Alex Bennée <alex.bennee@linaro.org> wrote:
>
> Peter Maydell <peter.maydell@linaro.org> writes:
>
> > When msys2 updated their libusb packages to libusb 1.0.27, they
> > dropped support for building them for mingw32, leaving only mingw64
> > packages. This broke our CI job, as the 'pacman' package install now
> > fails with:
> >
> > error: target not found: mingw-w64-i686-libusb
> > error: target not found: mingw-w64-i686-usbredir
> >
> > (both these binary packages are from the libusb source package).
> >
> > Similarly, spice is now 64-bit only:
> > error: target not found: mingw-w64-i686-spice
> >
> > Fix this by dropping these packages from the list we install for our
> > msys2-32bit build. We do this with a simple mechanism for the
> > msys2-64bit and msys2-32bit jobs to specify a list of extra packages
> > to install on top of the common ones we install for both jobs.
> >
> > Cc: qemu-stable@nongnu.org
> > Resolves: https://gitlab.com/qemu-project/qemu/-/issues/2160
> > Signed-off-by: Peter Maydell <peter.maydell@linaro.org>
>
> Queued to testing/next, thanks.
I'm just testing a merge where I've applied this directly to
get our CI back to green, so you don't need to take it via
your tree.
thanks
-- PMM
next prev parent reply other threads:[~2024-02-16 13:21 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-02-15 15:50 [PATCH] .gitlab-ci/windows.yml: Don't install libusb or spice packages on 32-bit Peter Maydell
2024-02-15 17:36 ` Philippe Mathieu-Daudé
2024-02-15 18:54 ` Michael Tokarev
2024-02-16 11:29 ` Alex Bennée
2024-02-16 13:19 ` Peter Maydell [this message]
2024-02-16 15:47 ` Alex Bennée
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='CAFEAcA-7S7QOBzDBS0UmWDxK=2AWuX1QFZ-TCfvCOOhJpL-wng@mail.gmail.com' \
--to=peter.maydell@linaro.org \
--cc=alex.bennee@linaro.org \
--cc=luoyonggang@gmail.com \
--cc=philmd@linaro.org \
--cc=qemu-devel@nongnu.org \
--cc=qemu-stable@nongnu.org \
--cc=thuth@redhat.com \
/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;
as well as URLs for NNTP newsgroup(s).