From: "Philippe Mathieu-Daudé" <philmd@linaro.org>
To: "Thomas Huth" <thuth@redhat.com>,
"Alex Bennée" <alex.bennee@linaro.org>,
"Peter Maydell" <peter.maydell@linaro.org>,
qemu-devel@nongnu.org
Cc: "Michael Tokarev" <mjt@tls.msk.ru>,
"Daniel P . Berrangé" <berrange@redhat.com>
Subject: Re: [PATCH v5] testing: bump mips64el cross to bookworm and fix package list
Date: Thu, 3 Oct 2024 17:42:59 +0200 [thread overview]
Message-ID: <947533e7-ddc4-4242-887b-3d6bde2c7a84@linaro.org> (raw)
In-Reply-To: <20241002080333.127172-1-thuth@redhat.com>
On 2/10/24 10:03, Thomas Huth wrote:
> From: Alex Bennée <alex.bennee@linaro.org>
>
> 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 with all packages 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 disable the problematic packages
> via the lcitool's mappings.yml file.
>
> See also: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1081535
>
> Signed-off-by: Alex Bennée <alex.bennee@linaro.org>
> [thuth: Disable the problematic packages via lcitool's mappings.yml]
> Signed-off-by: Thomas Huth <thuth@redhat.com>
> ---
> v5: Adjust the patch subject
>
> .../dockerfiles/debian-mips64el-cross.docker | 18 +++----------
> tests/lcitool/mappings.yml | 26 +++++++++++++++++++
> tests/lcitool/refresh | 2 +-
> 3 files changed, 31 insertions(+), 15 deletions(-)
Acked-by: Philippe Mathieu-Daudé <philmd@linaro.org>
prev parent reply other threads:[~2024-10-03 15:55 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-10-02 8:03 [PATCH v5] testing: bump mips64el cross to bookworm and fix package list Thomas Huth
2024-10-02 8:06 ` Daniel P. Berrangé
2024-10-03 15:42 ` Philippe Mathieu-Daudé [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=947533e7-ddc4-4242-887b-3d6bde2c7a84@linaro.org \
--to=philmd@linaro.org \
--cc=alex.bennee@linaro.org \
--cc=berrange@redhat.com \
--cc=mjt@tls.msk.ru \
--cc=peter.maydell@linaro.org \
--cc=qemu-devel@nongnu.org \
--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).