Comment 48 for bug 328089

I just helped a confused user through this. It's important to note that none of the GUI package installation utilities is able to recover from this failure case to the point that the user can use the APT/dpkg subsystem any more without command-line twiddling.

I understand and support the effort to fix lsb-base to make Splashy work, but at the same time I feel it's disappointing and just plain wrong that we are shipping two Ubuntu releases with an obviously known-broken package that will blow up the GUI package managers that non-technically-inclined users like to use.

In the interim, can we agree on some mitigating solution to block users from installing the broken package? If we can't yank it out of the archive, SRU it without the lsb-logging-base.sh file? SRU it to a blank package or one that the package manager refuses to install?