From: "Daniel P. Berrangé" <berrange@redhat.com>
To: Richard Henderson <richard.henderson@linaro.org>
Cc: qemu-devel <qemu-devel@nongnu.org>,
"Alex Bennée" <alex.bennee@linaro.org>,
"Thomas Huth" <thuth@redhat.com>,
"Wainer dos Santos Moschetta" <wainersm@redhat.com>,
"Beraldo Leal" <bleal@redhat.com>
Subject: Re: lcitool update required
Date: Tue, 12 Jul 2022 09:22:25 +0100 [thread overview]
Message-ID: <Ys0vQXxWE2aXDkK0@redhat.com> (raw)
In-Reply-To: <7cd15bdb-578e-4d28-6c8b-a101c9f8f4e6@linaro.org>
On Tue, Jul 12, 2022 at 12:31:35PM +0530, Richard Henderson wrote:
> Hi guys,
>
> Cirrus FreeBSD builds are now broken, because we're trying to install py38-*
> packages that no longer exist. There was, yesterday, an update to lcitool
> that addresses this. However in the meantime there has been a major change
> to the way lcitool is packaged such that we cannot merely update the
> submodule and 'make lcitool-rebuild'.
Oh the source files were slightly re-arranged to make it look more like
a normal python app, but functionally it should still be the same.
> I'm planning to edit the cirrus ci files by hand for the moment, in an
> effort to re-green the ci, but please update our automation.
I'll send an update.
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 :|
prev parent reply other threads:[~2022-07-12 8:41 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-07-12 7:01 lcitool update required Richard Henderson
2022-07-12 8:22 ` Daniel P. Berrangé [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=Ys0vQXxWE2aXDkK0@redhat.com \
--to=berrange@redhat.com \
--cc=alex.bennee@linaro.org \
--cc=bleal@redhat.com \
--cc=qemu-devel@nongnu.org \
--cc=richard.henderson@linaro.org \
--cc=thuth@redhat.com \
--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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.