From: Nicolas Frey <n.frey@proxmox.com>
To: pve-devel@lists.proxmox.com
Subject: [PATCH pve-docs 1/2] software updates: use apt instead of apt-get
Date: Thu, 11 Jun 2026 15:58:46 +0200 [thread overview]
Message-ID: <20260611135847.276100-2-n.frey@proxmox.com> (raw)
In-Reply-To: <20260611135847.276100-1-n.frey@proxmox.com>
and use full-upgrade instead of dist-upgrade.
although in pveupgrade we still use `apt-get dist-upgrade`, the user
facing doc should use apt, as:
* apt-get is normally used if you want a stable interface, e.g. for
scripts
* if {apt,apt-get} upgrade is run instead of {apt,apt-get} dist-upgrade,
the potential for a partially-upgraded package state is lower with apt,
as it can install new packages - if needed - to satisfy dependencies
full-upgrade is used as it is the preferred term for apt (see `man
apt`). also, it isn't *only* used to upgrade between dist releases, so
full-upgrade is clearer
As a reference to these claims, see:
https://lists.ubuntu.com/archives/ubuntu-users/2025-September/314942.html
Signed-off-by: Nicolas Frey <n.frey@proxmox.com>
---
system-software-updates.adoc | 6 +++---
1 file changed, 3 insertions(+), 3 deletions(-)
diff --git a/system-software-updates.adoc b/system-software-updates.adoc
index e6bf356..32afac1 100644
--- a/system-software-updates.adoc
+++ b/system-software-updates.adoc
@@ -9,15 +9,15 @@ Proxmox provides updates on a regular basis for all repositories. To install
updates use the web-based GUI or the following CLI commands:
----
-# apt-get update
-# apt-get dist-upgrade
+# apt update
+# apt full-upgrade
----
For occasionally upgrading Ceph to its succeeding major release, see
xref:sysadmin_package_repositories_ceph[Ceph Repositories].
NOTE: The APT package management system is very flexible and provides many
-features, see `man apt-get`, or <<Hertzog13>> for additional information.
+features, see `man apt`, or <<Hertzog13>> for additional information.
TIP: Regular updates are essential to get the latest patches and security
related fixes. Major system upgrades are announced in the {forum}.
--
2.47.3
next prev parent reply other threads:[~2026-06-11 13:59 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-06-11 13:58 [PATCH docs 0/2] software updates: improve user-facing update reference Nicolas Frey
2026-06-11 13:58 ` Nicolas Frey [this message]
2026-06-11 13:58 ` [PATCH pve-docs 2/2] software updates: add warning about using apt upgrade Nicolas Frey
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=20260611135847.276100-2-n.frey@proxmox.com \
--to=n.frey@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.