From: Baurzhan Ismagulov <ibr@radix50.net>
To: isar-users@googlegroups.com
Subject: Re: [PATCH 1/1] apt: allow package downgrades in sbuild chroots
Date: Thu, 5 Jun 2025 15:00:39 +0200 [thread overview]
Message-ID: <aEGU9-b9PBGIbPxf@abai.de> (raw)
In-Reply-To: <b9a95f82-c669-46ba-b79c-333e503df153n@googlegroups.com>
On 2025-06-04 06:58, Cihan Mete Bahadır wrote:
> 14 Mayıs 2025 Çarşamba tarihinde saat 16:44:40 UTC+3 itibarıyla Baurzhan
> Ismagulov şunları yazdı:
> > 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).
> Also had the issue while downgrading :
>
> The following packages will be DOWNGRADED:
> libsystemd0 libudev1
> 0 upgraded, 266 newly installed, 2 downgraded, 0 to remove and 0 not
> upgraded.
> E: Packages were downgraded and -y was used without --allow-downgrades.
Thanks Mete for the update. To be clear, I'm not challenging that the issue
exists. Tricky topics need testcases for the code to stay modifiable. We'll
check this.
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/aEGU9-b9PBGIbPxf%40abai.de.
prev parent reply other threads:[~2025-06-05 13:00 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
2025-06-04 13:58 ` Cihan Mete Bahadır
2025-06-05 13:00 ` Baurzhan Ismagulov [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=aEGU9-b9PBGIbPxf@abai.de \
--to=ibr@radix50.net \
--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