Ok - I did zypper up from terminal and it updated the kernel and then zypper up and zypper dup did not update anything. Uname -a gives me that the kernel in use is 3.14. Te question is what kernel was updated?
And you will continue to see that 3.11 update waiting to go, as I do, but it will not be installed when you zypper dup. It’s a known idiosyncrasy of Tumbleweed.
Oh, now I see. You regard the kernel “3.11 update messages” as a symptom of “not working”. I suppose technically correct, because the scripting that deals with it from 13.1 standard is confused by the different kernel naming by Tumbleweed. So we live with the harmless messages if we don’t want to install an old kernel [by Tumbleweed’s standards].
On 2014-05-15 16:56, consused wrote:
>
> And you will continue to see that 3.11 update waiting to go, as I do,
> but it will not be installed when you zypper dup. It’s a known
> idiosyncrasy of Tumbleweed.
The funny thing is that the terminal showed me that it was updated, the update messages stoppped to pop out and the kernel in use is sitill the latest 3.14.
If you have Kernel 3.11.6 installed, libzypp wants to install the update to 3.11.10 for this, no matter what the highest kernel version is that you have installed.
I suppose you could also uninstall both 3.11.x kernels instead.
Or tabooing the patch itself (in YaST->Online Update’s left list) should prevent that update to be shown as well (maybe you have to taboo the kernel-3.11.10 package as well).
But I don’t know for sure as I don’t use Tumbleweed/an updated Kernel from a different repo.
Tabooing the patch didn’t work last time I tried it wrt to preventing the update message.
How to taboo a specific kernel version using YaST? The Version tab lets you click on each version, but only toggles a tick or a cross against it, nothing else it seems.
You would have to edit /etc/zypp/locks manually with a text editor then, or use “zypper addlock”. You can lock specific package versions there.
Something like this should do I suppose:
type: package
match_type: exact
case_sensitive: on
solvable_name: kernel-desktop < 3.12
Hm, strange enough, if you add such a lock with “zypper addlock” (or by editing the file manually), YaST will actually correctly show the versions locked in the “Versions” tab and you can even remove the locks for specific versions there (although that doesn’t work really, they will be back on restart).
And it doesn’t allow to set the version-specific locks in the first place… You can only lock/unlock a package completely in YaST.
Today I made virtual machine openSUSE 13.1 from DVD iso without updating during installation process.
After finishing I disabled all repositories, add Kernel stable repository http://download.opensuse.org/repositories/Kernel:/stable/standard and made updating to actual stable kernel 3.15.6.
Then I enabled previously disabled repositories, inserted command zypper dup into terminal and saw that system wanted to install kernel 3.11.10.
So I decided to uninstall kernel 3.11.6. This did not help. Updating still insisted on installation of kernel 3.11.10.
I noticed during uninstallation of kernel 3.11.6, that virtualbox-guest-kmp and virtualbox-host-kmp packages went out also. This packages depends on kernel version.
So I added repository VirtualBox [FONT=Arial][size=2]http://download.opensuse.org/repositories/Virtualization/Kernel_stable_standard.
After this updating was OK, without need for [/FONT][/size]kernel 3.11.10.