public inbox for isar-users@googlegroups.com
 help / color / mirror / Atom feed
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 12:59:17 +0200	[thread overview]
Message-ID: <06ec58b8-1322-475b-9849-ce379416bef0@ilbers.de> (raw)
In-Reply-To: <321e7729-5785-47d3-bfd5-a5c875010945@siemens.com>

09/02/2025 11:19, Jan Kiszka wrote:
> On 07.02.25 16:57, Anton Mikanovich wrote:
>> Hello Jan,
>>
>> It looks like this change creates one more issue.
>> Here are simple steps to reproduce:
>>
>> Prepare test recipe:
>>
>> $ cat meta-isar/recipes-app/hello/pcre2.bb
>> inherit dpkg
>>
>> SRC_URI = "apt://pcre2"
>>
>> CHANGELOG_V = "<orig-version>+isar"
>>
>> do_prepare_build() {
>>          deb_add_changelog
>> }
>>
>> Go to kas shell (qemuamd64 bookworm):
>>
>> $ kas-container shell
>>
>> Perform those steps:
>>
>> builder@b5422048da4a:/build$ bitbake -c local_isarapt cowsay
>> builder@b5422048da4a:/build$ bitbake -c build pcre2
>> builder@b5422048da4a:/build$ bitbake -c cleansstate sbuild-chroot-target
>> builder@b5422048da4a:/build$ bitbake -c build cowsay
> The outcome is expected: local_isarapt is incorrectly run prior to
> deploy_deb of pcre2. This won't happen during a normal build when cowsay
> DEPENDS on pcre2, though, because of do_local_isarapt[deptask] =
> "do_deploy_deb".
>
> Now, if you used ISAR_REBUILD_ESSENTIAL_PKGS in your actual scenario, we
> do have problem because your patch 21a05608d85b forgot to adjust
> meta/classes/essential.bbclass. I'll send a fix.
>
> Jan
>
After some testing with ISAR_REBUILD_ESSENTIAL_PKGS="pcre2" the issue is 
still
there. Steps to reproduce (clean build inside kas, 
ISAR_REBUILD_ESSENTIAL_PKGS
is set to "pcre2"):

builder@a1f979144422:/build$ bitbake -c build pcre2
builder@a1f979144422:/build$ echo -e "\npython 
do_rootfs_install:append() {\n\n}" >> /work/meta/classes/rootfs.bbclass
builder@a1f979144422:/build$ bitbake -c build pcre2

So the question is the same: which use case does your original commit 
suppose
to fix?

-- 
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/06ec58b8-1322-475b-9849-ce379416bef0%40ilbers.de.

  parent reply	other threads:[~2025-02-10 10:59 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 [this message]
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
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=06ec58b8-1322-475b-9849-ce379416bef0@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