Comment 10 for bug 503765

Everything is from precise. Namely

aptitude 0.6.6 compiled at Mar 30 2012 17:19:20
Compiler: g++ 4.6.3
Compiled against:
  apt version 4.12.0
  NCurses version 5.9
  libsigc++ version: 2.2.10
  Ept support enabled.
  Gtk+ support disabled.
  Qt support disabled.

Current library versions:
  NCurses version: ncurses 5.9.20110404
  cwidget version: 0.5.16
  Apt version: 4.12.0

To see the 'wrong' behavior I am running just 'aptitude install'

The point is exactly that there should be no marked/scheduled changes waiting in aptitude at this point...

If I clean up the scheduled changes in aptitude, then I work for some time (say 1 month) without using aptitude, but just apt-get, synaptic, or apper and after 1 month I go back to saying 'sudo aptitude install', then aptitude shows that mess, probably due to the fact that it is being confused by something that happened behind it shoulders.

IMHO this is dangerous. If some user says 'sudo aptitude install' and then Y, he risks messing up all of its applications, possibly even loosing his desktop due to the funny ways that aptitude proposes to solve imaginary issues in this case.