Re: [PATCH 6/6] meta: Do not update isar-apt during sbuild chroot prepare

[Anton Mikanovich <amikan@ilbers.de>]

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.

> Practically, users could just pull such packages whenever they build
> something in that custom schroot, but having to handle self-built
> packages differently than those coming from external repos is at least
> not intuitive.
>
> Jan
>

-- 
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/9e9b8292-2150-47e6-a035-4a948b8a4df4%40ilbers.de.