You know, I never got into these issues with a Debian system installed from scratch. But after a knoppix-based install? My uneducated guess is that the "kitchen sink" involved adding some items that didn't follow Debian policy. Here is an example. The dvipdfm package required something that is no longer available from standard sources. So aptitude wants to remove it, and won't do anything else until it is removed. But if I try to remove either with aptitude or apt-get I run into trouble:
root@sarnassi:~# apt-get remove dvipdfm
Reading Package Lists... Done
Building Dependency Tree... Done
The following packages will be REMOVED:
dvipdfm
0 packages upgraded, 0 newly installed, 1 to remove and 0 not upgraded.
Need to get 0B of archives.
After unpacking 440kB disk space will be freed.
Do you want to continue? [Y/n]
(Reading database ... 102022 files and directories currently installed.)
Removing dvipdfm ...
Removing `diversion of /usr/share/texmf/tex/latex/graphics/dvipdfm.def to /usr/share/texmf/tex/latex/graphics/dvipdfm.def.tetex by dvipdfm'
dpkg-divert: rename involves overwriting `/usr/share/texmf/tex/latex/graphics/dvipdfm.def' with
different file `/usr/share/texmf/tex/latex/graphics/dvipdfm.def.tetex', not allowed
dpkg: error processing dvipdfm (--remove):
subprocess post-removal script returned error exit status 2
Errors were encountered while processing:
dvipdfm
E: Sub-process /usr/bin/dpkg returned an error code (1)
So, how do I get rid of it for real?
Thanks,
Ben