Package: prometheus-node-exporter-collectors
Version: 0.0~git20231018.f5c56e7-1
Severity: important
Dear Maintainer,
* What led up to the situation?
Upgraded to 0.0~git20231018.f5c56e7-1 version of the package
* What was the outcome of this action?
On a "Debian testing" machine with currently 9 packages upgradable and 3 held
packages :
apt list --upgradable
Listing... Done
fonts-urw-base35/testing,unstable 20200910-8 all [upgradable from: 20200910-7]
gsfonts-x11/testing,unstable 2:20200910-8 all [upgradable from: 2:20200910-7]
gsfonts/testing,unstable 2:20200910-8 all [upgradable from: 2:20200910-7]
libgif7/testing,unstable 5.2.2-1 amd64 [upgradable from: 5.2.1-2.5+b1]
libsensors-config/testing,unstable 1:3.6.0-9 all [upgradable from: 1:3.6.0-8]
libsensors5/testing,unstable 1:3.6.0-9 amd64 [upgradable from: 1:3.6.0-8+b1]
lm-sensors/testing,unstable 1:3.6.0-9 amd64 [upgradable from: 1:3.6.0-8+b1]
mmdebstrap/testing,unstable 1.4.3-6 all [upgradable from: 1.4.3-4]
partclone/testing,unstable 0.3.27+repack-2 amd64 [upgradable from:
0.3.27+repack-1]
apt-mark showhold
kodi
kodi-bin
kodi-data
apt_info.py reports upgradable packages as as "held" :
/usr/share/prometheus-node-exporter-collectors/apt_info.py
# HELP apt_upgrades_held Apt packages pending updates but held back.
# TYPE apt_upgrades_held gauge
apt_upgrades_held{arch="all",origin="Debian:sid/unstable,Debian:trixie/testing"}
5.0
apt_upgrades_held{arch="amd64",origin="Debian:sid/unstable,Debian:trixie/testing"}
4.0
# HELP apt_autoremove_pending Apt packages pending autoremoval.
# TYPE apt_autoremove_pending gauge
apt_autoremove_pending 2.0
# HELP apt_package_cache_timestamp_seconds Apt update last run time.
# TYPE apt_package_cache_timestamp_seconds gauge
apt_package_cache_timestamp_seconds 0.0
# HELP node_reboot_required Node reboot is required for software updates.
# TYPE node_reboot_required gauge
node_reboot_required 0.0
* What outcome did you expect instead?
I expect instead to see apt_upgrades_pending info like this :
...
apt_upgrades_pending{arch="all",origin="Debian:sid/unstable,Debian:trixie/testing"}
5.0
apt_upgrades_pending{arch="amd64",origin="Debian:sid/unstable,Debian:trixie/testing"}
4.0
...
and the right number of held packages :
...
apt_upgrades_held{arch="amd64",origin="Debian:sid/unstable,Debian:trixie/testing"}
3.0
...
Note : 0.0~git20230203.6f710f8-1 version reports apt_upgrades_pending correctly
(5 + 4) but reports 0 apt_upgrades_held packages
-- System Information:
Debian Release: trixie/sid
APT prefers stable-updates
APT policy: (500, 'stable-updates'), (500, 'stable-security'), (500,
'testing'), (500, 'stable')
Architecture: amd64 (x86_64)
Kernel: Linux 6.6.15-amd64 (SMP w/8 CPU threads; PREEMPT)
Kernel taint flags: TAINT_PROPRIETARY_MODULE, TAINT_OOT_MODULE,
TAINT_UNSIGNED_MODULE
Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8),
LANGUAGE=en_US:en
Shell: /bin/sh linked to /usr/bin/dash
Init: systemd (via /run/systemd/system)
LSM: AppArmor: enabled
Versions of packages prometheus-node-exporter-collectors depends on:
ii moreutils 0.69-1
ii prometheus-node-exporter 1.7.0-1+b1
ii python3-apt 2.7.6
ii python3-prometheus-client 0.19.0+ds1-1
ii systemd-sysv 255.3-2
Versions of packages prometheus-node-exporter-collectors recommends:
ii ipmitool 1.8.19-7
ii jq 1.7.1-2
ii nvme-cli 2.8-1
ii python3 3.11.6-1
ii smartmontools 7.4-2
prometheus-node-exporter-collectors suggests no packages.
-- no debconf information
