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

[Manuel A. Fernandez Montecelo]

Control: fixed -1 aptitude/0.7.6-1
Control: close -1


Hi Manuel :-)


2014-01-12 10:56 Manuel Bilderbeek:
>Package: aptitude
>Version: 0.6.8.2-1.2
>Severity: normal
>
>Dear Maintainer,
>
>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 expect that in this situation also
>the old package should not be removed after all as no new (conflicting)
>package is going to be installed.

I believe that this has been fixed in 0.7.6-1, with sequences of actions
being more strict and aborting in the face of failures:

  * Abort with Failure (rather to continue with the installation) when packages
    fail to be fetched -- except if APT::Get::Fix-Missing is present and set to
    true.  When this happens, the actions in the command line also return with
    non-zero status.  (Closes: #121313, #302784)

  * [cmdline] Abort with Failure when actions cannot be taken
    (Closes: #121313, #430392, #445034, #498239, #576212, #639789, #798320)

    The Closes of #121313 overlap with other fixes, there are reports of each
    case merged.


If you find the problem again, please reopen.


Cheers.
-- 
Manuel A. Fernandez Montecelo <manuel.montezelo at gmail.com>