Hendrik Woltersdorf writes:
I can do a "zypper dup --from Tumbleweed", but howto avoid this in the future?
Well, you are using an unsupported configuration… so you either should drop Packman and do what GregKH intends you to do or you need to tell zypper exactly what has priority for you. This is my setup: # | Alias | Name | Enabled | Refresh | Priority ---+--------------------------------+---------------------------------+---------+---------+--------- 1 | Tumbleweed | Tumbleweed | Yes | Yes | 97 2 | Packman-Tumbleweed | Packman-Tumbleweed | Yes | Yes | 98 3 | Science-Tumbleweed | Science-Tumbleweed | Yes | Yes | 99 4 | Update-Non-Oss | openSUSE-current-Update-Non-Oss | Yes | Yes | 99 5 | current-Update | openSUSE-current-Updates | Yes | Yes | 99 6 | openSUSE-current-OSS | openSUSE-current OSS | Yes | Yes | 99 7 | openSUSE-current-Updates-debug | openSUSE-current-Updates-debug | Yes | Yes | 99 8 | openSUSE-current-debug | openSUSE-current-debug | Yes | Yes | 99 9 | openSUSE-current-non-OSS | openSUSE-current Non-OSS | Yes | Yes | 99 Then a "zypper dup" will generally do the right thing (it installs from Tumbleweed when there's something in Tumbleweed, then from Packman and then from 12.2 repos), but there are times where it won't. I currently have these locks in place to work around some of the quirks: # | Name | Type | Repository ---+-------------------+---------+------------------------- 1 | kernel-pae | package | openSUSE-current-OSS 2 | kernel-pae | package | current-Update 3 | k3b-lang | package | openSUSE-current-OSS 4 | openSUSE-2012-685 | patch | (any) 5 | openSUSE-2012-701 | patch | (any) 6 | openSUSE-2012-588 | patch | (any) 7 | openSUSE-2012-552 | patch | (any) 8 | openSUSE-2012-567 | patch | (any) 9 | openSUSE-2012-666 | patch | (any) 10 | openSUSE-2012-710 | patch | (any) 11 | openSUSE-2012-791 | patch | (any) 12 | openSUSE-2012-658 | patch | (any) 13 | openSUSE-2012-813 | patch | (any) 14 | openSUSE-2012-658 | patch | (any) 15 | openSUSE-2012-813 | patch | (any) 16 | openSUSE-2012-587 | patch | (any) 17 | openSUSE-2012-880 | patch | (any) But you really need to check each update (press "d" at the y/n/c prompt) when you do a dup before letting it through so you can spot when it tries to do something strange. This ususally happens when something new gets into Tumbleweed and the repo update is not yet complete and typically resolves itself by postponing the update in question by a day or two. Regards, Achim. -- +<[Q+ Matrix-12 WAVE#46+305 Neuron microQkb Andromeda XTk Blofeld]>+ Wavetables for the Waldorf Blofeld: http://Synth.Stromeko.net/Downloads.html#BlofeldUserWavetables -- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-factory+owner@opensuse.org