Package: runit Version: 1.8.0-4 Severity: critical Justification: breaks unrelated software
Upgrading from runit 1.8.0-2 to 1.8.0-4 fails. It seems to restart user processes, including the one that is doing the upgrade. The first time it kicked me out of X. It leaves dpkg/apt in an unusable and unrecoverable state. Symptom: # apt-get upgrade E: dpkg was interrupted, you must manually run 'dpkg --configure -a' to correct the problem. # dpkg --configure -a Setting up runit (1.8.0-4) ... Debian GNU/Linux lenny/sid recycle tty5 recycle login: First, I would respectfully request advice on how to recover apt/dpkg state. Do you think downgrading to 1.8.0-2 will work? Hmm, I left a non-runit-managed console around, maybe I can try dpkg --configure -a from there. Second, if there are any experiments I can do to isolate the problem, let me know. Nothing showed up in dmesg from the process shown above. -- System Information: Debian Release: lenny/sid APT prefers unstable APT policy: (500, 'unstable') Architecture: amd64 (x86_64) Kernel: Linux 2.6.24-1-amd64 (SMP w/1 CPU core) Locale: LANG=en_US, LC_CTYPE=en_US (charmap=ISO-8859-1) Shell: /bin/sh linked to /bin/bash runit depends on no packages. Versions of packages runit recommends: pn fgetty <none> (no description available) -- no debconf information -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
