[Aptitude-devel] Bug#735050: Bug#735050: aptitude: Continues to remove conflicting package, although new package failed to download

[Axel Beckert]

Control: severity -1 wishlist

Hi,

Manuel Bilderbeek wrote:
> I asked aptitude to install a new package, which conflicted with an
> older package. So, it suggested to remove that package. So far so good.
> However, the new package failed to download (some transient network
> error). But to my surprise, the conflicting older package was still
> removed. End result: no new and no old package installed...
> 
> I think this is wrong behaviour.

I see the point, but I'm actually not sure if that behaviour would be
inconsistent from other points of view. At least the described
behaviour sounds "consistent" and "expected" to me.

So I consider such a behaviour rather as new feature than as real bug.
(Hence downgrading to severity "wishlist".)

But maybe I'm biased by being used to how aptitude works now, so I
would love to hear other opinions, e.g. from APT developers.

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