Comment 8 for bug 375825

Hi John; thanks for the response

I'm not sure whether or not this issue is purely a KVM issue, but I've gone from pillar to post in the various IRC channels (kvm, vibvirt, ubuntu-virt, qemu, etc), and every group indicated that it's not an issue in their domain.

As indicated above & in the forum, I've been able to work through the issue before by manually hacking the post-install script, and then reverting the KVM package to a earlier version, but now the problem is exacerbated, since the package manager tried to (re)install this critical update (regardless of whether or not the libvirt has been updated accordingly), and now I'm unable to do any further upgrades (I understand that this issue is not necessarily related to this "bug", but this is where my troubles have started)

As requested, herewith is my output from `dpkg -s sysv-rc`:

Package: sysv-rc
Status: install ok installed
Priority: required
Section: admin
Installed-Size: 264
Maintainer: Debian sysvinit maintainers <email address hidden>
Architecture: all
Source: sysvinit
Version: 2.86.ds1-38+etchnhalf.1
Replaces: file-rc, sysvinit (<< 2.85-1)
Recommends: lsb-base (>= 3.0-6)
Suggests: sysv-rc-conf, bum
Conflicts: file-rc
Description: System-V-like runlevel change mechanism
 This package provides support for the System-V like system
 for booting, shutting down and changing runlevels,
 configured through symbolic links in /etc/rc?.d/.

At present, this problem seems to look like a apt issue, so I'll try & address it from that angle first, before trying to hack KVM again.

Thanks