From: "'MOESSBAUER, Felix' via isar-users" <isar-users@googlegroups.com>
To: Zhihang Wei <wzh@ilbers.de>,
"isar-users@googlegroups.com" <isar-users@googlegroups.com>
Cc: "Kiszka, Jan" <jan.kiszka@siemens.com>
Subject: Re: [PATCH] testsuite: Add KFAIL to qemumipsel-bookworm
Date: Fri, 24 Jul 2026 09:33:38 +0000 [thread overview]
Message-ID: <6d581c3f0fc04a4a0d28b38cdd48538c1d8775e8.camel@siemens.com> (raw)
In-Reply-To: <16bc3c16-d3f3-45bf-8018-d33fa71b3075@ilbers.de>
On Fri, 2026-07-24 at 10:48 +0200, Zhihang Wei wrote:
> On 7/24/26 09:59, Zhihang Wei wrote:
> >
> > On 7/23/26 17:28, 'MOESSBAUER, Felix' via isar-users wrote:
> > > 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
> > >
> >
> > On my side this occurs consistently. It's not caused by recent changes. I
> > tested on the old master branch and the problem occurred there as well.
> >
> > Zhihang
> >
>
> I was just summarizing recent CI failures and found this error occurs
> with other targets as well, such as qemuarm64-bookworm and
> qemuamd64-bookworm, but only sporadically. On qemumipsel-bookworm the
> error occurs consistently.
The root-cause of this is the manually modeled dependency chain in
sbuild-chroot.inc around libgcc-<...> and libstd++-<...>. The
assumptions made there are not universally valid, especially not when
packages are taken from debian security (which explains the late
breakage). This was introduced by Jan to reduce the sbuild install
times in 2be866677 and d90f75bd00f. Reverting the changes fixes the
build.
Still I don't fully understand why this breaks non-deterministically.
Best regards,
Felix
>
> Zhihang
--
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/6d581c3f0fc04a4a0d28b38cdd48538c1d8775e8.camel%40siemens.com.
next prev parent reply other threads:[~2026-07-24 9:33 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
2026-07-24 7:59 ` Zhihang Wei
2026-07-24 8:48 ` Zhihang Wei
2026-07-24 9:33 ` 'MOESSBAUER, Felix' via isar-users [this message]
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=6d581c3f0fc04a4a0d28b38cdd48538c1d8775e8.camel@siemens.com \
--to=isar-users@googlegroups.com \
--cc=felix.moessbauer@siemens.com \
--cc=jan.kiszka@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