Have updated proxmox, now cannot install pve-container due to dependency now wrong version

Proxmox
1

Hi guys

I’m running Proxmox 8.2.2. on my Dell R810.

Today I did an apt-get update;apt-get upgrade which ran normally.

After the above step, apt still reported that

The following packages have been kept back:
libpve-cluster-api-perl libpve-cluster-perl libpve-notify-perl libpve-rs-perl proxmox-kernel-6.8 pve-container pve-manager

I therefore ran

apt install libpve-cluster-api-perl libpve-cluster-perl libpve-notify-perl libpve-rs-perl proxmox-kernel-6.8 pve-container pve-manager

but now I get

apt install libpve-cluster-api-perl libpve-cluster-perl libpve-notify-perl libpve-rs-perl proxmox-kernel-6.8 pve-container pve-manager

Reading package lists… Done
Building dependency tree… Done
Reading state information… Done
Some packages could not be installed. This may mean that you have
requested an impossible situation or if you are using the unstable
distribution that some required packages have not yet been created
or been moved out of Incoming.
The following information may help to resolve the situation:

The following packages have unmet dependencies:
pve-container : Depends: proxmox-backup-client (>= 3.2.5-1) but 3.2.3-1 is to be installed
E: Unable to correct problems, you have held broken packages.

So it appears a default apt-get update;apt-get upgrade on Proxmox 8.2.2. has caused the proxmox-backup-client to become too new a version to be compatible with the pve-container currently available on the official Debian Bookworm proxmox repo?

What is my course of action here? What is the best thing to do?

Thanks!

Stefan

2

Hi Stefan,
I have zero experience with Proxmox so my suggestions may be off base.

When I see messages like these I believe it is due to one of the following possibilities:

  1. Several packages need to be upgrade at the same time, but not all of them have been pushed to the repos when you tried the upgrade.
  2. Some package version needs to be upgraded to a version that is not normally done by apt. (AFAIK it will upgrade a package but not replace with a newer major version in line with Debian Stable policies.)

The solution to the first is to wait for the remaining packages to be pushed to the repos.

Solution to the second is to run apt dist-upgrade. This is normally only used on Debian Testing/Sid, but I’m not familiar with how Proxmox manages their repos.

If your system is fully functional, I’d just wait for the situation to clear itself up. If you’re missing backup functionality … I’m less sure. I’d be inclined to revert to the situation as it was when apt reported held packages, assuming everything was still working at that point.

Lastly, does Proxmox running apt directly or does it have a custom tool for performing these actions? If the latter, I’d be inclined to stick with their built in stuff so as to avoid a "FrankenProxmox.)

best,

1 Like
3

Thank you HankB! Much obliged. I’ll consider what you said.

Appreciate the time taken to reply.

Kind regards

Stefan

4

This popped up on Mastodon - perhaps related?

2 Likes