Just want to notice that because the ZYpp update from today, that fixes bnc#631306, the “zypper dup” behavior has changed in a way that could make multimedia packages from Packman to be substituted by the openSUSE ones. To an user this could mean some formats stop to play… and if Packman packages aren’t 100% perfect (I didn’t check), perhaps some crashes.
This will hit mostly only people that has Packman with a lower priority than the official repo.
Hi RedDwarf,
Can you be more specifics, I am not sure newbies and some others will understand what you are explaining here… 
I have Packman with priority 90 and the main repo with priority 50. GStreamer and Xine packages were installed from Packman.
Before, because of a bug, a “zypper dup” didn’t touch the GStreamer/Xine packages and everything worked. Now, in such a case, it correctly changes the Packman packages for openSUSE ones, without MP3 and other multimedia formats support.
This can get more complex if you have other repos as multimedia:libs/multimedia:apps. But the thing is that people should check two times the list of packages iff they do a “zypper dup”, as some people do, after the zypper/libzypp update from today.
So,
you’re implying that the priority of repos doesn’t mean anything anymore, is that right?
Quite the opposite, if I understood correctly with 50 being a higher priority than 90.
Oh! I thought that the higher the number, higher is the priority.
Before the priority had a meaning, but there was a bug that missed some cases. Now the priority has a meaning… and works 
On 2010-12-02 22:06, DaaX wrote:
>
> Oh! I thought that the higher the number, higher is the priority.
No.
When you count, 50 is before 100.
–
Cheers / Saludos,
Carlos E. R.
(from 11.2 x86_64 “Emerald” at Telcontar)
Yeah, ok, I didn’t thought about it like that.
Good to know, thanks. 
Thanks for the information and warning.
Best regards,
Greg
You can toy around with the priority settings all you want but from 11.2 on things changed regarding package management, repos, and priorities. Some other things to consider are in the mix. Check this out.
“This article explains vendor stickiness concept and provides information about how to override the default behaviour.”
I posted a reply on this down thread but thought I’d hit your original post. I had a discussion with caf4926 on this a while back. I don’t change priority on my repos anymore. Priority of a repo isn’t handled the same way from 11.2 on and I’m wondering how your post is related to information at the below. “This article explains vendor stickiness concept and provides information about how to override the default behavior.”
I don’t really remember 11.2 status. But right now priorities are handled the only way that, IMHO, makes sense.
Since vendor stickiness doesn’t applies to dist-upgrade, isn’t related at all.
My post only says: “it’s possible you were relying on a buggy zypper dup, since now it’s fixed… double check”.
Okay. My bad but the simple statement quoted prompted some googles and cleared up another gap in my kowledge so thanks for the tip. Sorry for drifting off a bit from the original post but my understanding of some of the basics was apparently a bit off. I thought that priorities were somewhat irrelevant and repos were subject to vender stickiness in zypp which I assumed implied that dup would honor it too. Apparently dup WILL try to sync your currently installed packages with the ones available from (all) the repos you have enabled and dup worries me anyway so thinking about a buggy zypper dup makes my eyes water.