Marcus Meissner writes:
On Fri, Aug 05, 2011 at 01:26:45PM +0200, Joachim Schrod wrote:
What I would really like to have: A zypper or zypp.conf option "don't list non-updateable packages caused by irrelevant vendor changes" in the "will NOT be installed" list at zypper update. Irrelevant here means: The package would change vendor and all its dependencies could be installed. Then the admin probably didn't install it by choice.
Currently, I have to do the dependency analysis to distinguish these two cases myself, and also haven't yet found good tools in the zypper framework that tells me concisely "why could something not be installed".
You can always check with a direct zypper in why zypper thinks it would be a bad idea to install them:
zypper in NetworkManager-kde4-libs which will likely print the reason of why not.
Very good point, almost always that helps, or at least gives sufficient information what one has to look for in /var/log/zypper.solverTestCase/*. Thanks for pointing that out, Joachim -- =-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=- Joachim Schrod Email: jschrod@acm.org Roedermark, Germany -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org