From: "Moessbauer, Felix" <felix.moessbauer@siemens.com>
To: "ubely@ilbers.de" <ubely@ilbers.de>,
"Schild, Henning" <henning.schild@siemens.com>
Cc: "isar-users@googlegroups.com" <isar-users@googlegroups.com>
Subject: Re: [PATCH] Reinstall imager deps if package in IMAGER_INSTALL has changed.
Date: Mon, 30 Jan 2023 12:28:40 +0000 [thread overview]
Message-ID: <2601af9e373c6756e6adad7c6128a3acccbbc793.camel@siemens.com> (raw)
In-Reply-To: <20230130115353.067f0d5c@md1za8fc.ad001.siemens.net>
On Mon, 2023-01-30 at 11:53 +0100, Henning Schild wrote:
> Am Mon, 30 Jan 2023 10:07:41 +0100
> schrieb Uladzimir Bely <ubely@ilbers.de>:
>
> > When debugging packages in `isar-apt` that are in IMAGER_INSTALL
> > list, they happen not to be updated in the resulting image.
> >
> > For example, in case of u-boot IMAGE_BOOT_FILES is used to generate
> > files for `/boot` partition. Buildchroot is currently used for
> > extracting required files from `u-boot`, `optee-os`, etc. These
> > packages are installed in buildchroot via IMAGER_INSTALL list.
> >
> > Since modifications of the packages don't change their versions,
> > updated packages don't go to buildchroot, so previously used
> > versions
> > are wrongly used. The following can be seen in log:
> >
> > "<package> is already the newest version"
> >
> > This patch forces reinstalling all the packages from IMAGER_INSTALL
> > list if some of them has changed.
>
>
> That makes some sense anyhow. But we should really watch out for such
> issues and demand version bumping when contents change. Maybe not for
> every recipe. Or we should include all recipes for IMAGER_INSTALL
> into
> the sstate input so the cache gets invalidated and the chroot gets
> rebuild from scratch.
I agree for packages that we deploy. But especially the imaging
packages are often local-only and specific to the machine and
configuration. By that, we should not require versioning.
Regarding sstate: This is actually a rebuild-only issue. The sstate-
cache is fully transparent in this regard, as the bb hashes change in
case we change an imaging package (including all downstream hashes).
Felix
>
> Henning
>
> >
> > Signed-off-by: Uladzimir Bely <ubely@ilbers.de>
> > ---
> > meta/classes/image-tools-extension.bbclass | 4 ++--
> > 1 file changed, 2 insertions(+), 2 deletions(-)
> >
> > diff --git a/meta/classes/image-tools-extension.bbclass
> > b/meta/classes/image-tools-extension.bbclass index
> > 101704d0..640e1958
> > 100644 --- a/meta/classes/image-tools-extension.bbclass
> > +++ b/meta/classes/image-tools-extension.bbclass
> > @@ -35,12 +35,12 @@ do_install_imager_deps() {
> > -o APT::Get::List-Cleanup="0"
> > apt-get -o Debug::pkgProblemResolver=yes
> > --no-install-recommends -y \ --allow-unauthenticated
> > --allow-downgrades --download-only install \
> > - ${IMAGER_INSTALL}'
> > + --reinstall ${IMAGER_INSTALL}'
> >
> > deb_dl_dir_export ${BUILDCHROOT_DIR} ${distro}
> > sudo -E chroot ${BUILDCHROOT_DIR} sh -c ' \
> > apt-get -o Debug::pkgProblemResolver=yes
> > --no-install-recommends -y \ --allow-unauthenticated
> > --allow-downgrades install \
> > - ${IMAGER_INSTALL}'
> > + --reinstall ${IMAGER_INSTALL}'
> > }
> > addtask install_imager_deps before do_image_tools
>
next prev parent reply other threads:[~2023-01-30 12:28 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-01-30 9:07 Uladzimir Bely
2023-01-30 10:53 ` Henning Schild
2023-01-30 12:28 ` Moessbauer, Felix [this message]
2023-01-30 13:00 ` Roberto A. Foglietta
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=2601af9e373c6756e6adad7c6128a3acccbbc793.camel@siemens.com \
--to=felix.moessbauer@siemens.com \
--cc=henning.schild@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