public inbox for isar-users@googlegroups.com
 help / color / mirror / Atom feed
From: Uladzimir Bely <ubely@ilbers.de>
To: isar-users <isar-users@googlegroups.com>
Cc: Jan Kiszka <jan.kiszka@siemens.com>
Subject: Re: Offline build broken with sbuild?
Date: Tue, 22 Nov 2022 15:15:32 +0300	[thread overview]
Message-ID: <6844674.9J7NaK4W3v@home> (raw)
In-Reply-To: <2639780.lGaqSPkdTl@home>

In the email from Monday, 21 November 2022 10:36:43 +03 user Uladzimir Bely 
wrote:
> 
> I'll try to check more things (e.g. Isar revision mentioned in the bug;
> complete image build, etc), but at the first glance sbuild-chroot-host looks
> to be cached OK, at least with the latest Isar.
>

So, I've got the following result for now:

- In Isar itself cached cross-build works well (while both HOST_DISTRO and 
DISTRO are equal). The only exception: raspberry targets, while DISTRO and 
HOST_DISTRO are different by nature.

- In meta-iot2050, cached cross-build doesn't work for both "sbuild" and "pre-
sbuild" cases. Evend "isar-bootstrap-host" task doesn't work for cached build.

I've applied the following patch for now and it at least fixed sbuild-chroot-
host task for cached build. Waiting for full build finished and will update 
you with the result.

diff --git a/meta/recipes-devtools/base-apt/base-apt.bb b/meta/recipes-
devtools/base-apt/base-apt.bb
index 506a28f..316960d 100644
--- a/meta/recipes-devtools/base-apt/base-apt.bb
+++ b/meta/recipes-devtools/base-apt/base-apt.bb
@@ -13,7 +13,9 @@ KEYFILES ?= ""
 BASE_REPO_FEATURES ?= ""
 
 populate_base_apt() {
-    find "${DEBDIR}"/"${DISTRO}" -name '*\.deb' | while read package; do
+    distro="${BASE_DISTRO}-${BASE_DISTRO_CODENAME}"
+
+    find "${DEBDIR}"/"${distro}" -name '*\.deb' | while read package; do
         # NOTE: due to packages stored by reprepro are not modified, we can
         # use search by filename to check if package is already in repo. In
         # addition, md5sums are compared to ensure that the package is the
@@ -38,7 +40,7 @@ populate_base_apt() {
             "${package}"
     done
 
-    find "${DEBSRCDIR}"/"${DISTRO}" -name '*\.dsc' | while read package; do
+    find "${DEBSRCDIR}"/"${distro}" -name '*\.dsc' | while read package; do
         repo_add_srcpackage "${REPO_BASE_DIR}"/"${BASE_DISTRO}" \
             "${REPO_BASE_DB_DIR}"/"${BASE_DISTRO}" \
             "${BASE_DISTRO_CODENAME}" \


-- 
Uladzimir Bely




  reply	other threads:[~2022-11-22 12:15 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-11-21  6:49 Jan Kiszka
2022-11-21  7:36 ` Uladzimir Bely
2022-11-22 12:15   ` Uladzimir Bely [this message]
2022-11-22 13:11     ` Jan Kiszka
2022-11-23 15:49       ` Jan Kiszka
2022-11-23 16:17         ` Jan Kiszka
2022-11-24  6:57           ` Uladzimir Bely
2022-11-24  7:32             ` Jan Kiszka

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=6844674.9J7NaK4W3v@home \
    --to=ubely@ilbers.de \
    --cc=isar-users@googlegroups.com \
    --cc=jan.kiszka@siemens.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