dev <devuan.2@???> writes:

[...]


> #
> # apt-get upgrade <--<< kernel 2.6.32 will NOT install, updates will

[...]

> The following packages have been kept back:
> proxmox-ve-2.6.32
> The following packages will be upgraded:
> base-files libnvpair1 libpve-common-perl libuutil1 libwbclient0
> libzfs2 libzpool2 openssh-client openssh-server samba-common smbclient
> ssh tzdata

[...]

> # apt-get dist-upgrade <--<< kernel will install, updates will

[...]

> The following NEW packages will be installed:
> pve-kernel-2.6.32-45-pve
> The following packages will be upgraded:
> base-files libnvpair1 libpve-common-perl libuutil1 libwbclient0
> libzfs2 libzpool2 openssh-client openssh-server proxmox-ve-2.6.32
> samba-common smbclient ssh tzdata

[...]

'upgrade' is supposed to update already installed packages but must not
install new packages or remove installed packages. Hence, for the first
example, proxmox-ve-2.6.23 is not upgraded because it depends on a kernel
package which isn't installed.

'dist-upgrade' should update everything and 'intelligently' handle
changed dependencies, ie install new depedencies if that enables an
existing package to be upgraded (pve-kernel-2.6.32-45-pve/
proxmox-ve-2.6.32) or remove installed packages if they conflict with
to-be-installed ones and nothing depends on them.

As far as I remember (I've neve user aptitude), older version of
aptitude could solve some dependency conflicts older versions of apt-get
couldn't handle because aptitude could temporarily 'break' a dependency
by removing a package to resolve a conflict provided a to be installed
package would 'unbreak' it again. But meanwhile, apt-get can
(reportedly) do this as well.