From: Li-Wen Hsu <lwhsu@freebsd.org>
To: Richard Henderson <richard.henderson@linaro.org>
Cc: qemu-devel <qemu-devel@nongnu.org>,
"Alex Bennée" <alex.bennee@linaro.org>,
"Warner Losh" <imp@bsdimp.com>, "Ed Maste" <emaste@freebsd.org>
Subject: Re: FreeBSD update required for CI?
Date: Tue, 16 Jul 2024 10:15:42 +0800 [thread overview]
Message-ID: <CAKBkRUzf1ZWahU3WrTxfM_fHPpxVBMC=YcjHu+evKB5PWdQGaQ@mail.gmail.com> (raw)
In-Reply-To: <63699dab-42d9-45ca-932f-acd6df688b6e@linaro.org>
[-- Attachment #1: Type: text/plain, Size: 1117 bytes --]
On Tue, Jul 16, 2024 at 7:01 AM Richard Henderson <
richard.henderson@linaro.org> 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?
>
Oh yes, the default python version has been changed to 3.11 so the `py39-`
prefix of the package name should be also changed to `py311-`
Where are those packages name listed? I can check if it is possible to
change to use some more deterministic names.
Best,
Li-Wen
[-- Attachment #2: Type: text/html, Size: 1625 bytes --]
next prev parent reply other threads:[~2024-07-16 2:17 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 [this message]
2024-07-16 6:38 ` Thomas Huth
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='CAKBkRUzf1ZWahU3WrTxfM_fHPpxVBMC=YcjHu+evKB5PWdQGaQ@mail.gmail.com' \
--to=lwhsu@freebsd.org \
--cc=alex.bennee@linaro.org \
--cc=emaste@freebsd.org \
--cc=imp@bsdimp.com \
--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).