http://bugzilla.opensuse.org/show_bug.cgi?id=1037700 http://bugzilla.opensuse.org/show_bug.cgi?id=1037700#c2 --- Comment #2 from John Shand --- Created attachment 723904 --> http://bugzilla.opensuse.org/attachment.cgi?id=723904&action=edit Dmesg info -- You are receiving this mail because: You are on the CC list for the bug.

http://bugzilla.opensuse.org/show_bug.cgi?id=1037700 http://bugzilla.opensuse.org/show_bug.cgi?id=1037700#c4 --- Comment #4 from John Shand --- Created attachment 723906 --> http://bugzilla.opensuse.org/attachment.cgi?id=723906&action=edit HW Information -- You are receiving this mail because: You are on the CC list for the bug.

http://bugzilla.opensuse.org/show_bug.cgi?id=1037700 http://bugzilla.opensuse.org/show_bug.cgi?id=1037700#c6 --- Comment #6 from John Shand --- as a current fix i have found is to disable all repos that are not part of the os as you will find in my repos file. you will notice they are turned on. -- You are receiving this mail because: You are on the CC list for the bug.

http://bugzilla.opensuse.org/show_bug.cgi?id=1037700 http://bugzilla.opensuse.org/show_bug.cgi?id=1037700#c8 Michael Andres changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |jshand2013@gmail.com Flags| |needinfo?(jshand2013@gmail. | |com) --- Comment #8 from Michael Andres --- (In reply to John Shand from comment #5)

let me know if there is anything else you need

Sorry John, but I don't understand the problem description. What exactly is happening? And if it is zypper related, please attach the /var/log/zypper.log -- You are receiving this mail because: You are on the CC list for the bug.

http://bugzilla.opensuse.org/show_bug.cgi?id=1037700 http://bugzilla.opensuse.org/show_bug.cgi?id=1037700#c10 --- Comment #10 from John Shand --- (In reply to Michael Andres from comment #8)

