Package: xymon Severity: serious Version: 4.3.30-2 Tags: pending Due to a superfluous leftover debconf initialisation in xymon.postinst not being removed with the cleaning up of old transition code, upgrading xymon (but not xymon-client) resulted in a hanging upgrade process as well as in a xymon.postinst zombie process.
A fix is committed locally and I'll upload soon, but it still needs some more testing how to handle further, but more harmless leftovers from that incomplete code removal. Filing this bug mostly due to several transitions (well, mostly t64 transitions) being listed on https://tracker.debian.org/pkg/xymon to make clear why an upload is currently necessary. -- System Information: Debian Release: trixie/sid APT prefers unstable APT policy: (990, 'unstable'), (600, 'testing'), (500, 'unstable-debug'), (500, 'buildd-unstable'), (110, 'experimental'), (1, 'experimental-debug'), (1, 'buildd-experimental') Architecture: amd64 (x86_64) Foreign Architectures: i386 Kernel: Linux 6.6.13-amd64 (SMP w/8 CPU threads; PREEMPT) Kernel taint flags: TAINT_WARN Locale: LANG=C.UTF-8, LC_CTYPE=C.UTF-8 (charmap=UTF-8), LANGUAGE not set Shell: /bin/sh linked to /usr/bin/dash Init: sysvinit (via /sbin/init) LSM: AppArmor: enabled