From: "Daniel P. Berrangé" <berrange@redhat.com>
To: Thomas Huth <thuth@redhat.com>
Cc: Peter Maydell <peter.maydell@linaro.org>,
qemu-devel@nongnu.org, qemu-stable@nongnu.org
Subject: Re: [PATCH v2] docs/conf.py: Remove usage of distutils
Date: Mon, 4 Mar 2024 18:04:49 +0000 [thread overview]
Message-ID: <ZeYNQdqW2bBA4gNL@redhat.com> (raw)
In-Reply-To: <3262c873-b845-4286-a71f-a53b96bbc8a9@redhat.com>
On Mon, Mar 04, 2024 at 06:11:58PM +0100, Thomas Huth wrote:
> On 04/03/2024 17.56, Peter Maydell wrote:
> > On Mon, 4 Mar 2024 at 13:04, Thomas Huth <thuth@redhat.com> wrote:
> > >
> > > The macOS jobs in our CI recently started failing, complaining that
> > > the distutils module is not available anymore. And indeed, according to
> > > https://peps.python.org/pep-0632/ it's been deprecated since a while
> > > and now likely got removed in recent Python versions.
> >
> > This doesn't seem to be sufficient to fix the macos CI:
> > something in glib seems to still be using it.
> >
> > https://gitlab.com/qemu-project/qemu/-/jobs/6313212803
> >
> > [281/6553] Generating ui/dbus-display gdbus-codegen with a custom command
> > FAILED: ui/dbus-display1.h ui/dbus-display1.c
> > /opt/homebrew/Cellar/glib/2.78.4/bin/gdbus-codegen
> > ui/dbus-display1.xml --glib-min-required 2.64 --output-directory
> > /private/var/folders/xc/tpssff9959345bnqq4c6tlww0000gn/T/cirrus-ci-build/build/ui
> > --interface-prefix org.qemu. --c-namespace QemuDBus --generate-c-code
> > dbus-display1
> ...
> > ModuleNotFoundError: No module named 'distutils'
>
> Looking at the glib sources, I think this has been fixed here:
>
> https://gitlab.gnome.org/GNOME/glib/-/commit/6ef967a0f930ce37a8c9b5aff96969
>
> The fix will be in glib 2.79, unfortunately homebrew still seems to use glib
> 2.78 ...
>
> We could maybe temporarily work-around the problem by disabling the dbus
> code in the CI job? Or just wait for homebrew to update the package?
File a bug against homebrew. IME they are very quick (1-3 days) at
putting out fixes for things like this, especially if you point them
to the upstream solution.
With regards,
Daniel
--
|: https://berrange.com -o- https://www.flickr.com/photos/dberrange :|
|: https://libvirt.org -o- https://fstop138.berrange.com :|
|: https://entangle-photo.org -o- https://www.instagram.com/dberrange :|
next prev parent reply other threads:[~2024-03-04 18:06 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-03-04 13:04 [PATCH v2] docs/conf.py: Remove usage of distutils Thomas Huth
2024-03-04 13:09 ` Michael Tokarev
2024-03-04 13:10 ` Thomas Huth
2024-03-04 16:56 ` Peter Maydell
2024-03-04 17:11 ` Thomas Huth
2024-03-04 18:04 ` Daniel P. Berrangé [this message]
2024-03-05 10:39 ` Thomas Huth
2024-03-09 17:27 ` Peter Maydell
2024-03-09 18:29 ` Philippe Mathieu-Daudé
2024-03-09 20:15 ` Peter Maydell
2024-03-10 14:10 ` Peter Maydell
2024-03-04 21:15 ` Alex Bennée
2024-03-05 9:44 ` Peter Maydell
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=ZeYNQdqW2bBA4gNL@redhat.com \
--to=berrange@redhat.com \
--cc=peter.maydell@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 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.