From: Thomas Huth <thuth@redhat.com>
To: Richard Henderson <richard.henderson@linaro.org>,
qemu-devel <qemu-devel@nongnu.org>
Cc: "Alex Bennée" <alex.bennee@linaro.org>,
"Warner Losh" <imp@bsdimp.com>, "Ed Maste" <emaste@freebsd.org>,
"Li-Wen Hsu" <lwhsu@freebsd.org>
Subject: Re: FreeBSD update required for CI?
Date: Tue, 16 Jul 2024 08:38:28 +0200 [thread overview]
Message-ID: <f09b78e1-383a-4fce-8e19-45e9240d245f@redhat.com> (raw)
In-Reply-To: <63699dab-42d9-45ca-932f-acd6df688b6e@linaro.org>
On 16/07/2024 01.00, Richard Henderson wrote:
> Hi guys,
>
> CI currently failing FreeBSD:
>
> https://gitlab.com/qemu-project/qemu/-/jobs/7347517439
>
>> pkg: No packages available to install matching 'py39-pillow' have been
>> found in the repositories
>> pkg: No packages available to install matching 'py39-pip' have been found
>> in the repositories
>> pkg: No packages available to install matching 'py39-sphinx' have been
>> found in the repositories
>> pkg: No packages available to install matching 'py39-sphinx_rtd_theme'
>> have been found in the repositories
>> pkg: No packages available to install matching 'py39-yaml' have been found
>> in the repositories
>
> Has FreeBSD ports updated to something beyond python 3.9, and we need an
> update to match?
Yes, we discussed it in IRC yesterday: Python has been updated there, we
need to update lcitool to the latest version to get the fix for it. Alex is
planning to provide a patch.
Thomas
prev parent reply other threads:[~2024-07-16 6:39 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-07-15 23:00 FreeBSD update required for CI? Richard Henderson
2024-07-16 2:15 ` Li-Wen Hsu
2024-07-16 6:38 ` 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=f09b78e1-383a-4fce-8e19-45e9240d245f@redhat.com \
--to=thuth@redhat.com \
--cc=alex.bennee@linaro.org \
--cc=emaste@freebsd.org \
--cc=imp@bsdimp.com \
--cc=lwhsu@freebsd.org \
--cc=qemu-devel@nongnu.org \
--cc=richard.henderson@linaro.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).