On Mon, Jan 18, 2010 at 08:31:16PM +0100, Salvo Tomaselli wrote:
> Try to do
> aptitude remove diff
>
> It looks like pretty dangerous
I guess you just found a bug in aptitude:
$ aptitude remove diff
...
The following ESSENTIAL packages will be REMOVED!
diff
WARNING: Performing this action will probably cause your system to break!
Do NOT continue unless you know EXACTLY what you are doing!
To continue, type the phrase "I am aware that this is a very bad idea":
Is this the output you see? If it is, then the bug is that aptitude
thinks that diff is still essential although the version in unstable is
not. This happens if you still have stable or oldstable in your
sources.list, although you run testing or sid.
Either without the stable lines in your sources.list or a fixed aptitude
the output should look like this:
$ aptitude remove diff
...
The following packages will be REMOVED:
diff{u} mktemp{u}
...
I'm not sure if this bug is already reported to aptitude. If it is not,
this bug should be reassigned, otherwise it should be closed.
Deborphan is right in showing diff and mktemp as possibly orphaned when
you pass --guess-dummy or --guess-all to it, since these are dummy
packages on your system.
Regards
Carsten
--
To UNSUBSCRIBE, email to [email protected]
with a subject of "unsubscribe". Trouble? Contact [email protected]
