From: Nicolas Frey <n.frey@proxmox.com>
To: pve-devel@lists.proxmox.com
Subject: [PATCH pve-docs 2/2] software updates: add warning about using apt upgrade
Date: Thu, 11 Jun 2026 15:58:47 +0200 [thread overview]
Message-ID: <20260611135847.276100-3-n.frey@proxmox.com> (raw)
In-Reply-To: <20260611135847.276100-1-n.frey@proxmox.com>
as it has increasingly come up in enterprise support and is generally an
easy foot gun for people coming from other Debian-based distros.
See commit 2eaf8334 for further reference.
Signed-off-by: Nicolas Frey <n.frey@proxmox.com>
---
system-software-updates.adoc | 4 ++++
1 file changed, 4 insertions(+)
diff --git a/system-software-updates.adoc b/system-software-updates.adoc
index 32afac1..6b30aff 100644
--- a/system-software-updates.adoc
+++ b/system-software-updates.adoc
@@ -13,6 +13,10 @@ updates use the web-based GUI or the following CLI commands:
# apt full-upgrade
----
+WARNING: As {PVE} uses a rolling release model on top of Debian, performing an `apt upgrade`
+may result in a partially-upgraded or broken package state. This is because `apt full-upgrade`
+can also remove existing packages to satisfy dependencies if needed, while `apt upgrade` cannot.
+
For occasionally upgrading Ceph to its succeeding major release, see
xref:sysadmin_package_repositories_ceph[Ceph Repositories].
--
2.47.3
prev parent reply other threads:[~2026-06-11 13:58 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 ` [PATCH pve-docs 1/2] software updates: use apt instead of apt-get Nicolas Frey
2026-06-11 13:58 ` Nicolas Frey [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=20260611135847.276100-3-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.