Re: [PATCH v7] dpkg: Restore support for replacing pre-installed packages in sbuild-chroot

[Anton Mikanovich <amikan@ilbers.de>]

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).
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.

-- 
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/df6de931-e8da-4a1e-bb84-85984303e01a%40ilbers.de.