public inbox for pve-user@lists.proxmox.com
 help / color / mirror / Atom feed
From: Federico Alves <venefax@gmail.com>
To: Proxmox VE user list <pve-user@lists.proxmox.com>
Subject: Re: [PVE-User] Proxmox VE 8.4 released!
Date: Fri, 11 Apr 2025 15:50:32 -0400	[thread overview]
Message-ID: <CAC9cSOB48cijLYctBoY=g8Zr9ToCj8_zn2UqZXHU13fmBfnKGg@mail.gmail.com> (raw)
In-Reply-To: <2d16993e-e8d5-4ca8-b62e-0ccd0bfa27c4@proxmox.com>

Just out of curiosity, why should I use apt-get vs apt?
what are the equivalent commands for apt?


On Thu, Apr 10, 2025 at 5:52 AM Fiona Ebner <f.ebner@proxmox.com> wrote:

> Hi,
>
> Am 10.04.25 um 07:08 schrieb Jack Raats via pve-user:
> >
> > I use the following script:
> >
> > upgrade.sh:
> >
> > #!/bin/sh
> > apt-get update
> > apt-get upgrade
>
> you shouldn't use 'upgrade' on Proxmox VE systems even if followed by
> 'full-upgrade'. Using only 'full-upgrade' is enough. See:
>
> https://lore.proxmox.com/pve-devel/20240909102050.40220-1-f.ebner@proxmox.com/
>
> Best Regards,
> Fiona
>
> > apt-get full-upgrade
> > apt-get autoremove
> > apt-get autoclean
> >
> > Gr.,
> > Jack Raats
>
>
>
>
> _______________________________________________
> pve-user mailing list
> pve-user@lists.proxmox.com
> https://lists.proxmox.com/cgi-bin/mailman/listinfo/pve-user
>
>
_______________________________________________
pve-user mailing list
pve-user@lists.proxmox.com
https://lists.proxmox.com/cgi-bin/mailman/listinfo/pve-user

  reply	other threads:[~2025-04-11 19:51 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <84cf9af1-5e12-48fa-81ca-35547845683d@proxmox.com>
2025-04-09 12:21 ` Michel Donais
2025-04-09 23:45 ` Federico Alves
2025-04-10  5:08   ` Jack Raats via pve-user
2025-04-10  9:51     ` Fiona Ebner
2025-04-11 19:50       ` Federico Alves [this message]
2025-04-11 20:14         ` Michael Rasmussen via pve-user
2025-04-10  6:31   ` DERUMIER, Alexandre

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='CAC9cSOB48cijLYctBoY=g8Zr9ToCj8_zn2UqZXHU13fmBfnKGg@mail.gmail.com' \
    --to=venefax@gmail.com \
    --cc=pve-user@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
Service provided by Proxmox Server Solutions GmbH | Privacy | Legal