RE: Migration to SCHROOT

["Arjunan, Srinu" <srinuvasan.a@siemens.com>]

Hi Jan,


                 Thanks for the suggestion, let me check this one is fitting for my requirements, and meanwhile I will do some POC on vanilla ISAR too.

Many thanks,
Srinuvasan.A

-----Original Message-----
From: Kiszka, Jan (T CED) <jan.kiszka@siemens.com> 
Sent: 07 November 2023 18:56
To: Arjunan, Srinu (DI CTO FDS CES LX PBU RSOL) <srinuvasan.a@siemens.com>; Anton Mikanovich <amikan@ilbers.de>; isar-users <isar-users@googlegroups.com>
Subject: Re: Migration to SCHROOT

On 07.11.23 13:41, 'Arjunan, Srinu' via isar-users wrote:
> Hi Anton,
> 
> Thanks for the update, I understood this one, but in my case I need to install the custom packages in persistent sbuildchroot , because this packages details referred multiple places in different classes for some processing meta data before image creation.

Have a look at SBUILD_CHROOT_PREINSTALL_EXTRA, but maybe not to override for everyone. Here is an example to create an extended SBUILD_FLAVOR:

meta-isar/recipes-app/hello-isar/hello-isar.bb
meta-isar/recipes-app/libhello/libhello.bb
meta-isar/recipes-devtools/sbuild-chroot/sbuild-chroot-host-db2m.bb
meta-isar/recipes-devtools/sbuild-chroot/sbuild-chroot-target-db2m.bb

> 
> I don't' want the session kind of approach at least for achieving the above criteria, hence I used the old buildchroot style of configuration like "configure_isar_apt" in sbuildchroot.
> 
> In this way I can able to install few custom packages in sbuildchroot, 
> most of the things are working fine, but in some packages am facing build failure Because sbuild automatically do the apt-get upgrade , this will upgrade the base-files packages already installed in buildchroot.

Only if there are living replacements in isar-apt. We do not update base-apt packages.

> When we bootstrap we normally do the upgrade and get the latest version of the packages installed in the chroot, this can be carry over to the buildchroot, again I don't want to do the apt-get upgrade, but sbuild does by default.
> 
> I used --no-apt-upgrade , but this one sporadically throws the dpkg error as I mentioned in the below thread, but some the clean build works fine.
> 
> Can you please suggest how to disable the schroot upgrade step in sbuild like how we did --no-apt-update previously in sbuild?
> 

I suspect there are additional, local changes on your side involved causing the issues. If you don't think so, please demonstrate the
issue(s) with vanilla Isar.

Jan

--
Siemens AG, Technology
Linux Expert Center