public inbox for isar-users@googlegroups.com
 help / color / mirror / Atom feed
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: Fri, 21 Feb 2025 17:34:30 +0100	[thread overview]
Message-ID: <7632446b-0eab-406c-be91-ccabcc4c4711@siemens.com> (raw)
In-Reply-To: <20250221154843.515037-7-amikan@ilbers.de>

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?

> 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?

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

-- 
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/7632446b-0eab-406c-be91-ccabcc4c4711%40siemens.com.

  reply	other threads:[~2025-02-21 16:34 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 [this message]
2025-03-03 10:13     ` Anton Mikanovich
2025-03-03 14:32       ` 'Jan Kiszka' via isar-users
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=7632446b-0eab-406c-be91-ccabcc4c4711@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