apt attempting to remove proxmox-ve after upgrade

T

twowordz

Member
Nov 10, 2021
3
1
8
45
Hi!

I've upgraded from 7.1 to 7.3 this morning. After a successful upgrade and reboot, I've uninstalled unneeded nvidia drivers.

So basically:
Upgrade from GUI
Reboot
apt update
apt purge "*nvidia*"
apt purge cuda-drivers
apt install
apt install usb-modeswitch (to use a wireless adapter I was previous running with a compiled kernel module)
apt install firmware-realtek

Bash: 
root@pve:~# apt install firmware-realtek
Reading package lists... Done
Building dependency tree... Done
Reading state information... Done
The following packages were automatically installed and are no longer required:
  pve-kernel-5.11.22-3-pve pve-kernel-5.4.128-1-pve
Use 'apt autoremove' to remove them.
The following packages will be REMOVED:
  proxmox-ve pve-firmware pve-kernel-5.11 pve-kernel-5.15 pve-kernel-5.4
The following NEW packages will be installed:
  firmware-realtek
0 upgraded, 1 newly installed, 5 to remove and 0 not upgraded.
Need to get 0 B/921 kB of archives.
After this operation, 254 MB disk space will be freed.
Do you want to continue? [Y/n]
Abort.
root@pve:~# apt dist-upgrade
Reading package lists... Done
Building dependency tree... Done
Reading state information... Done
Calculating upgrade... Done
0 upgraded, 0 newly installed, 0 to remove and 0 not upgraded.
root@pve:~# apt -o Debug::pkgProblemResolver=yes install firmware-realtek
Reading package lists... Done
Building dependency tree... Done
Reading state information... Done
Starting pkgProblemResolver with broken count: 1
Starting 2 pkgProblemResolver with broken count: 1
Investigating (0) pve-firmware:amd64 < 3.6-2 @ii mK Ib >
Broken pve-firmware:amd64 Conflicts on firmware-realtek:amd64 < none -> 20210315-3 @un puN >
  Considering firmware-realtek:amd64 9998 as a solution to pve-firmware:amd64 5
  Removing pve-firmware:amd64 rather than change firmware-realtek:amd64
Investigating (0) pve-kernel-5.15:amd64 < 7.3-1 @ii mK Ib >
Broken pve-kernel-5.15:amd64 Depends on pve-firmware:amd64 < 3.6-2 @ii mR >
  Considering pve-firmware:amd64 5 as a solution to pve-kernel-5.15:amd64 3
  Removing pve-kernel-5.15:amd64 rather than change pve-firmware:amd64
Investigating (0) pve-kernel-5.11:amd64 < 7.0-10 @ii mK Ib >
Broken pve-kernel-5.11:amd64 Depends on pve-firmware:amd64 < 3.6-2 @ii mR >
  Considering pve-firmware:amd64 5 as a solution to pve-kernel-5.11:amd64 0
  Removing pve-kernel-5.11:amd64 rather than change pve-firmware:amd64
Investigating (0) proxmox-ve:amd64 < 7.3-1 @ii mK Ib >
Broken proxmox-ve:amd64 Depends on pve-kernel-5.15:amd64 < 7.3-1 @ii mR >
  Considering pve-kernel-5.15:amd64 3 as a solution to proxmox-ve:amd64 0
  Removing proxmox-ve:amd64 rather than change pve-kernel-5.15:amd64
Investigating (0) pve-kernel-5.4:amd64 < 6.4-5 @ii mK Ib >
Broken pve-kernel-5.4:amd64 Depends on pve-firmware:amd64 < 3.6-2 @ii mR >
  Considering pve-firmware:amd64 5 as a solution to pve-kernel-5.4:amd64 -2
  Removing pve-kernel-5.4:amd64 rather than change pve-firmware:amd64
Done
The following package was automatically installed and is no longer required:
  pve-kernel-5.4.128-1-pve
Use 'apt autoremove' to remove it.
The following packages will be REMOVED:
  proxmox-ve pve-firmware pve-kernel-5.11 pve-kernel-5.15 pve-kernel-5.4
The following NEW packages will be installed:
  firmware-realtek
0 upgraded, 1 newly installed, 5 to remove and 0 not upgraded.
Need to get 0 B/921 kB of archives.
After this operation, 254 MB disk space will be freed.
Do you want to continue? [Y/n]

I'm not sure how to proceed from here.

The realtek driver is for a wireless adapter I'm using in a lxd container.

Thanks
 
Sometimes installing software will create a package conflict. apt will attempt to resolve by uninstalling packages affected, and since the proxmox-ve metapackages covers so much ground it will fall into that net.

your options are either to either NOT to install the affecting package, or- you can go ahead and hit yes. once the installation/removal is done, DO NOT REBOOT, AND MAKE SURE TO REINSTALL PROXMOX-VE (this process removes your kernel, which would make your OS not boot.)

Mind you, this isnt certain to work, and apt may require you to uninstall the package causing the conflict to complete reinstallation.
 
@alexskysilk that seems like more risk than I'm comfortable with. I might just rebuild the module from source. I was just trying to save the trouble between kernel upgrades.
 
You must log in or register to reply here.
Top Bottom