upgrade inconsistencies in pbs webui - why does it show libglusterfs-dev ?

[RolandK]

i have pbs installed on top of pve

when running apt update in pbs, there is a difference of 1 package shown, i.e. in pbs webui,

why is libglusterfs-dev shown here ?

this looks weird

 

[RolandK]

for my curiousity, the gluster package is no longer shown after upgrading the other 2 packages

and i don't have any libglusterfs-dev installed

maybe this could be a parsing bug in pbs webui ?

root@pbsvm:/tmp# apt upgrade
Reading package lists... Done
Building dependency tree... Done
Reading state information... Done
Calculating upgrade... Done
The following packages will be upgraded:
pve-i18n pve-qemu-kvm
2 upgraded, 0 newly installed, 0 to remove and 0 not upgraded.
Need to get 28.7 MB of archives.
After this operation, 14.3 kB of additional disk space will be used.
Do you want to continue? [Y/n] Y
Get:1 http://download.proxmox.com/debian/pve bookworm/pve-no-subscription amd64 pve-i18n all 3.1.5 [359 kB]
Get:2 http://download.proxmox.com/debian/pve bookworm/pve-no-subscription amd64 pve-qemu-kvm amd64 8.1.2-6 [28.3 MB]
Fetched 28.7 MB in 1s (42.4 MB/s)
Reading changelogs... Done
(Reading database ... 79277 files and directories currently installed.)
Preparing to unpack .../pve-i18n_3.1.5_all.deb ...
Unpacking pve-i18n (3.1.5) over (3.1.4) ...
Preparing to unpack .../pve-qemu-kvm_8.1.2-6_amd64.deb ...
Unpacking pve-qemu-kvm (8.1.2-6) over (8.1.2-5) ...
Setting up pve-qemu-kvm (8.1.2-6) ...
Setting up pve-i18n (3.1.5) ...
Processing triggers for man-db (2.11.2-2) ...
Processing triggers for mailcap (3.70+nmu1) ...

root@pbsvm:/tmp# dpkg --list|grep gluster
ii glusterfs-client 10.3-5 amd64 clustered file-system (client package)
ii glusterfs-common 10.3-5 amd64 GlusterFS common libraries and translator modules
ii libglusterd0:amd64 10.3-5 amd64 GlusterFS glusterd shared library
ii libglusterfs0:amd64 10.3-5 amd64 GlusterFS shared library

 

[RolandK]

opened bugticket

https://bugzilla.proxmox.com/show_bug.cgi?id=5134

 

[fabian]

possibly something got confused there because pve-qemu-kvm depends on either libglusterfs-dev or glusterfs-common, and the code tries to also list dependencies that would be newly installed cause of the upgrade. it doesn't know about alternate dependencies like that, so if you have glusterfs-common installed, apt will use that to satisfy the dependency, but our upgrade check doesn't, so it will falsely list libglusterfs-dev.

 

[RolandK]

yeah, but why does pve gui and apt commandline behave different from pbs gui ?

after upgrade, i don't see that libglusterfs-dev is being installed.

and even if it would have been installed, it makes no sense to me, as libglusterfs-dev is a package for development, not for runtime

 

[fabian]

PBS and PVE use different code (and both use bindings to libapt, but don't do a full upgrade resolution like "apt" the binary does)

edit: to explain more

pve-qemu-kvm has a dependency on "libglusterfs-dev | glusterfs-common (>= 5.6)" (among other things). this was required because at some point the upstream glusterfs packages messed up their packaging and were incompatible with the regular Debian packages. "apt" when calculating upgrades in "apt dist-upgrade" will see that "glusterfs-common" is installed, and not also install libglusterfs-dev (or vice-versa, if you have libglusterfs-dev installed but not glusterfs-common). but when we try to determine upgradable packages up front using libapt, we get back "package pve-qemu-kvm is upgradable" and when we then look at the dependencies of that package to see if all of them are installed, or something new would be pulled in, we just get a list, but the information that some of the dependencies are alternate dependencies where one of them being installed/satisfied is enough is lost.

 

[RolandK]

thanks for explaining it. very valuable !

so, essentially , can this be called a "missing feature" in pbs rust/apt subroutines to properly resolve (and thus skip) fulfilled alternate dependencies ?

here ?
https://github.com/proxmox/proxmox-backup/blob/master/src/tools/apt.rs#L150

 

[fabian]

yeah, I'll re-open the bug, but it won't be high priority to fix since it's mostly cosmetic..