(In reply to John Shand from comment #5)

...

let me know if there is anything else you need

Sorry John, but I don't understand the problem description.

What exactly is happening? And if it is zypper related, please attach the /var/log/zypper.log

when i only have the oss non-oss and update repos active i have to used zypper dup to fix the problem with the kernel update. this should happen if you use the zypper up command, but it doesn't seem to respond correctly -- You are receiving this mail because: You are on the CC list for the bug.

http://bugzilla.opensuse.org/show_bug.cgi?id=1037700 http://bugzilla.opensuse.org/show_bug.cgi?id=1037700#c12 --- Comment #12 from John Shand --- Created attachment 724951 --> http://bugzilla.opensuse.org/attachment.cgi?id=724951&action=edit test case 1 -- You are receiving this mail because: You are on the CC list for the bug.

http://bugzilla.opensuse.org/show_bug.cgi?id=1037700 http://bugzilla.opensuse.org/show_bug.cgi?id=1037700#c14 --- Comment #14 from John Shand --- Created attachment 724955 --> http://bugzilla.opensuse.org/attachment.cgi?id=724955&action=edit test case 3 -- You are receiving this mail because: You are on the CC list for the bug.

http://bugzilla.opensuse.org/show_bug.cgi?id=1037700 http://bugzilla.opensuse.org/show_bug.cgi?id=1037700#c16 --- Comment #16 from John Shand --- Created attachment 724957 --> http://bugzilla.opensuse.org/attachment.cgi?id=724957&action=edit test case 5 -- You are receiving this mail because: You are on the CC list for the bug.

http://bugzilla.opensuse.org/show_bug.cgi?id=1037700 http://bugzilla.opensuse.org/show_bug.cgi?id=1037700#c18 --- Comment #18 from John Shand --- Created attachment 724959 --> http://bugzilla.opensuse.org/attachment.cgi?id=724959&action=edit test case 7 -- You are receiving this mail because: You are on the CC list for the bug.

http://bugzilla.opensuse.org/show_bug.cgi?id=1037700 http://bugzilla.opensuse.org/show_bug.cgi?id=1037700#c20 --- Comment #20 from John Shand --- Created attachment 724962 --> http://bugzilla.opensuse.org/attachment.cgi?id=724962&action=edit test case 9 -- You are receiving this mail because: You are on the CC list for the bug.

http://bugzilla.opensuse.org/show_bug.cgi?id=1037700 http://bugzilla.opensuse.org/show_bug.cgi?id=1037700#c22 --- Comment #22 from John Shand --- i have had that kernel update issue again and i have uploaded the test case files -- You are receiving this mail because: You are on the CC list for the bug.

http://bugzilla.opensuse.org/show_bug.cgi?id=1037700 http://bugzilla.opensuse.org/show_bug.cgi?id=1037700#c24 --- Comment #24 from John Shand --- (In reply to Michael Andres from comment #23)

Thanks. Actually it is no bug, but there's something we can improve...

'zypper update' does a 'best effort' approach. It will update packages as far as possible, but it will never raise any conflict. If a newer version can not be installed for some reason, the package won't be updated. This way you can use 'zypper up' unattended (e.g. in cron scripts).

Usually multiple kernel versions can be installed in parallel. kernel-default-4.10.13-1.4 however explicitly obsoletes versions 4.10.13-1.1, 4.10.13-1.2 and 4.10.13-1.3. Thus installing 4.10.13-1.4 would require removing the installed 4.10.12-1.2. Due to this conflict 'zypper update' skips 4.10.13-1.4. I don't know why, but the kernel maintainers explicitly prevent those versions from being installed together.

'zypper dup' is more aggressive, that's why it will 4.10.12-1.2 to enforce 4.10.13-1.4. AFAIK Tumbleweeed even recommends using 'zypper dup --no-allow-vendor-change' rather than 'zypper up'.

We're now thinking about introducing a force-best option for 'zypper update', which will force the resolver to use the best version, even if it needs to raise conflicts. With such an option zyyper would ask whether it's ok to remove 4.10.12-1.2 in order to install 4.10.13-1.4.

this new feature would be absolutely fantastic! Thanks -- You are receiving this mail because: You are on the CC list for the bug.

http://bugzilla.opensuse.org/show_bug.cgi?id=1037700 http://bugzilla.opensuse.org/show_bug.cgi?id=1037700#c26 John Shand changed: What |Removed |Added ---------------------------------------------------------------------------- Status|NEW |RESOLVED Resolution|--- |WORKSFORME --- Comment #26 from John Shand --- (In reply to John Shand from comment #25)

(In reply to John Shand from comment #24)

...

(In reply to Michael Andres from comment #23)

...

Thanks. Actually it is no bug, but there's something we can improve...

'zypper update' does a 'best effort' approach. It will update packages as far as possible, but it will never raise any conflict. If a newer version can not be installed for some reason, the package won't be updated. This way you can use 'zypper up' unattended (e.g. in cron scripts).

Usually multiple kernel versions can be installed in parallel. kernel-default-4.10.13-1.4 however explicitly obsoletes versions 4.10.13-1.1, 4.10.13-1.2 and 4.10.13-1.3. Thus installing 4.10.13-1.4 would require removing the installed 4.10.12-1.2. Due to this conflict 'zypper update' skips 4.10.13-1.4. I don't know why, but the kernel maintainers explicitly prevent those versions from being installed together.

'zypper dup' is more aggressive, that's why it will 4.10.12-1.2 to enforce 4.10.13-1.4. AFAIK Tumbleweeed even recommends using 'zypper dup --no-allow-vendor-change' rather than 'zypper up'.

We're now thinking about introducing a force-best option for 'zypper update', which will force the resolver to use the best version, even if it needs to raise conflicts. With such an option zyyper would ask whether it's ok to remove 4.10.12-1.2 in order to install 4.10.13-1.4.

this new feature would be absolutely fantastic! Thanks. will this feature work with the applet on KDE? Will i be asked those questions from the applet?

this doesn't seem to be an issue now -- You are receiving this mail because: You are on the CC list for the bug.