From: Peter Maydell <peter.maydell@linaro.org>
To: "Daniel P. Berrangé" <berrange@redhat.com>
Cc: Paolo Bonzini <pbonzini@redhat.com>,
QEMU Developers <qemu-devel@nongnu.org>
Subject: Re: meson complains about "broken python installation"
Date: Mon, 1 Nov 2021 15:13:10 +0000 [thread overview]
Message-ID: <CAFEAcA8eND_knYS23YDyX6ZboXJxn-0FYiQ3kq2gAMot14ZkaA@mail.gmail.com> (raw)
In-Reply-To: <YYACktMpIIswE9Zi@redhat.com>
On Mon, 1 Nov 2021 at 15:07, Daniel P. Berrangé <berrange@redhat.com> wrote:
>
> On Mon, Nov 01, 2021 at 02:53:44PM +0000, Peter Maydell wrote:
> > At some point in the last month a meson change landed, and now
> > when meson runs it complains:
> >
> > WARNING: Broken python installation detected. Python files installed
> > by Meson might not be found by python interpreter.
> > Any idea what meson is complaning about ?
>
> The source code emitting this warning message has a comment
> pointing to:
>
> https://github.com/mesonbuild/meson/issues/8739
>
> It seems that there is something broken about Python on Debian but
> can't say i especially understand the bug report discussion there.
Me neither. The warning is pretty unhelpful (in the sense that it
does not clearly describe what/where the problem is or how it might be
fixed) and seems mostly likely to cause our users who run Ubuntu or
Debian to come and complain at us about something that's not under
our control.
Also, Debian have been shipping Python for years and years and
years with nothing obviously being badly wrong with it.
thanks
-- PMM
prev parent reply other threads:[~2021-11-01 15:14 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-11-01 14:53 meson complains about "broken python installation" Peter Maydell
2021-11-01 15:06 ` Daniel P. Berrangé
2021-11-01 15:13 ` Peter Maydell [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=CAFEAcA8eND_knYS23YDyX6ZboXJxn-0FYiQ3kq2gAMot14ZkaA@mail.gmail.com \
--to=peter.maydell@linaro.org \
--cc=berrange@redhat.com \
--cc=pbonzini@redhat.com \
--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;
as well as URLs for NNTP newsgroup(s).