On Wed, Apr 01, 2015 at 09:18:56PM -0300, Felipe Sateler wrote: > Package: apt > Version: 1.0.9.7 > Severity: normal > > > I believe a cli-shot is clearer than trying to explain: > > % sudo apt upgrade > [sudo] password for felipe: > Reading package lists... Done > Building dependency tree > Reading state information... Done > Calculating upgrade... Done > The following packages have been kept back: > wine wine-bin:i386 wine32:i386 wine64 > 0 upgraded, 0 newly installed, 0 to remove and 4 not upgraded. Try: apt upgrade -o Debug::pkgProblemResolver=1 -s My guess is that it includes a "Policy breaks with upgrade of" message, which is apt-speak for: A recommends relation isn't satisfied anymore after this upgrade. As recommends are supposed to be installed by default and more importantly you could loose features by having a recommends no longer satisfied upgrade isn't doing this upgrade as its supposed to do only 'safe' things. dist-upgrade on the other hand has no problem with breaking recommends. So, assuming I am right, the real question is why one of the wine packages has a recommends which isn't satisfiable (currently?). I presume dist-upgrade (at least in apt, the usual difficulties with changing apt-get apply) should grow a "unsatisfied recommends" display. I think aptitude has it too, but apt-get has this display for sure while install(ing) packages. Its showing suggests in this view too, through, that is probably a bit much given that they aren't installed by default and dist-upgrade potentially touches thousands of packages so that could end up being thousands of unsatisfied suggests – but the list of unsatisfied recommends is ideally very small if not zero. One complication through: Upgrading packages considers new vs. old unsatisfied recommends and installs new recommends, while leaving the old ones uninstalled, so such a list might want to consider that as well. Best regards David Kalnischkies
Attachment:
signature.asc
Description: Digital signature