public inbox for isar-users@googlegroups.com
 help / color / mirror / Atom feed
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 0/3] Fixes for BASE_DISTRO
Date: Tue, 10 Nov 2026 11:42:17 +0000	[thread overview]
Message-ID: <78a38212a95e86d9af925a2d86e0ad8a0f463bb4.camel@siemens.com> (raw)
In-Reply-To: <1a416d6c-416b-4d5a-854d-c84c44bfc71f@ilbers.de>

On Fri, 2026-11-06 at 17:00 +0100, Zhihang Wei wrote:
> On 11/6/26 10:59, Moessbauer, Felix wrote:
> > On Wed, 2026-10-21 at 12:25 +0200, Felix Moessbauer wrote:
> > > The raspi builds expose issues related to the handling of the BASE_DISTRO,
> > > as it is not "debian" but "raspios64". With the upcoming changes
> > > in "More build time reductions", these bugs are surfaced.
> > > 
> > > In the CI, the bugs probably have partially been hidden by leftover
> > > artifacts from previous test cases.
> > Hi, are there any news on this? Is there anything needed from my side
> > to get this merged?
> > 
> > Felix
> > 
> 
> Hi Felix,
> 
> This patch set itself is fine. But when testing it with "More build
> time reductions", there are some issues.

Ok, but then please merge this first and I'll take care of the "More
build time reductions ..." cleanup afterwards.

> 
> On fast testsuite, CompatTest.test_compat_recipe fails with:
> ERROR: mc:qemuarm64-trixie:libhello-compat-0.3-f4a5669-r0 do_dpkg_build: 
> ExecutionError('/build/isar_wzh_devel_2b_fast/79/build/tmp/work/debian-trixie-arm64/libhello-compat/0.3-f4a5669-r0/temp/run.dpkg_runbuild.3920233', 
> 1, None, None)

Thanks, I'll look into it.

Felix

> 
> DEBUG: Executing python function sstate_task_prefunc
> DEBUG: Python function sstate_task_prefunc finished
> DEBUG: Executing python function do_dpkg_build
> DEBUG: Executing shell function dpkg_chroot_prepare
> Creating 
> /etc/schroot/chroot.d/isar-jenkins-d397b874-809d-4d27-a3b6-051089ce40ed-3920233
> DEBUG: Shell function dpkg_chroot_prepare finished
> DEBUG: Executing shell function dpkg_runbuild
> dpkg-parsechangelog: error: cannot open file 
> /build/isar_wzh_devel_2b_fast/79/build/debian/changelog: No such file or 
> directory
> E: Could not parse /build/isar_wzh_devel_2b_fast/79/build/debian/changelog:
> WARNING: exit code 1 from a shell command.
> DEBUG: Executing shell function dpkg_chroot_finalize
> Removing 
> /etc/schroot/isar-jenkins-d397b874-809d-4d27-a3b6-051089ce40ed-3920233
> Removing 
> /etc/schroot/chroot.d/isar-jenkins-d397b874-809d-4d27-a3b6-051089ce40ed-3920233
> DEBUG: Shell function dpkg_chroot_finalize finished
> DEBUG: Python function do_dpkg_build finished
> 
> It attempted to find the changelog directly under build/debian, it's 
> definitely not right.
> 
> But running CompatTest.test_compat_recipe alone passes. In the fast suite,
> DevTest and LocaleTest run before CompatTest, so one of the earlier builds
> probably affects it. I’ve been trying to find which target affects it, but
> haven’t found it yet.
> 
> Zhihang
> 
> > > Best regards,
> > > Felix Moessbauer
> > > 
> > > Felix Moessbauer (3):
> > >    crossvars: provide the base distro of the selected sbuild chroot
> > >    apt-fetcher: cache sources under the chroot's base distro
> > >    bootstrap: point cached deb-src at the bootstrapped base distro
> > > 
> > >   meta/classes-recipe/crossvars.bbclass                 | 8 ++++++++
> > >   meta/classes-recipe/dpkg.bbclass                      | 5 +----
> > >   meta/lib/aptsrc_fetcher.py                            | 4 +++-
> > >   meta/recipes-core/isar-mmdebstrap/isar-mmdebstrap.inc | 2 +-
> > >   4 files changed, 13 insertions(+), 6 deletions(-)
> > > 
> > > -- 
> > > 2.55.0

-- 
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/78a38212a95e86d9af925a2d86e0ad8a0f463bb4.camel%40siemens.com.

  reply	other threads:[~2026-11-10 11:42 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-10-21 10:25 'Felix Moessbauer' via isar-users
2026-10-21 10:25 ` [PATCH 1/3] crossvars: provide the base distro of the selected sbuild chroot 'Felix Moessbauer' via isar-users
2026-10-21 10:25 ` [PATCH 2/3] apt-fetcher: cache sources under the chroot's base distro 'Felix Moessbauer' via isar-users
2026-10-21 10:25 ` [PATCH 3/3] bootstrap: point cached deb-src at the bootstrapped " 'Felix Moessbauer' via isar-users
2026-11-06  9:59 ` [PATCH 0/3] Fixes for BASE_DISTRO 'Moessbauer, Felix' via isar-users
2026-11-06 16:00   ` Zhihang Wei
2026-11-10 11:42     ` 'Moessbauer, Felix' via isar-users [this message]
2026-11-11 16:05 ` Zhihang Wei

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=78a38212a95e86d9af925a2d86e0ad8a0f463bb4.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