public inbox for isar-users@googlegroups.com
 help / color / mirror / Atom feed
From: Uladzimir Bely <ubely@ilbers.de>
To: isar-users@googlegroups.com
Subject: Re: [PATCH v7] dpkg: Restore support for replacing pre-installed packages in sbuild-chroot
Date: Mon, 29 Jan 2024 13:48:44 +0300	[thread overview]
Message-ID: <a41076356048be7ab4ddaf32c6d922434bf343b9.camel@ilbers.de> (raw)
In-Reply-To: <20240127074253.24570-1-ubely@ilbers.de>

On Sat, 2024-01-27 at 08:42 +0100, Uladzimir Bely wrote:
> From: Jan Kiszka <jan.kiszka@siemens.com>
> 
> During the migration to sbuild, support for using self-built packages
> in
> the build environment was lost if those were already part of the
> sbuild-chroot. This restores it by adding --apt-distupgrade to the
> sbuild call. But that is not enough because sbuild will only upgrade
> packages from already configured sources, not those specified via
> --extra-repository. We therefore have to switch back to configuring
> isar-apt during sbuild-chroot creation.
> 
> As rootfs_configure_isar_apt configures the isar repo under
> /isar-apt, we bind-mount the one in /home/builder/${PN} to that
> folder.
> Another difference is that we now need to run apt-get update
> explicitly,
> but only for isar-apt.
> 
> For apt fetching, we neither need nor want isar-apt to be available.
> Rebuilding self-generated apt packages is generally pointless as the
> needs are better addressed in the generating recipe itself. Exposing
> isar-apt to the fetch may furthermore lead to fetching a previously
> built source package of the same recipe, rather than pulling the
> external version.
> 
> And because the sbuild-chroots are now left behind with isar-apt
> configured, the configuration in imager_run can be removed (credits
> to
> Srinuvasan Arjunan).
> 
> Signed-off-by: Jan Kiszka <jan.kiszka@siemens.com>
> Reviewed-by: Uladzimir Bely <ubely@ilbers.de>
> ---
> 
> Changes in v7: Merged v6 with fix disabling isar-apt for do_apt_fetch
> 
>  meta/classes/dpkg-base.bbclass                | 37 ++++++++++++-----
> --
>  meta/classes/dpkg.bbclass                     |  5 ++-
>  meta/classes/image-tools-extension.bbclass    | 13 -------
>  .../sbuild-chroot/sbuild-chroot.inc           |  2 -
>  4 files changed, 27 insertions(+), 30 deletions(-)
> 

Applied to next, thanks.

      parent reply	other threads:[~2024-01-29 10:48 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
2025-02-10 12:02           ` 'Jan Kiszka' via isar-users
2025-02-10 16:09             ` Anton Mikanovich
2024-01-29 10:48 ` Uladzimir Bely [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=a41076356048be7ab4ddaf32c6d922434bf343b9.camel@ilbers.de \
    --to=ubely@ilbers.de \
    --cc=isar-users@googlegroups.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