From: "Daniel P. Berrangé" <berrange@redhat.com>
To: Thomas Huth <thuth@redhat.com>
Cc: QEMU Developers <qemu-devel@nongnu.org>,
Stefan Hajnoczi <stefanha@redhat.com>,
Brad Smith <brad@comstyle.com>, John Snow <jsnow@redhat.com>
Subject: Re: QEMU's FreeBSD 13 CI job is failing
Date: Tue, 20 Sep 2022 09:21:36 +0100 [thread overview]
Message-ID: <Yyl4EO0L5h02HOLN@redhat.com> (raw)
In-Reply-To: <b403c8e4-3788-7ba1-a038-3a71fa0bc7c6@redhat.com>
On Tue, Sep 20, 2022 at 08:44:27AM +0200, Thomas Huth wrote:
>
> Seen here for example:
>
> https://gitlab.com/qemu-project/qemu/-/jobs/3050165356#L2543
>
> ld-elf.so.1: /lib/libc.so.7: version FBSD_1.7 required by
> /usr/local/lib/libpython3.9.so.1.0 not found
> ERROR: Cannot use '/usr/local/bin/python3', Python >= 3.6 is required.
>
> ... looks like the Python binary is not working anymore? Does anybody know
> what happened here?
FreeBSD ports is only guaranteed to work with latest minor release
base image. The python binary recently started relying on symbols
in the 13.1 base image, and we're using 13.0.
I updated lcitool last week to pick 13.1, so we just need a refresh
on the QEMU side to pick this up.
With regards,
Daniel
--
|: https://berrange.com -o- https://www.flickr.com/photos/dberrange :|
|: https://libvirt.org -o- https://fstop138.berrange.com :|
|: https://entangle-photo.org -o- https://www.instagram.com/dberrange :|
next prev parent reply other threads:[~2022-09-20 9:27 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-09-20 6:44 QEMU's FreeBSD 13 CI job is failing Thomas Huth
2022-09-20 8:21 ` Daniel P. Berrangé [this message]
2022-09-20 8:23 ` Thomas Huth
2022-09-20 8:28 ` Daniel P. Berrangé
2022-09-20 20:21 ` Warner Losh
2022-09-21 7:13 ` Daniel P. Berrangé
2022-09-21 14:32 ` Warner Losh
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=Yyl4EO0L5h02HOLN@redhat.com \
--to=berrange@redhat.com \
--cc=brad@comstyle.com \
--cc=jsnow@redhat.com \
--cc=qemu-devel@nongnu.org \
--cc=stefanha@redhat.com \
--cc=thuth@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).