public inbox for isar-users@googlegroups.com
 help / color / mirror / Atom feed
From: "'Moessbauer, Felix' via isar-users" <isar-users@googlegroups.com>
To: "isar-users@googlegroups.com" <isar-users@googlegroups.com>
Cc: "wzh@ilbers.de" <wzh@ilbers.de>
Subject: Re: [PATCH 0/3] Fixes for BASE_DISTRO
Date: Fri, 6 Nov 2026 09:59:08 +0000	[thread overview]
Message-ID: <d6536e6827d615a09ec251fcc10c0559772aecd3.camel@siemens.com> (raw)
In-Reply-To: <20261021102544.3614772-1-felix.moessbauer@siemens.com>

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

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

  parent reply	other threads:[~2026-11-06  9:59 UTC|newest]

Thread overview: 6+ 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 ` 'Moessbauer, Felix' via isar-users [this message]
2026-11-06 16:00   ` [PATCH 0/3] Fixes for BASE_DISTRO 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=d6536e6827d615a09ec251fcc10c0559772aecd3.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