From: Thomas Lamprecht <t.lamprecht@proxmox.com>
To: "Fiona Ebner" <f.ebner@proxmox.com>,
"Fabian Grünbichler" <f.gruenbichler@proxmox.com>,
"Proxmox VE development discussion" <pve-devel@lists.proxmox.com>
Subject: Re: [pve-devel] [RFC qemu-server] apt hook: warn against using 'upgrade' command
Date: Mon, 9 Sep 2024 09:57:39 +0200 [thread overview]
Message-ID: <5f4007c3-97be-4cc9-a746-ccc72ca659f4@proxmox.com> (raw)
In-Reply-To: <d544faec-5319-4f00-baa8-01fbd7a197bd@proxmox.com>
Am 09/09/2024 um 09:52 schrieb Fiona Ebner:
> Am 09.09.24 um 09:48 schrieb Fabian Grünbichler:
>> given that I also use `apt upgrade` from time to time (habit from being an unstable user ;)), and that it might alienate power users coming from Debian, I'd prefer this to be a non-interactive warning with the text "disarmed" a bit?
>>
>> something like
>>
>> !! WARNING !!
>> Since Proxmox VE follows a rolling release model, using 'upgrade' can lead to a system being stuck on outdated versions, or in rare cases, break upon upgrading. Use 'dist-upgrade' or 'full-upgrade' instead.
>> !! WARNING !!
All right, albeit I find the "!! WARNING !!" still rather a bit to scary then.
Maybe just an extra newline above and below and then something like your wording:
NOTE: Proxmox VE follows a rolling release model, so using the 'upgrade' command [...]
FWIW, you could also make this more generic for easier re-use, like:
NOTE: Proxmox projects follow [...]
and ship it in a common package, maybe even an extra one that is only recommended,
not hard-dependency, so the power user can remove the warning if they don't care
(or are daring)
_______________________________________________
pve-devel mailing list
pve-devel@lists.proxmox.com
https://lists.proxmox.com/cgi-bin/mailman/listinfo/pve-devel
prev parent reply other threads:[~2024-09-09 7:57 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-09-06 10:40 Fiona Ebner
2024-09-06 10:42 ` Fiona Ebner
2024-09-06 11:01 ` Dominik Csapak
2024-09-06 16:54 ` Thomas Lamprecht
2024-09-06 12:16 ` Alexander Zeidler
2024-09-06 16:56 ` Thomas Lamprecht
2024-09-06 16:58 ` Thomas Lamprecht
2024-09-09 7:48 ` Fabian Grünbichler
2024-09-09 7:52 ` Fiona Ebner
2024-09-09 7:57 ` Thomas Lamprecht [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=5f4007c3-97be-4cc9-a746-ccc72ca659f4@proxmox.com \
--to=t.lamprecht@proxmox.com \
--cc=f.ebner@proxmox.com \
--cc=f.gruenbichler@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox