Comment 7 for bug 1022102

Wesley, your issue is unrelated to the original reported here (though the symptoms are similar). It _may_ be a bug and so require it's own report. As your report contains details only of aptitude's behaviour, please note that safe-upgrade is not guaranteed to find any solution and it is *not* a bug simply because it fails and you must use full-upgrade. However, if apt-get upgrade finds an upgrade path given the same situation then this has grounds to be looked at.

If you experience the problem in other programs also (such as muon) then it is not likely to be a bug in either, but rather to do with some combination of your configuration, the archive, and the particular relationships between the packages involved.