From: Thomas Lamprecht <t.lamprecht@proxmox.com>
To: Proxmox VE development discussion <pve-devel@lists.proxmox.com>,
Fiona Ebner <f.ebner@proxmox.com>
Subject: [pve-devel] applied: [PATCH v2 proxmox 1/5] apt: drop older Ceph standard repositories
Date: Sun, 4 Jun 2023 18:54:12 +0200 [thread overview]
Message-ID: <a8b5b95f-c65e-2059-ebf0-0cc70a4b4817@proxmox.com> (raw)
In-Reply-To: <20230602084824.54967-1-f.ebner@proxmox.com>
Am 02/06/2023 um 10:48 schrieb Fiona Ebner:
> On Proxmox VE 8, only Quincy and newer will be supported.
>
> Signed-off-by: Fiona Ebner <f.ebner@proxmox.com>
> ---
>
> No changes in v2.
>
> Changes for the series in v2:
> * create temporary test directories inside CARGO_TARGET_TMPDIR
> * mention that deprecated 'main' component maps to no-subscription
> in description of the repo.
A cover letter would make this a bit easier to notice. ^^
>
> proxmox-apt/src/repositories/mod.rs | 4 --
> proxmox-apt/src/repositories/standard.rs | 58 ------------------------
> proxmox-apt/tests/repositories.rs | 4 --
> 3 files changed, 66 deletions(-)
>
>
applied, thanks!
But I'd favor that the repo infos are namespaced by dist (bullseye, bookworm, ..), that way
we could keep historical records and add future ones up-front (for a future "change repos
to next release" helper), that would then also allow to generate some docs for available
repos automatically, e.g.: https://pve.proxmox.com/wiki/Package_Repositories
For the "Add Repo" UI it might be nicer to split repo & product, i.e., have another field
above the current repository one where one selects "Proxmox VE" or "Ceph", can simply be
disabled+hidden in Proxmox Backup Server and Proxmox Mail Gateway web UI's (as IIRC we
share the UI down to the whole panel).
prev parent reply other threads:[~2023-06-04 16:54 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-06-02 8:48 [pve-devel] " Fiona Ebner
2023-06-02 8:48 ` [pve-devel] [PATCH v2 proxmox 2/5] apt: split Ceph main repository into no-subscription and enterprise Fiona Ebner
2023-06-02 8:48 ` [pve-devel] [PATCH v2 proxmox 3/5] apt: tests: create temporary test directories in CARGO_TARGET_TMPDIR Fiona Ebner
2023-06-02 8:48 ` [pve-devel] [PATCH v2 proxmox 4/5] apt: tests: code cleanup to avoid useless vector Fiona Ebner
2023-06-02 8:48 ` [pve-devel] [PATCH v2 proxmox 5/5] apt: tests: add tests for Ceph Quincy repository detection on Bookworm Fiona Ebner
2023-06-04 16:54 ` Thomas Lamprecht [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=a8b5b95f-c65e-2059-ebf0-0cc70a4b4817@proxmox.com \
--to=t.lamprecht@proxmox.com \
--cc=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