[SOLVED] Debian 10 Buster / apt wants to deinstall pve/proxmox

P

plast

New Member
Proxmox Subscriber
May 18, 2022
4
0
1
Hello,

I'm running Debian 10 Buster / PVE 6.4-13 system and I'm trying to update it:

# apt full-upgrade
Reading package lists... Done
Building dependency tree
Reading state information... Done
Calculating upgrade... Done
(..)
The following packages will be REMOVED:
proxmox-ve pve-firmware pve-kernel-5.4
The following NEW packages will be installed:
firmware-linux-free linux-image-4.19.0-20-amd64
The following packages will be upgraded:
base-files bind9-host gzip intel-microcode libbind9-161 libc-bin libc-dev-bin libc-l10n libc6 libc6-dev libcups2 libdns-export1104 libdns1104 libexpat1 libflac8 libgmp10 libicu63 libisc-export1100 libisc1100 libisccc161 libisccfg163 liblwres161
liblzma5 libnss3 libpve-http-server-perl libsasl2-2 libsasl2-modules-db libsdl1.2debian libsmbclient libssl1.1 libtiff5 libwbclient0 libxml2 linux-image-amd64 linux-libc-dev locales openssl proxmox-widget-toolkit pve-kernel-helper pve-manager
rsyslog samba-common samba-libs smbclient tzdata vim vim-common vim-runtime vim-tiny xxd xz-utils zlib1g
52 upgraded, 2 newly installed, 3 to remove and 0 not upgraded.

This of course is not an option as I don't want to remove PVE/Proxmox.

My source.list is simple:

# cat /etc/apt/sources.list
deb http://mirror.hetzner.de/debian/packages buster main contrib non-free
deb http://mirror.hetzner.de/debian/security buster/updates main contrib non-free
deb http://mirror.hetzner.de/debian/packages buster-updates main contrib non-free
deb http://deb.debian.org/debian/ buster main non-free contrib
deb http://security.debian.org/debian-security buster/updates main contrib non-free
deb http://deb.debian.org/debian/ buster-updates main contrib non-free

deb https://enterprise.proxmox.com/debian/pve buster pve-enterprise

What can I do/check?
 
Last edited:
Yes I do have a subscription that's why I am using enterprise repo :)

But this problem occurs also on non-subscription repo, I've just tested (on another server, without a subscription).
 
# apt update Hit:1 http://mirror.hetzner.de/debian/packages buster InRelease Hit:2 http://mirror.hetzner.de/debian/security buster/updates InRelease Hit:3 http://mirror.hetzner.de/debian/packages buster-updates InRelease Hit:4 http://security.debian.org/debian-security buster/updates InRelease Hit:5 http://deb.debian.org/debian buster InRelease Hit:6 http://deb.debian.org/debian buster-updates InRelease Hit:7 https://enterprise.proxmox.com/debian/pve buster InRelease Reading package lists... Done Building dependency tree Reading state information... Done 53 packages can be upgraded. Run 'apt list --upgradable' to see them.
 
plast said:
The following NEW packages will be installed:
firmware-linux-free linux-image-4.19.0-20-amd64
Click to expand...
There was a recent change with the dependencies of the linux-image (from debian upstream) - this can lead to that situation

in any case - since you're running pve you're running with the pve-kernel - the simplest and cleanest solution is to simply remove the debian-upstream kernel and meta package:
`apt remove linux-image-amd64`
(if you like you can also remove all packages matching `linux-image-4.19.`)

I hope this helps!
 
  • Like
Reactions: plast
Yes, that helped, thanks a lot :)

Additional question - I've got now newest packages pve-*, but I'm running older kernel. I'd need to reboot machine to run newer kernel, but can't do it right now, it will have to wait 2-4 days. Is it safe (in terms of system/services stability) to use older kernel with newest packages? I'm asking because I rarely have opportunity to restart physical machine so this kind of situation may happen often.
 
plast said:
but I'm running older kernel. I'd need to reboot machine to run newer kernel, but can't do it right now, it will have to wait 2-4 days. Is it safe (in terms of system/services stability) to use older kernel with newest packages?
Click to expand...
While I cannot guarantee that there never will be any issue at all when running a (really) old kernel with the latest userspace software - I don't think that anything crashing due to this has happened in the past years (however I would argue that rebooting after a major version upgrade (e.g. PVE 6 -> PVE 7 is a must)).

That being said - I would suggest to keep the time running with an older kernel as short as possible (quite a few updated kernel versions are released because they fix security-issues, to which you're still exposed when running and older version)

I hope this helps!
 
  • Like
Reactions: plast
You must log in or register to reply here.
Top Bottom