From: Nicolas Frey <n.frey@proxmox.com>
To: pve-devel@lists.proxmox.com
Subject: [PATCH pve-docs 1/1] software updates: add short section about unattended-upgrades
Date: Wed, 26 Aug 2026 17:05:30 +0200 [thread overview]
Message-ID: <20260826150547.692282-1-n.frey@proxmox.com> (raw)
as it has increasingly come up in enterprise support, where it would be
of use to have something in our own docs to quote about this topic.
this is somewhat of a follow-up to commit 86bddb2e3d39 that introduced a
warning right above this section about partial upgrades using `apt
upgrade`.
Signed-off-by: Nicolas Frey <n.frey@proxmox.com>
---
Notes:
This was discussed off-list a bunch with Laurențiu, only found
time now to get to this.
Same as for the series for adding the warning for partial upgrades,
this is intended to be sent to the docs of all other products too. just
gathering feedback here first.
system-software-updates.adoc | 8 ++++++++
1 file changed, 8 insertions(+)
diff --git a/system-software-updates.adoc b/system-software-updates.adoc
index aa8f90d..483863c 100644
--- a/system-software-updates.adoc
+++ b/system-software-updates.adoc
@@ -26,3 +26,11 @@ 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}.
+
+Unattended Upgrades
+^^^^^^^^^^^^^^^^^^^
+`unattended-upgrades` cannot be configured to perform an equivalent
+action to `apt full-upgrade`, which is required for {pve} repositories
+to ensure full system updates. However, Debian base repositories can be
+configured to be automatically updated this way by using `Origins-Pattern`
+to only match a specific origin and/or suite.
--
2.47.3
reply other threads:[~2026-08-26 15:05 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=20260826150547.692282-1-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.