public inbox for isar-users@googlegroups.com
 help / color / mirror / Atom feed
From: Jan Kiszka <jan.kiszka@siemens.com>
To: "Arjunan, Srinu" <srinuvasan.a@siemens.com>,
	Anton Mikanovich <amikan@ilbers.de>,
	isar-users <isar-users@googlegroups.com>
Subject: Re: Migration to SCHROOT
Date: Tue, 7 Nov 2023 14:25:39 +0100	[thread overview]
Message-ID: <cc1a8c80-8cde-4843-a4f8-275811c5b5ec@siemens.com> (raw)
In-Reply-To: <PUZPR06MB5747F003DE798732C0907D6188A9A@PUZPR06MB5747.apcprd06.prod.outlook.com>

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


  reply	other threads:[~2023-11-07 13:25 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-11-07  9:36 srinu
2023-11-07 11:20 ` Anton Mikanovich
2023-11-07 12:41   ` Arjunan, Srinu
2023-11-07 13:25     ` Jan Kiszka [this message]
2023-11-08  5:21       ` Arjunan, Srinu

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=cc1a8c80-8cde-4843-a4f8-275811c5b5ec@siemens.com \
    --to=jan.kiszka@siemens.com \
    --cc=amikan@ilbers.de \
    --cc=isar-users@googlegroups.com \
    --cc=srinuvasan.a@siemens.com \
    /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