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: Mon, 21 Nov 2022 10:36:43 +0300 [thread overview]
Message-ID: <2639780.lGaqSPkdTl@home> (raw)
In-Reply-To: <9d111e65-99ac-52fe-eb30-1605facce23c@siemens.com>
In the email from Monday, 21 November 2022 09:49:00 +03 user Jan Kiszka wrote:
> Hi,
>
> seems like at least sbuild-chroot-host is not properly cached /wrt the
> additional Debian packages is pulls. Therefore, offline build fails.
> I've just confirmed this bug report:
>
> https://github.com/siemens/meta-iot2050/issues/382
>
> What could be missing?
>
> Jan
Just performed a quick test with the latest Isar 'next':
1. Run first build
```
bitbake mc:qemuarm64-bullseye:sbuild-chroot-host
```
2. Cleaned "tmp" directory
3. Added ISAR_USE_CACHED_BASE_REPO = "1" and BB_NO_NETWORK = "1"
4. To be sure, stopped network on the machine and run build again:
```
bitbake mc:qemuarm64-bullseye:sbuild-chroot-host
```
Repo "base-apt" was created and the build was OK.
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.
--
Uladzimir Bely
next prev parent reply other threads:[~2022-11-21 7:36 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 [this message]
2022-11-22 12:15 ` Uladzimir Bely
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=2639780.lGaqSPkdTl@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