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. How would zypper INSIDE the VM know what virtualbox you have installed on the host machine? Zypper does not and should not care about that, all it sees is that
On 9/1/20 10:23 AM, David C. Rankin wrote: there is a device for which it has a driver available and it is installed. -- Benjamin Zeller <bzeller@suse.de> Systems Programmer SUSE Software Solutions Germany GmbH, Maxfeldstr. 5, 90409 Nuremberg, Germany Tel: +49-911-74053-0; Fax: +49-911-7417755; https://www.suse.com/ (HRB 36809, AG Nürnberg) Managing Director: Felix Imendörffer -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org