apt wants to remove itself

[Axel Beckert <abe@debian.org>]

Hi,

JFYI: while testing aptitude built against apt 1.1~exp9 I experienced
the following:

I've installed aptitude, aptitude-common and aptitude-dbg with "dpkg
-i". Then I added experimental to sources.list, ran "apt update".

And then I ran "apt install -f" and was surprised about the outcome:

root@c-cactus2:/tmp# apt install -f                 
Reading package lists... Done
Building dependency tree       
Reading state information... Done
Correcting dependencies... Done
The following extra packages will be installed:
  libapt-pkg5.0
The following packages will be REMOVED:
  apt
The following NEW packages will be installed:
  libapt-pkg5.0
WARNING: The following essential packages will be removed.
This should NOT be done unless you know exactly what you are doing!
  apt
0 upgraded, 1 newly installed, 1 to remove and 0 not upgraded.
2 not fully installed or removed.
Need to get 0 B/750 kB of archives.
After this operation, 749 kB disk space will be freed.
You are about to do something potentially harmful.
To continue type in the phrase 'Yes, do as I say!'
 ?] 

I thought that apt considers itself essential and hence I'd rather
expected it to upgrade itself in favour of removing itself. Or does
the "fix mode" work differently with regards to this?

Aaaaand, I wonder (once again :-) if we should add a dependency from
aptitude to apt for the download methods which reside in the package
apt.

		Regards, Axel
-- 
 ,''`.  |  Axel Beckert <abe@debian.org>, http://people.debian.org/~abe/
: :' :  |  Debian Developer, ftp.ch.debian.org Admin
`. `'   |  4096R: 2517 B724 C5F6 CA99 5329  6E61 2FF9 CD59 6126 16B5
  `-    |  1024D: F067 EA27 26B9 C3FC 1486  202E C09E 1D89 9593 0EDE