From: Thomas Huth <thuth@redhat.com>
To: "Philippe Mathieu-Daudé" <philmd@linaro.org>, qemu-devel@nongnu.org
Cc: "Ryo ONODERA" <ryoon@netbsd.org>,
"Wainer dos Santos Moschetta" <wainersm@redhat.com>,
"Kyle Evans" <kevans@freebsd.org>,
"Alex Bennée" <alex.bennee@linaro.org>,
"Beraldo Leal" <bleal@redhat.com>,
"Reinoud Zandijk" <reinoud@netbsd.org>,
"Warner Losh" <imp@bsdimp.com>
Subject: Re: [PATCH-for-8.2] tests/vm/netbsd: Use Python v3.11
Date: Thu, 9 Nov 2023 18:06:45 +0100 [thread overview]
Message-ID: <e456a120-d12f-4377-bcf0-81e070120643@redhat.com> (raw)
In-Reply-To: <20231109150900.91186-1-philmd@linaro.org>
On 09/11/2023 16.09, Philippe Mathieu-Daudé wrote:
> We requiere the 'ninja-build', which depends on 'python311':
>
> $ pkgin show-deps ninja-build
> direct dependencies for ninja-build-1.11.1nb1
> python311>=3.11.0
>
> So we end up installing both Python v3.10 and v3.11:
>
> [31/76] installing python311-3.11.5...
> [54/76] installing python310-3.10.13...
> [74/76] installing py310-expat-3.10.13nb1...
>
> Then the build system picks Python v3.11, and doesn't find
> py-expat because we only installed the 3.10 version:
>
> python determined to be '/usr/pkg/bin/python3.11'
> python version: Python 3.11.5
>
> *** Ouch! ***
...
> diff --git a/tests/vm/netbsd b/tests/vm/netbsd
> index 40b27a3469..649fcad353 100755
> --- a/tests/vm/netbsd
> +++ b/tests/vm/netbsd
> @@ -30,8 +30,8 @@ class NetBSDVM(basevm.BaseVM):
> "git-base",
> "pkgconf",
> "xz",
> - "python310",
> - "py310-expat",
> + "python311",
> + "py311-expat",
> "ninja-build",
>
> # gnu tools
Indeed, this seems to be required now!
Tested-by: Thomas Huth <thuth@redhat.com>
prev parent reply other threads:[~2023-11-09 17:07 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-11-09 15:09 [PATCH-for-8.2] tests/vm/netbsd: Use Python v3.11 Philippe Mathieu-Daudé
2023-11-09 17:06 ` 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=e456a120-d12f-4377-bcf0-81e070120643@redhat.com \
--to=thuth@redhat.com \
--cc=alex.bennee@linaro.org \
--cc=bleal@redhat.com \
--cc=imp@bsdimp.com \
--cc=kevans@freebsd.org \
--cc=philmd@linaro.org \
--cc=qemu-devel@nongnu.org \
--cc=reinoud@netbsd.org \
--cc=ryoon@netbsd.org \
--cc=wainersm@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).