From: Thomas Huth <thuth@redhat.com>
To: "Alex Bennée" <alex.bennee@linaro.org>, qemu-devel@nongnu.org
Cc: "Michael Tokarev" <mjt@tls.msk.ru>,
"Philippe Mathieu-Daudé" <philmd@linaro.org>,
"Wainer dos Santos Moschetta" <wainersm@redhat.com>,
"Jiaxun Yang" <jiaxun.yang@flygoat.com>
Subject: Re: [PATCH] testing: bump mips64el cross to bookworm and allow to fail
Date: Wed, 25 Sep 2024 13:17:10 +0200 [thread overview]
Message-ID: <a3644805-e4ba-4cfb-a429-0604d7282f06@redhat.com> (raw)
In-Reply-To: <20240923081537.3846145-1-alex.bennee@linaro.org>
On 23/09/2024 10.15, Alex Bennée wrote:
> The mips64el cross setup is very broken for bullseye which has now
> entered LTS support so is unlikely to be fixed. While we still can't
> build the container for bookworm due to a single missing dependency
> that will hopefully get fixed in due course. For the sake of keeping
> the CI green we mark it as allow_fail for the time being.
>
> Signed-off-by: Alex Bennée <alex.bennee@linaro.org>
> Cc: Michael Tokarev <mjt@tls.msk.ru>
> ---
...
> @@ -143,6 +140,7 @@ RUN export DEBIAN_FRONTEND=noninteractive && \
> libvdeplug-dev:mips64el \
> libvirglrenderer-dev:mips64el \
> libvte-2.91-dev:mips64el \
> + libxdp-dev:mips64el \
> libzstd-dev:mips64el \
> nettle-dev:mips64el \
> systemtap-sdt-dev:mips64el \
We could also do a temporary manual hack and remove the problematic packages
from the list that cause the failure. I guess removing libdrm-dev:mips64el ,
libgtk-3-dev:mips64el and the SDL2 packages might help to avoid that the
mesa stuff gets installed (which causes the trouble)...
Of course this will be overwritten the next time someone runs lcitool again,
but with a little bit of luck, Debian already got fixed at that point in
time. What do you think?
Thomas
next prev parent reply other threads:[~2024-09-25 11:17 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-09-23 8:15 [PATCH] testing: bump mips64el cross to bookworm and allow to fail Alex Bennée
2024-09-25 11:17 ` Thomas Huth [this message]
2024-09-30 9:32 ` Alex Bennée
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=a3644805-e4ba-4cfb-a429-0604d7282f06@redhat.com \
--to=thuth@redhat.com \
--cc=alex.bennee@linaro.org \
--cc=jiaxun.yang@flygoat.com \
--cc=mjt@tls.msk.ru \
--cc=philmd@linaro.org \
--cc=qemu-devel@nongnu.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).