[Aptitude-devel] Bug#836263: Bug#836263: aptitude: safe-upgrade removes dirmngr and gnupg-l10n

[Axel Beckert]

Hi Sven,

Sven Joachim wrote:
> After a recent upload of gnupg in unstable the following happens: 
> 
> ,----
> | $ LANG=C aptitude -s -V -D safe-upgrade
> | Resolving dependencies...                
> | The following packages will be REMOVED:
> |   dirmngr{u} [2.1.14-5] (R: gnupg)  gnupg-l10n{u} [2.1.14-5] (R: gnupg)  
> | The following packages will be upgraded:
> |   gpgv [2.1.14-5 -> 2.1.15-2]  
> | 1 packages upgraded, 0 newly installed, 2 to remove and 11 not upgraded.
> | Need to get 365 kB of archives. After unpacking 5112 kB will be freed.
> | 
> | Note: Using 'Simulate' mode.
> | Do you want to continue? [Y/n/?] 
> | Would download/install/remove packages.
> `----
> 
> Short analysis: both the old (2.1.14-5) and the new (2.1.15-2) version
> of gnupg have a strictly versioned Recommends on dirmngr and gnupg-l10n.
> The new gnupg version is not installable because it Breaks python-apt,
> but dirmngr and gnupg-l10n could be upgraded.  However, their new
> versions become unused and so aptitude removes them

So far I completely agree.

> which is clearly suboptimal (they should rather be held back to not
> break the gnupg Recommends).

I only noticed it during a dist-upgrade, I was (and am) fine with that
solution for a full-/dist-upgrade. But I couldn't reproduce it with a
safe-upgrade. Then again, there are currently way more Breaks
influencing my system's upgrade than the one you mention, so probably
a non-comparable case.

But I agree, that this shouldn't happen on a safe-upgrade.

		Regards, Axel
-- 
 ,''`.  |  Axel Beckert <abe at 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