• Bug#1067110: xymon: Upgrade process hangs with zombie in postinst

    From Axel Beckert@21:1/5 to All on Mon Mar 18 16:10:02 2024
    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

    --- SoupGate-Win32 v1.05
    * Origin: fsxNet Usenet Gateway (21:1/5)
  • From Debian Bug Tracking System@21:1/5 to All on Wed Mar 27 02:10:01 2024
    This is a multi-part message in MIME format...

    Your message dated Wed, 27 Mar 2024 01:06:41 +0000
    with message-id <E1rpHkX-003W1l-1l@fasolo.debian.org>
    and subject line Bug#1067110: fixed in xymon 4.3.30-3
    has caused the Debian Bug report #1067110,
    regarding xymon: Upgrade process hangs with zombie in postinst
    to be marked as done.

    This means that you claim that the problem has been dealt with.
    If this is not the case it is now your responsibility to reopen the
    Bug report if necessary, and/or fix the problem forthwith.

    (NB: If you are a system administrator and have no idea what this
    message is talking about, this may indicate a serious mail system misconfiguration somewhere. Please contact owner@bugs.debian.org
    immediately.)


    --
    1067110: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1067110
    Debian Bug Tracking System
    Contact owner@bugs.debian.org with problems

    Received: (at submit) by bugs.debian.org; 18 Mar 2024 15:00:07 +0000 X-Spam-Checker-Version: SpamAssassin 3.4.6-bugs.debian.org_2005_01_02
    (2021-04-09) on buxtehude.debian.org
    X-Spam-Level:
    X-Spam-Status: No, score=-16.7 required=4.0 tests=BAYES_00,
    BODY_INCLUDES_PACKAGE,FOURLA,FROMDEVELOPER,HAS_PACKAGE,
    HEADER_FROM_DIFFERENT_DOMAINS,SPF_HELO_NONE,SPF_NONE,
    T_SCC_BODY_TEXT_LINE,X_DEBBUGS_CC autolearn=ham autolearn_force=no
    version=3.4.6-bugs.debian.org_2005_01_02
    X-Spam-Bayes: score:0.0000 Tokens: new, 9; hammy, 150; neutral, 98; spammy, 0.
    spammytokens: hammytokens:0.000-+--trixie, 0.000-+--cutf8,
    0.000-+--CUTF8, 0.000-+--c.utf-8, 0.000-+--C.UTF-8
    Return-path: <abe@c6.deuxchevaux.org>
    Received: from sym.noone.org ([2a01:4f8:120:4161::3]:37988 helo=sym2.noone.org)
    by buxtehude.debian.org with esmtps (TLS1.2:ECDHE_X25519__RSA_SHA512__AES_256_G