From mboxrd@z Thu Jan 1 00:00:00 1970
Return-Path: <pve-devel-bounces@lists.proxmox.com>
Received: from firstgate.proxmox.com (firstgate.proxmox.com [212.224.123.68])
by lore.proxmox.com (Postfix) with ESMTPS id 449ED1FF18C
for <inbox@lore.proxmox.com>; Mon, 24 Mar 2025 17:50:55 +0100 (CET)
Received: from firstgate.proxmox.com (localhost [127.0.0.1])
by firstgate.proxmox.com (Proxmox) with ESMTP id 1739231AF8;
Mon, 24 Mar 2025 17:50:50 +0100 (CET)
Message-ID: <b7703f81-8418-4cd7-802e-9852b5b1b8bf@proxmox.com>
Date: Mon, 24 Mar 2025 17:50:45 +0100
MIME-Version: 1.0
User-Agent: Mozilla Thunderbird
Content-Language: en-US
To: Proxmox VE development discussion <pve-devel@lists.proxmox.com>,
Alexander Zeidler <a.zeidler@proxmox.com>
References: <20250210103644.3-1-a.zeidler@proxmox.com>
From: Aaron Lauterer <a.lauterer@proxmox.com>
In-Reply-To: <20250210103644.3-1-a.zeidler@proxmox.com>
X-SPAM-LEVEL: Spam detection results: 0
AWL -0.033 Adjusted score from AWL reputation of From: address
BAYES_00 -1.9 Bayes spam probability is 0 to 1%
DMARC_MISSING 0.1 Missing DMARC policy
KAM_DMARC_STATUS 0.01 Test Rule for DKIM or SPF Failure with Strict Alignment
RCVD_IN_VALIDITY_CERTIFIED_BLOCKED 0.001 ADMINISTRATOR NOTICE: The query to
Validity was blocked. See
https://knowledge.validity.com/hc/en-us/articles/20961730681243 for more
information.
RCVD_IN_VALIDITY_RPBL_BLOCKED 0.001 ADMINISTRATOR NOTICE: The query to
Validity was blocked. See
https://knowledge.validity.com/hc/en-us/articles/20961730681243 for more
information.
RCVD_IN_VALIDITY_SAFE_BLOCKED 0.001 ADMINISTRATOR NOTICE: The query to
Validity was blocked. See
https://knowledge.validity.com/hc/en-us/articles/20961730681243 for more
information.
SPF_HELO_NONE 0.001 SPF: HELO does not publish an SPF Record
SPF_PASS -0.001 SPF: sender matches SPF record
URIBL_BLOCKED 0.001 ADMINISTRATOR NOTICE: The query to URIBL was blocked. See
http://wiki.apache.org/spamassassin/DnsBlocklists#dnsbl-block for more
information. [proxmox.com]
Subject: Re: [pve-devel] [PATCH docs v1] package repos: revise Ceph section,
introduce 2 attributes
X-BeenThere: pve-devel@lists.proxmox.com
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: Proxmox VE development discussion <pve-devel.lists.proxmox.com>
List-Unsubscribe: <https://lists.proxmox.com/cgi-bin/mailman/options/pve-devel>,
<mailto:pve-devel-request@lists.proxmox.com?subject=unsubscribe>
List-Archive: <http://lists.proxmox.com/pipermail/pve-devel/>
List-Post: <mailto:pve-devel@lists.proxmox.com>
List-Help: <mailto:pve-devel-request@lists.proxmox.com?subject=help>
List-Subscribe: <https://lists.proxmox.com/cgi-bin/mailman/listinfo/pve-devel>,
<mailto:pve-devel-request@lists.proxmox.com?subject=subscribe>
Reply-To: Proxmox VE development discussion <pve-devel@lists.proxmox.com>
Content-Transfer-Encoding: 7bit
Content-Type: text/plain; charset="us-ascii"; Format="flowed"
Errors-To: pve-devel-bounces@lists.proxmox.com
Sender: "pve-devel" <pve-devel-bounces@lists.proxmox.com>
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.zeidler@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