From: Baurzhan Ismagulov <ibr@radix50.net>
To: isar-users@googlegroups.com
Cc: Felix Moessbauer <felix.moessbauer@siemens.com>
Subject: Re: [PATCH 1/1] apt: allow package downgrades in sbuild chroots
Date: Wed, 14 May 2025 15:44:35 +0200 [thread overview]
Message-ID: <aCSeQzqRzdO8JThh@abai.de> (raw)
In-Reply-To: <20250513070208.1226836-1-felix.moessbauer@siemens.com>
On 2025-05-13 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.
I think this touches a tricky topic and we should check whether this intersects
with e.g. [1], [2]. A testcase would definitely help. Also, at least the known
cases should be considered (upgrade / downgrade, non-essential / essential,
maybe non-compat / compat).
1. https://lists.isar-build.org/isar-users/20250221154843.515037-1-amikan@ilbers.de/
2. https://lists.isar-build.org/isar-users/215cc575-fa4f-45e6-8511-eff4254a4383@ilbers.de/T/#t
With kind regards,
Baurzhan
--
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/aCSeQzqRzdO8JThh%40abai.de.
next prev parent reply other threads:[~2025-05-14 13:44 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
2025-05-14 13:44 ` Baurzhan Ismagulov [this message]
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=aCSeQzqRzdO8JThh@abai.de \
--to=ibr@radix50.net \
--cc=felix.moessbauer@siemens.com \
--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