From: Fiona Ebner <f.ebner@proxmox.com>
To: pve-devel@lists.proxmox.com
Subject: [pve-devel] [PATCH-SERIES proxmox-apt/widget-toolkit] prepare for major upgrade
Date: Mon, 5 Jun 2023 17:43:07 +0200 [thread overview]
Message-ID: <20230605154313.181289-1-f.ebner@proxmox.com> (raw)
There's a confusing issue when the suites are already updated,
because the UI will not detect any Proxmox VE repository anymore then.
This is fixed by the proxmox-apt patch intended for the stable branch.
The UI patches make sure the ignore-pre-upgrade-warning is actually
ignored and add a check for mixed repositories when upgrade is allowed.
The final UI patch is intended for the stable branch only and makes
sure that the warning handling expects a major upgrade to be allowed.
proxmox-apt:
Fiona Ebner (1):
repositories: also detect repository with next suite as configured
src/repositories/mod.rs | 7 ++++++-
1 file changed, 6 insertions(+), 1 deletion(-)
proxmox-widget-toolkit:
Fiona Ebner (5):
apt repositories: actually ignore ignore-pre-upgrade-warning
apt repositories: just ignore unknown info rather than throwing an
error
apt repositories: add classifyOrigin helper
apt repositories: detect mixed suites before major upgrade
apt repositoires: allow major upgrade
src/node/APTRepositories.js | 63 ++++++++++++++++++++++++++++++-------
1 file changed, 52 insertions(+), 11 deletions(-)
--
2.39.2
next reply other threads:[~2023-06-05 15:43 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-06-05 15:43 Fiona Ebner [this message]
2023-06-05 15:43 ` [pve-devel] [PATCH stable proxmox-apt 1/1] repositories: also detect repository with next suite as configured Fiona Ebner
2023-06-09 8:45 ` Wolfgang Bumiller
2023-06-09 8:49 ` Fiona Ebner
2023-06-09 9:59 ` [pve-devel] applied: " Wolfgang Bumiller
2023-06-05 15:43 ` [pve-devel] [PATCH widget-toolkit 1/5] apt repositories: actually ignore ignore-pre-upgrade-warning Fiona Ebner
2023-06-05 15:43 ` [pve-devel] [PATCH/RFC widget-toolkit 2/5] apt repositories: just ignore unknown info rather than throwing an error Fiona Ebner
2023-06-05 17:06 ` Thomas Lamprecht
2023-06-06 6:27 ` Fiona Ebner
2023-06-05 15:43 ` [pve-devel] [PATCH widget-toolkit 3/5] apt repositories: add classifyOrigin helper Fiona Ebner
2023-06-05 15:43 ` [pve-devel] [PATCH widget-toolkit 4/5] apt repositories: detect mixed suites before major upgrade Fiona Ebner
2023-06-05 15:43 ` [pve-devel] [PATCH stable-bullseye widget-toolkit 5/5] apt repositoires: allow " Fiona Ebner
2023-06-07 15:23 ` [pve-devel] applied-series: [PATCH-SERIES proxmox-apt/widget-toolkit] prepare for " Thomas Lamprecht
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=20230605154313.181289-1-f.ebner@proxmox.com \
--to=f.ebner@proxmox.com \
--cc=pve-devel@lists.proxmox.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