I'm installing KDevelop using YaST in SuSE 9.2.

I've been notified that there is a dependency conflict.

libogg 1.1-59 conflict
- Required by:
- libogg-devel requires libogg = 1.1-
- Conflict Resolution:
- Do Not Set libogg to Protected
- Ignore Conflict and Risk System Inconsistencies

So I have a choice of not setting it to Protected - I don't even know what that means.
Or
Ignore the Conflict.

I don't really see a problem here if I leave the 1.1-59 version that I installed earlier for MPlayer. I'd rather not downgrade if I don't have to. But, the wording on the two choices has me confused.

Any clarification?

From which source did you install libogg and libogg devel? It seems that the devel does not fit with the package. I think it would be safe to deinstall libogg-devel, since you only needed it for the compilation of mplayer. What I find strange is the required version 1.1-nothing. Maybe this is just an error from naming the package.

I went ahead and installed KDevelop after selecting "Ignore Conflict and Risk System Inconsistencies". Best thing to do if you're not sure, is to test it. Everything appears to have gone fine.

I think it's the wording that is confusing. I'm still trying to understand what those two lines mean. I haven't been able to find any references that could shed some light.

I installed libogg via an RPM for SuSE from the links on the MPlayer site. I make it a habit of determining if there is a SuSE RPM available for any applications and never introduce errors if it isn't necessary by compiling.

I think the first point :"Do Not Set libogg to Protected" means that the system tries to remove or update the conflicting package but it cannot because the package is protected. This happens when packages from other sources than SuSE are installed. You recognise those package by the 'locked' symbol. (All my rpm's from packman are 'protected'). Maybe it would have been sufficient to 'unlock' the package.

The second option should be rather clear: install the package, even if another version is required by the first one. What versions do you get ?

This is on my system:

That's what I have. I don't know that it's going to be a problem unless I decide to do some compiling with libogg.

What you're saying makes some sense. It's YaST package management that's "protecting" files.

So you're saying that the second option overwrites the first package. Or does it simply install the other version by it's side?

Not exactly. It seems that the packman version of libogg has been installed on your system previously and has been set 'protected' by YaST. Now, with the installation of kdevelop, the libogg-devel package is going to be installed, but from the original SuSE source. Since the packman package is protected, it cannot be replaced by the original SuSE version. If you select the later option "Ignore Conflict and Risk System Inconsistencies", YaST installs the devel files of version 1.1.59 together with the libraries of 1.1.2-0.pm.0 (leaving them untouched).

As you said before, it will most probably not affect your system unless you compile something with libogg. However I would suggest to install libogg-devel from packman aswell (first "Ignore Conflict", then install packman devel rpm) or both packages from SuSE ("Do Not Set libogg to Protected")

I think you understand it perfectly.

Now, I've just got to let the dust settle in my head and it will start making more sense as time goes by.

Thanks for the great response.

You're welcome