From: Thomas Huth <thuth@redhat.com>
To: "Daniel P. Berrangé" <berrange@redhat.com>
Cc: qemu-devel@nongnu.org, "Paolo Bonzini" <pbonzini@redhat.com>,
qemu-stable@nongnu.org,
"Marc-André Lureau" <marcandre.lureau@redhat.com>,
"Philippe Mathieu-Daudé" <philmd@linaro.org>,
"Peter Lieven" <pl@dlhnet.de>,
qemu-block@nongnu.org, "Stefan Hajnoczi" <stefanha@redhat.com>,
"Paolo Bonzini" <pbonzini@redhat.com>,
"Richard W.M. Jones" <rjones@redhat.com>
Subject: Re: [PATCH] meson.build: Disallow libnfs v6 to fix the broken macOS build
Date: Wed, 18 Dec 2024 11:45:38 +0100 [thread overview]
Message-ID: <92fcd473-588b-4981-9f14-b802a9e6aa84@redhat.com> (raw)
In-Reply-To: <Z2Kmo_Kixrun1mAl@redhat.com>
On 18/12/2024 11.40, Daniel P. Berrangé wrote:
> On Wed, Dec 18, 2024 at 07:51:57AM +0100, Thomas Huth wrote:
>> The macOS build in our CI is currently broken since homebrew
>> updated libnfs to version 6 - and that version apparently comes
>> with a big API breakage. Disallow that version for now to get the
>> broken CI job working again. Once somebody had enough time to
>> adapt our code in block/nfs.c, we can revert this change again.
>
> NB This isn't limited to macOS. We've already been broken by
> this in Fedora:
>
> https://lists.nongnu.org/archive/html/qemu-block/2024-12/msg00151.html
>
> other distros will no doubt break too soon enough.
Ah, that discussion was on qemu-block, not on qemu-devel, that's why I
didn't notice it :-/ Thanks for the pointer!
Thomas
prev parent reply other threads:[~2024-12-18 10:46 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-12-18 6:51 [PATCH] meson.build: Disallow libnfs v6 to fix the broken macOS build Thomas Huth
2024-12-18 10:31 ` Philippe Mathieu-Daudé
2024-12-18 10:40 ` Daniel P. Berrangé
2024-12-18 10:45 ` Thomas Huth [this message]
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=92fcd473-588b-4981-9f14-b802a9e6aa84@redhat.com \
--to=thuth@redhat.com \
--cc=berrange@redhat.com \
--cc=marcandre.lureau@redhat.com \
--cc=pbonzini@redhat.com \
--cc=philmd@linaro.org \
--cc=pl@dlhnet.de \
--cc=qemu-block@nongnu.org \
--cc=qemu-devel@nongnu.org \
--cc=qemu-stable@nongnu.org \
--cc=rjones@redhat.com \
--cc=stefanha@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.