all lists on lists.proxmox.com
 help / color / mirror / Atom feed
From: Christoph Heiss <c.heiss@proxmox.com>
To: pve-devel@lists.proxmox.com
Subject: [pve-devel] [PATCH docs 5/9] package-repos: align wording with pmg-docs
Date: Mon,  4 Mar 2024 14:22:12 +0100	[thread overview]
Message-ID: <20240304132221.901327-6-c.heiss@proxmox.com> (raw)
In-Reply-To: <20240304132221.901327-1-c.heiss@proxmox.com>

These are phrased better and more expansive in pmg-docs, so take them
from there and only slightly adapt naming as needed.

Signed-off-by: Christoph Heiss <c.heiss@proxmox.com>
---
 pve-package-repos.adoc | 18 ++++++++++++------
 1 file changed, 12 insertions(+), 6 deletions(-)

diff --git a/pve-package-repos.adoc b/pve-package-repos.adoc
index b0c2a95..1f23078 100644
--- a/pve-package-repos.adoc
+++ b/pve-package-repos.adoc
@@ -69,9 +69,14 @@ deb https://enterprise.proxmox.com/debian/pve bookworm pve-enterprise
 The `root@pam` user is notified via email about available updates. Click the
 'Changelog' button in the GUI to see more details about the selected update.
 
-You need a valid subscription key to access the `pve-enterprise` repository.
-Different support levels are available. Further details can be found at
-{pricing-url}.
+As soon as updates are available, the `root@pam` user is notified via email
+about the newly available packages. From the GUI, the 'Changelog' button in the
+GUI can be used to see more details about the selected update.
+Thus, you will never miss important security fixes.
+
+Please note that you need a valid subscription key to access the
+`pve-enterprise` repository. We offer different support levels, which you can
+find further details about at {pricing-url}.
 
 NOTE: You can disable this repository by commenting out the above line using a
 `#` (at the start of the line). This prevents error messages if your host does
@@ -82,9 +87,10 @@ repository in that case.
 {pve} No-Subscription Repository
 ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
 
-This is the recommended repository for testing and non-production use. Its
-packages are not as heavily tested and validated. You don't need a subscription key
-to access the `pve-no-subscription` repository.
+As the name suggests, you do not need a subscription key to access
+this repository. It can be used for testing and non-production
+use. It's not recommended to use this on production servers, as these
+packages are not always heavily tested and validated.
 
 We recommend to configure this repository in `/etc/apt/sources.list`.
 
-- 
2.43.0





  parent reply	other threads:[~2024-03-04 13:22 UTC|newest]

Thread overview: 18+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-03-04 13:22 [pve-devel] [PATCH docs 0/9] improve & unify installation(-related) documentation Christoph Heiss
2024-03-04 13:22 ` [pve-devel] [PATCH docs 1/9] gitignore: add package build outputs Christoph Heiss
2024-03-06 17:16   ` [pve-devel] applied: " Thomas Lamprecht
2024-03-04 13:22 ` [pve-devel] [PATCH docs 2/9] asciidoc: introduce `pricing-url` variable, much like pmg-docs Christoph Heiss
2024-03-06 17:16   ` [pve-devel] applied: " Thomas Lamprecht
2024-03-04 13:22 ` [pve-devel] [PATCH docs 3/9] local-btrfs: unify casing for btrfs Christoph Heiss
2024-03-06 17:19   ` [pve-devel] applied: " Thomas Lamprecht
2024-03-04 13:22 ` [pve-devel] [PATCH docs 4/9] getting-help: forum: align wording with pmg-docs Christoph Heiss
2024-03-06 17:19   ` [pve-devel] applied: " Thomas Lamprecht
2024-03-04 13:22 ` Christoph Heiss [this message]
2024-03-05  8:28   ` [pve-devel] [PATCH docs 5/9] package-repos: " Gabriel Goller
2024-03-05 12:00     ` Christoph Heiss
2024-03-04 13:22 ` [pve-devel] [PATCH docs 6/9] installation: iso: improve & " Christoph Heiss
2024-03-05  8:38   ` Gabriel Goller
2024-03-05 12:05     ` Christoph Heiss
2024-03-04 13:22 ` [pve-devel] [PATCH docs 7/9] installation: lvm-options: " Christoph Heiss
2024-03-04 13:22 ` [pve-devel] [PATCH docs 8/9] installation: zfs-options: " Christoph Heiss
2024-03-04 13:22 ` [pve-devel] [PATCH docs 9/9] installation: iso: reflow location and password dialog screenshots Christoph Heiss

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=20240304132221.901327-6-c.heiss@proxmox.com \
    --to=c.heiss@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.
Service provided by Proxmox Server Solutions GmbH | Privacy | Legal