From: "'Jan Kiszka' via isar-users" <isar-users@googlegroups.com>
To: Anton Mikanovich <amikan@ilbers.de>, isar-users@googlegroups.com
Subject: Re: [PATCH 6/6] meta: Do not update isar-apt during sbuild chroot prepare
Date: Mon, 3 Mar 2025 15:32:55 +0100 [thread overview]
Message-ID: <f8f31958-d62b-4d21-9376-1065733a7dc2@siemens.com> (raw)
In-Reply-To: <9e9b8292-2150-47e6-a035-4a948b8a4df4@ilbers.de>
On 03.03.25 11:13, Anton Mikanovich wrote:
> 21/02/2025 18:34, Jan Kiszka wrote:
>> On 21.02.25 16:48, Anton Mikanovich wrote:
>>> After moving to manual isar-apt update during package build in 0e846829
>>> there is no need in obtaining isar-apt package list during sbuild
>>> rootfs prepare. Moreover, it can results in out of sync between the
>>> data in /var/lib/apt/lists and local isar-apt copy of the recipe.
>>> In case of rebuilding the package already included into sbuild chroot
>>> this sync lost can raise 'File not found' issues with updated debs.
>> Why is the sync we do inside sbuild not curing this de-synchronization?
> That's a good question I was unable to answer: if /var/lib/apt/lists has an
> information about the package which not exists in the repo, apt still
> tries to
> install that package.
>>> Remove isar-apt update during sbuild chroot prepare and do it later
>>> for every package separately based on local isar-apt copy.
>> What about building a custom schroot that should have a self-built,
>> isar-apt-originated package included? Won't that fail now?
>
> If it is the case covered with hello-isar application - it is still
> working.
> Isar-apt is populated with libhello-dev because of fixed deps, then manual
> apt-get update will be performed on isar-apt only inside sbuild hook, so
> libhello-dev will be installed into schroot for hello-isar building.
>
But will the custom schroot already contain libhello-dev, or will
schroot simply install while setting up the build env for hello-isar?
I'm referring to SBUILD_CHROOT_PREINSTALL_EXTRA for self-built packages.
Jan
--
Siemens AG, Foundational Technologies
Linux Expert Center
--
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/f8f31958-d62b-4d21-9376-1065733a7dc2%40siemens.com.
next prev parent reply other threads:[~2025-03-03 14:33 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-02-21 15:48 [PATCH 0/6] Fix essentials rebuild and cover with CI Anton Mikanovich
2025-02-21 15:48 ` [PATCH 1/6] CI: Add API for checking package version in rootfs Anton Mikanovich
2025-02-21 15:48 ` [PATCH 2/6] CI: Add API for sbuild hook insertion Anton Mikanovich
2025-02-21 15:48 ` [PATCH 3/6] CI: Add sed as essential rebuild test package Anton Mikanovich
2025-02-21 15:48 ` [PATCH 4/6] CI: Add essential packages rebuild test case Anton Mikanovich
2025-02-21 15:48 ` [PATCH 5/6] CI: Fix getVars API on fast recalling Anton Mikanovich
2025-02-21 15:48 ` [PATCH 6/6] meta: Do not update isar-apt during sbuild chroot prepare Anton Mikanovich
2025-02-21 16:34 ` 'Jan Kiszka' via isar-users
2025-03-03 10:13 ` Anton Mikanovich
2025-03-03 14:32 ` 'Jan Kiszka' via isar-users [this message]
2025-03-03 15:16 ` Anton Mikanovich
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=f8f31958-d62b-4d21-9376-1065733a7dc2@siemens.com \
--to=isar-users@googlegroups.com \
--cc=amikan@ilbers.de \
--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