On 01/09/2020 10.23, David C. Rankin wrote:
On 9/1/20 3:07 AM, Per Jessen wrote:
David C. Rankin wrote:
I just added a lock for the virtualbox-guest-x11 package and was then able to update without it attempting to install.
I'm not sure having zypper look at decide it wants to install extra packages in this type situation is a good thing. If somebody installs virtualbox from openSUSE, then that packages is added as a dependency to begin with.
However, if the user has installed virtualbox from another source, then this package should be no more than a "recommends", not something that will evade the --no-recommends option requiring a full lock to prevent the thing -- that was not asked for to begin with -- from installing.
It is difficult to imagine how zypper should/could deal with that. Change a package dependency due to what a user may or may not have done ?
Precisely why when zypper says "Hey, not my Virtualbox!", it shouldn't have tried to do anything, but that isn't what happened. After finding a virtualbox that wasn't zypper's zypper went ahead a tried to add packages to it anyway -- that is the problem. It shouldn't have, but it did.
No, zypper only reacts to rpms. If you install an rpm in any manner, zypper reacts. Well, there is a manner in which it doesn't, but I'm sure you did not use it. -- Cheers / Saludos, Carlos E. R. (from 15.1 x86_64 at Telcontar)