public inbox for isar-users@googlegroups.com
 help / color / mirror / Atom feed
From: Jan Kiszka <jan.kiszka@siemens.com>
To: "Hombourger,
	Cedric (DI SW CAS ES LI)" <cedric.hombourger@siemens.com>,
	"Schmidt, Adriaan (T CED SES-DE)" <adriaan.schmidt@siemens.com>,
	"ubely@ilbers.de" <ubely@ilbers.de>
Cc: "isar-users@googlegroups.com" <isar-users@googlegroups.com>
Subject: Re: ISAR_REBUILD_ESSENTIAL_PKGS - upgrade packages present in isar-bootstrap
Date: Thu, 12 Oct 2023 07:01:08 +0200	[thread overview]
Message-ID: <30ee70af-057f-489c-8caa-febf9169ba6d@siemens.com> (raw)
In-Reply-To: <acb86030-0fe7-4307-bb6a-31723645a8f5@siemens.com>

On 11.10.23 23:00, Hombourger, Cedric (DI SW CAS ES LI) wrote:
> On 11/10/2023 10:27, Jan Kiszka wrote:
>> On 11.10.23 09:05, 'cedric.hombourger@siemens.com' via isar-users wrote:
>>> Hello Adriaan, Uladzimir,
>>>
>>> ISAR_REBUILD_ESSENTIAL_PKGS (as I understand it) injects dependencies to
>>> all non-essential recipes to make sure such packages are built first.
>>>
>>> Wouldn't we also need to upgrade them when we bootstrap the image?
>>>
>>> For example, if my layer ships a customized recipe for the base-files
>>> package, we would want my custom version to be in the image, not Debian's.
>>>
>>> I can prepare an example to support the discussion if needed.
>> This used to be ensured by performing an update/upgrade for all packages
>> coming from isar-apt. Can you demonstrate that this is no longer the case?
> 
> Yes that's what I was hoping. I don't know if I missing something 
> obvious. Here's a (public) git repo that may be used to demonstrate the 
> problem: https://github.com/chombourger/test-isar-essential-package
> 
> I used the following grep command to check which version of my 
> customized base-files package ended-up in the image:
> 
> grep base-files 
> build/tmp/deploy/images/qemuamd64/isar-image-base-debian-bookworm-qemuamd64.manifest
> 
> I noticed that an explicit IMAGE_PREINSTALL:append = " base-files" 
> caused the version to be upgraded. Is that expected? Should we make such 
> a suggestion in the documentation?

Yeah, right, that is still needed. I wonder if we should auto-upgrade
the schroots when ISAR_REBUILD_ESSENTIAL_PKGS is non-empty.

> 
> I should also note that ISAR_REBUILD_ESSENTIAL_PKGS does not seem to add 
> dependencies between image recipes and essential packages (I had to add 
> base-files to DEPENDS to get it built)

That should work: essential.bbclass is inherited by image.bbclass, and
it adds dependencies to do_install_rootfs.

Jan

-- 
Siemens AG, Technology
Linux Expert Center


      reply	other threads:[~2023-10-12  5:01 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-10-11  7:05 cedric.hombourger
2023-10-11  8:27 ` Jan Kiszka
2023-10-11 21:00   ` cedric.hombourger
2023-10-12  5:01     ` Jan Kiszka [this message]

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=30ee70af-057f-489c-8caa-febf9169ba6d@siemens.com \
    --to=jan.kiszka@siemens.com \
    --cc=adriaan.schmidt@siemens.com \
    --cc=cedric.hombourger@siemens.com \
    --cc=isar-users@googlegroups.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