From: "'MOESSBAUER, Felix' via isar-users" <isar-users@googlegroups.com>
To: "isar-users@googlegroups.com" <isar-users@googlegroups.com>,
"Kiszka, Jan" <jan.kiszka@siemens.com>
Subject: Re: [PATCH 1/1] apt: allow package downgrades in sbuild chroots
Date: Tue, 13 May 2025 13:11:29 +0000 [thread overview]
Message-ID: <7896b20dfa5a3c68fc8f99d67e7b50de5e3d6521.camel@siemens.com> (raw)
In-Reply-To: <c639b00e-4152-401c-a4f9-6e03a59dbbc9@siemens.com>
On Tue, 2025-05-13 at 13:40 +0200, Jan Kiszka wrote:
> On 13.05.25 09:02, 'Felix Moessbauer' via isar-users wrote:
> > The sbuild chroots carry many packages needed for the build
> > environment.
> > This sometimes requires packages from bootstrapping to be
> > downgraded so
> > that the dependencies can be resolved.
> >
> > An example is the liblzma5 which currently (1st of May 2025) needs
> > to be
> > downgraded on Debian bookworm.
> >
> > Signed-off-by: Felix Moessbauer <felix.moessbauer@siemens.com>
> > ---
> > meta/recipes-devtools/sbuild-chroot/sbuild-chroot.inc | 3 +++
> > 1 file changed, 3 insertions(+)
> >
> > diff --git a/meta/recipes-devtools/sbuild-chroot/sbuild-chroot.inc
> > b/meta/recipes-devtools/sbuild-chroot/sbuild-chroot.inc
> > index 6478d3a6..05424f54 100644
> > --- a/meta/recipes-devtools/sbuild-chroot/sbuild-chroot.inc
> > +++ b/meta/recipes-devtools/sbuild-chroot/sbuild-chroot.inc
> > @@ -61,6 +61,9 @@ ROOTFS_POSTPROCESS_COMMAND:remove =
> > "rootfs_cleanup_isar_apt"
> > # Do not cleanup base-apt
> > ROOTFS_POSTPROCESS_COMMAND:remove = "rootfs_cleanup_base_apt"
> >
> > +# Allow downgrades of packages from bootstrap
> > +ROOTFS_APT_ARGS += "--allow-downgrades"
> > +
>
> We already have partial downgrade permission for isar-apt and even
> for
> the devshell. We should check if those are then still relevant.
I also thought about globally applying the downgrade permission to the
rootfs class, but I also was unsure about the side-effects.
Nontheless, I prefer to have this fix merged rather sooner than later,
as Debian bookworm builds ~ after 1st of may are broken. It looks like
some package in the sbuild chroot list depends on an older version of
liblzma5 which is already installed during bootstrap.
Felix
>
> But we also need to check again about other, maybe less desirable
> side
> effects of this change...
>
> Jan
>
> > DEPLOY_SCHROOT = "${@d.getVar('SCHROOT_' +
> > d.getVar('SBUILD_VARIANT').upper() +
> > '_DIR')}${SBUILD_SCHROOT_SUFFIX}"
> >
> > do_sbuildchroot_deploy[dirs] = "${DEPLOY_DIR}/schroot-
> > ${SBUILD_VARIANT}"
>
--
Siemens AG
Linux Expert Center
Friedrich-Ludwig-Bauer-Str. 3
85748 Garching, Germany
--
You received this message because you are subscribed to the Google Groups "isar-users" group.
To unsubscribe from this group and stop receiving emails from it, send an email to isar-users+unsubscribe@googlegroups.com.
To view this discussion visit https://groups.google.com/d/msgid/isar-users/7896b20dfa5a3c68fc8f99d67e7b50de5e3d6521.camel%40siemens.com.
next prev parent reply other threads:[~2025-05-13 13:11 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-05-13 7:02 'Felix Moessbauer' via isar-users
2025-05-13 11:40 ` 'Jan Kiszka' via isar-users
2025-05-13 13:11 ` 'MOESSBAUER, Felix' via isar-users [this message]
2025-05-14 13:44 ` Baurzhan Ismagulov
2025-06-04 13:58 ` Cihan Mete Bahadır
2025-06-05 13:00 ` Baurzhan Ismagulov
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=7896b20dfa5a3c68fc8f99d67e7b50de5e3d6521.camel@siemens.com \
--to=isar-users@googlegroups.com \
--cc=felix.moessbauer@siemens.com \
--cc=jan.kiszka@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