From: "'MOESSBAUER, Felix' via isar-users" <isar-users@googlegroups.com>
To: Zhihang Wei <wzh@ilbers.de>,
"isar-users@googlegroups.com" <isar-users@googlegroups.com>
Subject: Re: [PATCH] testsuite: Add KFAIL to qemumipsel-bookworm
Date: Thu, 23 Jul 2026 15:28:50 +0000 [thread overview]
Message-ID: <1dac0c701ef611288162c23759da06c28d5614d5.camel@siemens.com> (raw)
In-Reply-To: <20260723133314.1579323-1-wzh@ilbers.de>
On Thu, 2026-07-23 at 15:33 +0200, Zhihang Wei wrote:
> Currently the following error occurs when building qemumipsel-bookworm:
> ERROR: Task (mc:qemumipsel-bookworm:./build/../meta/recipes-devtools/sbuild-chroot/sbuild-chroot-host.bb:do_rootfs_install) failed with exit code '1'
> The task log shows:
> Broken libc6-dev:amd64 Depends on linux-libc-dev:amd64 < none @un pH >
> <snip>
> The following packages have unmet dependencies:
> libc6-dev : Depends: linux-libc-dev but it is not installable
> E: Unable to correct problems, you have held broken packages.
Hi, I noticed this as well, but on my side this is a sporadic issue.
I did not investigate this further, though.
Felix
--
You received this message because you are subscribed to the Google Groups "isar-users" group.
To unsubscribe from this group and stop receiving emails from it, send an email to isar-users+unsubscribe@googlegroups.com.
To view this discussion visit https://groups.google.com/d/msgid/isar-users/1dac0c701ef611288162c23759da06c28d5614d5.camel%40siemens.com.
next prev parent reply other threads:[~2026-07-23 15:29 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-07-23 13:33 Zhihang Wei
2026-07-23 15:28 ` 'MOESSBAUER, Felix' via isar-users [this message]
2026-07-24 7:59 ` Zhihang Wei
2026-07-24 8:48 ` Zhihang Wei
2026-07-24 9:33 ` 'MOESSBAUER, Felix' via isar-users
2026-07-24 12:05 ` 'MOESSBAUER, Felix' via isar-users
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=1dac0c701ef611288162c23759da06c28d5614d5.camel@siemens.com \
--to=isar-users@googlegroups.com \
--cc=felix.moessbauer@siemens.com \
--cc=wzh@ilbers.de \
/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