Sounds familiar, yes. Happens occassionally, probably only if
versioned alternative dependencies in combination with conflicts are
involved. Which exists a bunch of times in Debian, but you probably
can count the cases on two hands.
(IMHO only a minor issue easy to workaround interactively, but I'll
leave it on normal and would like to hear Manuel's opinion on it.)
> This choice is surprising.
Not really. At that moment neither of the two alternative versioned
dependencies are fulfilled, hence it tries to fulfill the first
alternative dependency. The remainder seems to be a "local optimum"
issue it doesn't find to escape itself in time. It probably will find
the right solution later if you continue to request alternative
dependency solutions with ".".
Regards, Axel
--
,''`. | Axel Beckert <a...@debian.org>, https://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