BandiPat wrote:

On Friday 10 March 2006 05:43, Roger Oberholtzer wrote:

...

Anyone trying to install evolution from the SUSE gnome supplamental yast source? I have been keeping my system up-to-date from thre and it has for the most part been working.

Somehow, my system has updated parts of evolution (e.g., the evolution-dataserver RPM), and they contain newer version of libraries than the evolution RPM in the same repository wants. For example, libedataserver-1.2.so.4 is wanted by evolution, but only a newer one is installed/available.

I tried removing and then reinstalling evolution and it's parts. But this had no effect.

I also tried just putting copies of the older libs on the system, but they make references that are not satisfied by the current library setup.

Is there no evolution RPM that is compaible with the other evolution components in the repository? I cannot believe that I am the first to encounter this.

-- Roger Oberholtzer

========

Roger, No I'm sure you are not the only one that has encountered this anomaly, but did you tell YaST2 to install them despite the warnings? Since there are problems with certain files in the Gnome updates, it's best if you just refuse to update them at this time. It's possible that these are or were built for 10.1 which is why they won't work. Usually SuSE notices the problems and repairs them later. It's also possible, sometimes, to just recompile the src.rpm yourself to correct the problem for your system.

Guilty. Usually this is OK. Odd thing is that I have one machine where this seems to have worked OK. I think I will try the source RPM compile. It couldn't get much worse. OK. It could. I am probably missing a zillion -devel RPMs. BTW, even if it is for 10.1, the 10.1 evolution would be broken since Feb 21 (IIRC), when the new evolution support RPMs were made. Evolution itself is a week or two older.

You can't just copy over libs to get these things to work, as they don't or aren't registered with the rpm installed and database. Probably the best thing to do at this point, since everything is probably wanky, is to remove the Gnome source and revert all those files back to the originals on the DVD/CD to set the system back right.

I usually never try to copy libs this way. I was desperate and felt it was worth a try. They were duly removed when I saw my ploy had failed.

That's why these supplementary directories are referred to as experimental and to be used with caution. If you force things to be installed, you can expect problems. Sometimes even if you don't force them there will be problems! ;o)

Of course there were messages. Of course I knew better :) Else where would be the thrill?

SUSE will eventually get round to fixing them, but it's still up to the user to use a bit common sense in using them.

Common sense abounds here. I think that I was lulled into a false sense of security as these updates have been working OK. Better than OK. If nothing else, I get to try thunderbird for a bit. All my mail is stored locally in imap, so I am not MUA dependent. -- Roger Oberholtzer

On Fri, 2006-03-10 at 17:08 +0000, James Ogley wrote:

...

Somehow, my system has updated parts of evolution (e.g., the evolution-dataserver RPM), and they contain newer version of libraries than the evolution RPM in the same repository wants. For example, libedataserver-1.2.so.4 is wanted by evolution, but only a newer one is installed/available.

This looks like bug #152399 on bugzilla.novell.com - you might want to add your experience to it.

The description is exactly it. I do not know what the comments are on about. But this is the problem. -- Roger Oberholtzer