On  2025-02-10  11:36, Alexander Zeidler wrote:
* Remove duplicated text to maintain clarity
* Mention available installation methods (web-based wizard, CLI tool)
* Create a table to see the support state of Ceph releases

I am not sure if having this in the rather static documentation is a good idea. Having it in the Proxmox VE wiki where changes can be made quickly is probably better. Similar how we handle it for PVE releases with https://pve.proxmox.com/wiki/FAQ

* List and link to the EOL dates of Ceph releases
* Reword the descriptions of available PVE repositories

* Add two new attributes to avoid manual editing multiple lines
** debian-codename=bookworm
    It seems that the codename is not available in the build process,
    so updating the new attribute on Debian major release upgrades may
    be fine.
** pve-version=8
    While `revnumber` ("8.3.1") is made available by the current build
    process, it is not as suitable as only mentioning the major version
    number.

Signed-off-by: Alexander Zeidler <a.zeid...@proxmox.com>
---
  asciidoc/asciidoc-pve.conf |   2 +
  pve-package-repos.adoc     | 165 ++++++++++++++-----------------------
  2 files changed, 63 insertions(+), 104 deletions(-)

diff --git a/asciidoc/asciidoc-pve.conf b/asciidoc/asciidoc-pve.conf
index 0c28298..8ad635f 100644
--- a/asciidoc/asciidoc-pve.conf
+++ b/asciidoc/asciidoc-pve.conf
@@ -3,6 +3,8 @@
  proxmoxGmbh=Proxmox Server Solutions GmbH
  copyright=Proxmox Server Solutions GmbH
  pve=Proxmox VE
+pve-version=8
+debian-codename=bookworm
  pricing-url=https://proxmox.com/en/proxmox-virtual-environment/pricing
  website=https://www.proxmox.com/
  forum-url=https://forum.proxmox.com/
diff --git a/pve-package-repos.adoc b/pve-package-repos.adoc
index c831cd9..e0a9fb5 100644
--- a/pve-package-repos.adoc
+++ b/pve-package-repos.adoc
@@ -24,6 +24,7 @@ security updates, bug fixes and new features.
  APT Repositories are defined in the file `/etc/apt/sources.list` and in 
`.list`
  files placed in `/etc/apt/sources.list.d/`.
+[[repository_management]]
  Repository Management
  ^^^^^^^^^^^^^^^^^^^^^

Since we already have the auto-generated "_repository_management" anchor, I would keep it, but manually define it here. This way we do not break any existing references to this part of the admin guide.


_______________________________________________
pve-devel mailing list
pve-devel@lists.proxmox.com
https://lists.proxmox.com/cgi-bin/mailman/listinfo/pve-devel

Reply via email to