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
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:40:36 +0100	[thread overview]
Message-ID: <f2b3f60c-d40c-4c7c-8d7b-2680116f2428@siemens.com> (raw)
In-Reply-To: <df6de931-e8da-4a1e-bb84-85984303e01a@ilbers.de>

On 10.02.25 12:34, Anton Mikanovich wrote:
> 10/02/2025 13:13, Jan Kiszka wrote:
>> On 10.02.25 11:59, Anton Mikanovich wrote:
>>> 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
>>>
>> Let me try. Maybe we have more regressions piled up since the patch was
>> merged.
> The same issue can be easily reproduced on 0e846829 itself.
> And it was ok on previous commit (c44c088c).
>>> So the question is the same: which use case does your original commit
>>> suppose
>>> to fix?
>> A) the one from above
>> B) when you are rebuilding some non-essential package that happens to be
>>     in the sbuild-chroot already
>>
>> Jan
>>
> As I've already said both downgrade and upgrade cases are ok on the
> latest next
> with reverted 0e846829. And they were also ok on c44c088c (previous
> commit).

Without 0e846829, packages that are already in the sbuild-chroot are not
updated. That is what the patch fixes. If things apparently "work", then
you are not using the self-built package. Please read my length commit
message to understand the issue better.

Jan

> Are there any opensource downstream effected?
> I just want to make sure that my next fix for this pcre2 issue will not
> cause
> any more regressions.
> 

-- 
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/f2b3f60c-d40c-4c7c-8d7b-2680116f2428%40siemens.com.

  reply	other threads:[~2025-02-10 11:40 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 [this message]
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=f2b3f60c-d40c-4c7c-8d7b-2680116f2428@siemens.com \
    --to=isar-users@googlegroups.com \
    --cc=amikan@ilbers.de \
    --cc=ibr@ilbers.de \
    --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