From: Anton Mikanovich <amikan@ilbers.de>
To: Jan Kiszka <jan.kiszka@siemens.com>, isar-users@googlegroups.com
Cc: Uladzimir Bely <ubely@ilbers.de>, Baurzhan Ismagulov <ibr@ilbers.de>
Subject: Re: [PATCH v7] dpkg: Restore support for replacing pre-installed packages in sbuild-chroot
Date: Mon, 10 Feb 2025 18:09:55 +0200 [thread overview]
Message-ID: <215cc575-fa4f-45e6-8511-eff4254a4383@ilbers.de> (raw)
In-Reply-To: <be2f0b40-ca38-4bd0-ba14-9fad04751796@siemens.com>
10/02/2025 14:02, Jan Kiszka wrote:
> Invalid partial rebuild scenario: If you are enforcing a rebuild of the
> sbuild-chroot, you also need to wipe all ISAR_REBUILD_ESSENTIAL_PKGS
> first. Can you explain what you actually did to trigger this?
>
> If you sit down for a moment, it should become clear what makes
> rebuilding complex when essential packages are replaced: They can become
> part of their own sbuild-chroot.
>
> Simply excluding isar-apt from the sbuild-chroots of essential packages
> could help - but only as long as we are not rebuilding a dependency
> chain of multiple packages. Granted, the latter is even less likely to
> happen than already having to rebuild essential packages. We are going
> down the rabbit hole of distro boot strapping here...
>
> Jan
>
Ok, it looks like I've found the case that was fixed: If package A (already
installed in sbuild-chroot) gets rebuilt with an updated version, package B
depends on any version of A (not just =new version like in my case), when B is
built, apt would keep the old version of A and not pull the newly built one.
The issues were triggered downstream after updating Isar version. I've changed
a bbclass and bitbake has failed. As a user, I'd like to be able to perform
rebuilds without wiping packages.
I'll work on a testcase and a fix for this issue.
--
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/215cc575-fa4f-45e6-8511-eff4254a4383%40ilbers.de.
next prev parent reply other threads:[~2025-02-10 16:10 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-01-27 7:42 Uladzimir Bely
2024-01-29 7:59 ` Jan Kiszka
2025-02-07 15:57 ` Anton Mikanovich
2025-02-09 9:19 ` 'Jan Kiszka' via isar-users
2025-02-10 7:47 ` Anton Mikanovich
2025-02-10 7:49 ` 'Jan Kiszka' via isar-users
2025-02-10 10:59 ` Anton Mikanovich
2025-02-10 11:13 ` 'Jan Kiszka' via isar-users
2025-02-10 11:34 ` Anton Mikanovich
2025-02-10 11:40 ` 'Jan Kiszka' via isar-users
2025-02-10 12:02 ` 'Jan Kiszka' via isar-users
2025-02-10 16:09 ` Anton Mikanovich [this message]
2024-01-29 10:48 ` Uladzimir Bely
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=215cc575-fa4f-45e6-8511-eff4254a4383@ilbers.de \
--to=amikan@ilbers.de \
--cc=ibr@ilbers.de \
--cc=isar-users@googlegroups.com \
--cc=jan.kiszka@siemens.com \
--cc=ubely@ilbers.de \
/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