I do not know where to post this, so chose Virtualisation. Sorry if I have got it wrong.
I have run 13.2 since not long after it’s release. I am not exactly new to Linux or to openSuse, but for command line I have to follow instructions. On installation I activated virtualbox build service in the repo’s. About a month ago the update app (zypper?) said I had 4 updates for virtualbox - guest and host default and desktop. On install I get
There is no update candidate for virtualbox-guest-kmp-default-4.3.20_k3.16.7_7-127.5.x86_64
This error shows up for all updates once each is progressively disabled in the app.
Using yast update and search for virtualbox, I updated the system to
virtualbox-guest-kmp-default-4.3.20_k3.16.7_7-127.7.x86_64
Immediately the app stated I had 4 virtualbox updates, but the same error occurred on installing.
There is no update candidate for virtualbox-guest-kmp-default-4.3.20_k3.16.7_7-127.7.x86_64
So every time there is an update I have to de-activate the virtualbox updates the app tells me I have, in order to install the genuine ones. Does not matter if virtualbox build service is de-activated in the repo’s or not. How do I get out of this loop?
Sorry it’s been so long winded.
Richard
Well, I could think of two options right now:
- remove the Virtualization repo and install virtualbox from the standard repos instead (use YaST’s “Versions” tab to switch). Then you shouldn’t have a problem installing the update (which is the same version as virtualbox in the Virtualization repo anyway).
- right-click on the virtualbox update in YaST->Online Update (on the left side) and choose “Taboo - Never install” to prevent that update from being installed.
Btw, why do you have virtualbox-xxx-kmp-desktop and -default installed?
Which kernel are you actually using? (uname -a)
You could remove the other kernel and the corresponding virtualbox kmp packages.
Maybe just removing virtualbox-xxx-kmp-default would “fix” your problem already?
Also, the output of “zypper up” would be interesting. That would provide more information about the conflict that prevents the update from being installed successfully. PackageKit is not really good in solving dependency conflicts and its error messages are quite lacking on details as well.
Thank you. The learning process is never complete!
Kernal is
Linux openSuse 3.16.7-7-desktop #1 SMP PREEMPT Wed Dec 17 18:00:44 UTC 2014 (762f27a) x86_64 x86_64 x86_64 GNU/Linux. After running zypper up.
Result of uname -a
Why desktop and default are both installed I do not know. Obviously something I ‘clicked’ on.
I ran zypper up in a terminal. It could not find the files required and asked if I wanted to change. Did a Yes. Re-booted and I don’t get the install update messages now. Have also deleted the virtualbox build service from the repo list.
zypper up will go in my ‘do not forget’ folder.
Thanks again.
Richard
As I said, you could remove kernel-default (and the corresponding kmp-default packages). You are running kernel-desktop anyway.
I ran zypper up in a terminal. It could not find the files required and asked if I wanted to change. Did a Yes.
It probably asked you for a vendor change.
As I said, PackageKit doesn’t really support solving conflicts, as it is a cross-distribution tool. If it sees a problem, it just aborts.
Re-booted and I don’t get the install update messages now. Have also deleted the virtualbox build service from the repo list.
zypper up will go in my ‘do not forget’ folder.
A further explanation: “zypper up” basically does the same as the update applet. It refreshes all configured repos, and offers to install all updated packages it finds. It does also respect the vendor though, so it will not switch packages to versions from different repos automatically (unless it is necessary, but even then it asks the user).
I just suggested it, because it will give more detailed messages in case of conflicts/problems, and allows the user to solve them.
Have deleted both ‘default’ kernels. Everything working well. I now know what PackageKit and Zypper are. I’m slowly getting there.
Once again, thanks very much for your help.
Richard