From: Nicolas Frey <n.frey@proxmox.com>
To: pdm-devel@lists.proxmox.com
Subject: [PATCH proxmox-datacenter-manager 1/1] faq: add warning about using apt upgrade
Date: Thu, 9 Jul 2026 16:26:23 +0200 [thread overview]
Message-ID: <20260709142623.363347-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
docs/faq.rst | 6 ++++++
1 file changed, 6 insertions(+)
diff --git a/docs/faq.rst b/docs/faq.rst
index d4ba9b50..3d8ecd3f 100644
--- a/docs/faq.rst
+++ b/docs/faq.rst
@@ -41,6 +41,12 @@ with:
apt update
apt full-upgrade
+.. warning:: As Proxmox Datacenter Manager 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 you correctly setup the :ref:`package repositories
<sysadmin_package_repositories>` and only continue with the actual upgrade if `apt update` did
not hit any error.
--
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=20260709142623.363347-1-n.frey@proxmox.com \
--to=n.frey@proxmox.com \
--cc=pdm-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