[Aptitude-devel] Bug#836708: aptitude: refuses to upgrade packages, 'g' says "Actions: no changes"

[Manuel A. Fernandez Montecelo]

Control: tags -1 + wontfix
Control: close -1


Hi,

2016-09-05 01:50 Vincent Lefevre:
>Package: aptitude
>Version: 0.8.3-1
>Severity: normal
>
>In the UI, I've selected various packages for upgrade; I can see
>no breakages. But the 'g' key doesn't have any effect, it just
>says: "[1(1)/...] Actions: no changes" with no explanations.

That means that the currently selected action is "no changes" (== cancel
install actions, for example).


>Quitting aptitude and retarting it doesn't solve the problem.
>Neither does trying "Next".
>
>Here's the log from
>
>  aptitude --log-file=/tmp/aptitude.log --log-level=info
>
>2016-09-05 01:43:58 [139874063632256] temp.cc:207 INFO aptitude.temp - Initialized the temporary file module using the base directory /tmp/aptitude-root.18653:XjDwmS
>2016-09-05 01:43:58 [139874063632256] apt.cc:329 INFO aptitude.apt.globals - Closing apt cache.
>2016-09-05 01:43:58 [139874063632256] apt.cc:398 INFO aptitude.apt.globals - Loading apt cache.
>2016-09-05 01:44:02 [139874063632256] problemresolver.h:3804 INFO aptitude.resolver.search - Initially broken dependency: libmtp9:amd64 1.1.12-1 -S> {libmtp-runtime:amd64 1.1.12-1 libmtp-runtime:amd64 1.1.8-1+b1}

^^^^
this


2016-09-05 02:33 Vincent Lefevre:
>On 2016-09-05 01:50:04 +0200, Vincent Lefevre wrote:
>> In the UI, I've selected various packages for upgrade; I can see
>> no breakages. But the 'g' key doesn't have any effect, it just
>> says: "[1(1)/...] Actions: no changes" with no explanations.
>
>And 'e' (Examine) just says:
>
>  --\ Leave the following recommendations unresolved:
>    libmtp9 recommends libmtp-runtime
>
>libmtp9 recommends libmtp-runtime
>--\ The following actions will resolve this dependency:
>  -> Cancel the removal of libmtp-runtime
>  -> Downgrade libmtp-runtime [1.1.12-1 (now, testing, unstable) -> 1.1.8-1+b1 (
>  -> Leave the dependency "libmtp9 recommends libmtp-runtime" unresolved.
>
>which makes no sense since nothing related to libmtp is proposed.

This was implemented after your complaint in #819636 (not upgrading
"lightly" if it means breaking a recommend relationship), which then
needed #822329 to not be so eager on fixing unfulfilled recommends.

So you just need to acknowledge the missing recommends with '!' to
continue with the installation (or select a different solution).

Relevant entries in the NEWS file:

  * Actions involving unfulfilled Recommends invoke the resolver
    (Closes: #819636)

    With APT::Install-Recommends="true" (the default), actions resulting in
    unavailable Recommends (e.g., the recommended package is upgraded instead of
    remaining in the required version) invoke the resolver, for the user to take
    decision.

  * Invoke the resolver for unfulfilled Recommends only once (Closes: #822329)

    After the fix for #819636, the resolver was invoked after every action taken
    (in curses mode) to see if there were any unfulfilled dependencies.  This is
    too slow for some people/systems, so this is now only invoked will full
    check of dependencies (Recommends / "soft deps") before the final action.


So marking as +wontfix (for the lack of not-a-bug).


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