From: Thomas Lamprecht <t.lamprecht@proxmox.com>
To: Proxmox VE development discussion <pve-devel@lists.proxmox.com>,
Dominik Csapak <d.csapak@proxmox.com>,
Fiona Ebner <f.ebner@proxmox.com>
Subject: Re: [pve-devel] [RFC qemu-server] apt hook: warn against using 'upgrade' command
Date: Fri, 6 Sep 2024 18:54:09 +0200 [thread overview]
Message-ID: <18642cee-195b-4193-a920-1131ccb0c0b4@proxmox.com> (raw)
In-Reply-To: <be77bee0-7294-4d62-871e-977111896bbf@proxmox.com>
Am 06/09/2024 um 13:01 schrieb Dominik Csapak:
> just to mention it (i think it's not widely known):
>
> 'apt upgrade' behaves slightly different than 'apt-get upgrade'
>
> while the former also installs new packages if necessary, the latter
> doesn't, so an 'apt upgrade' will maybe work ok in most sitations.
> I guess we want to filter it out nonetheless?
>
> (none of the commands above will remove packages)
that's all true, but I agree also with your guess, we rely on removals
to happen as we have semi-frequent transitions during a stable release
cycle, so while `apt upgrade` is thankfully way more sensible already,
it still isn't enough for our use case.
_______________________________________________
pve-devel mailing list
pve-devel@lists.proxmox.com
https://lists.proxmox.com/cgi-bin/mailman/listinfo/pve-devel
next prev parent reply other threads:[~2024-09-06 16:53 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 [this message]
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
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=18642cee-195b-4193-a920-1131ccb0c0b4@proxmox.com \
--to=t.lamprecht@proxmox.com \
--cc=d.csapak@proxmox.com \
--cc=f.ebner@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.