Here is a patch against sysklogd for Jaunty. It works by removing the 'set -e' line in postrm so that this script does not exit on the first error.
Note that it is not bullet proof: if a non-patched Jaunty (or older) user upgrades to Karmic, this bug *will* trigger...
RFC: rsyslog should depend on an new, dummy, postrm-fixed, karmic-specific version of sysklogd. But how to get rid of this dummy sysklogd package then ?
Here is a patch against sysklogd for Jaunty. It works by removing the 'set -e' line in postrm so that this script does not exit on the first error.
Note that it is not bullet proof: if a non-patched Jaunty (or older) user upgrades to Karmic, this bug *will* trigger...
RFC: rsyslog should depend on an new, dummy, postrm-fixed, karmic-specific version of sysklogd. But how to get rid of this dummy sysklogd package then ?