Comment 18 for bug 990740

How do upgrade bugs like this even exist? Does nobody at Canonical actually test upgrades? Of course somebody must be, but what kind of unused/minimalist systems were they upgrading that they didn't even have python-minimal installed?

Between this and the libsasl upgrade debacle it really makes one wonder what kind of minimal upgrade testing is actually done. Clearly this is an area that needs some work.

I wonder if some kind of "will this system upgrade" test can be constructed that doesn't actually do an upgrade but tests for dependency breakage (so that people who are not ready to jump full on into a beta test can at least do this kind of test and report problems) prior to a full release.