From: Nicolas Frey <n.frey@proxmox.com>
To: pmg-devel@lists.proxmox.com
Subject: [PATCH pmg-docs 1/1] faq: add warning about using apt upgrade
Date: Thu, 9 Jul 2026 16:26:06 +0200 [thread overview]
Message-ID: <20260709142606.363114-1-n.frey@proxmox.com> (raw)
as it has increasingly come up in enterprise support and is generally an
easy foot gun for people coming from other Debian-based distros.
Signed-off-by: Nicolas Frey <n.frey@proxmox.com>
---
Notes:
A similar patch that adds this warning was recently applied to PVE,
see commit 86bddb2e3d39 in `pve-docs` for more context
pmg-faq.adoc | 5 +++++
1 file changed, 5 insertions(+)
diff --git a/pmg-faq.adoc b/pmg-faq.adoc
index 602a9d1..a8a1e73 100644
--- a/pmg-faq.adoc
+++ b/pmg-faq.adoc
@@ -68,6 +68,11 @@ apt update
apt full-upgrade
----
+
+WARNING: As {pmg} 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.
++
NOTE: Always ensure that you correctly set up the
xref:pmg_package_repositories[package repositories], and only continue with the
actual upgrade if `apt update` did not hit any errors.
--
2.47.3
reply other threads:[~2026-07-09 14:26 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=20260709142606.363114-1-n.frey@proxmox.com \
--to=n.frey@proxmox.com \
--cc=pmg-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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox