On Tue, 5 Mar 2024 at 10:39, Thomas Huth <th...@redhat.com> wrote: > > On 04/03/2024 19.04, Daniel P. Berrangé wrote: > > 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 <th...@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. > > Ok, while I was writing my mail, I was looking at https://brew.sh/ and > didn't see a link to a bug tracker there ... but now I realized that they > are simply using the github tracker, so I went ahead and filed a bug there: > > https://github.com/Homebrew/brew/issues/16823 > > Let's see how it goes...
Seems to be going slowly. I notice that there's a comment in there saying that "brew install python-setuptools" is a workaround to get glib 2.78 working -- that seems like it would be good to get our CI back to green. Is there a way to test changes to the cirrus config short of committing it and seeing if it helps? I don't see the jobs available on a pipeline in my personal gitlab repo... thanks -- PMM
