* C. Richard Matson (goldfarm@ranch-farm.com) [040301 12:18]:
On Mon March 1 2004 8:16 am, Timur wrote:
Hello Helmut,
Hallo Timur, i had the same problem some days bevor. I did the update of kdelibs and kdebase with yast. There was no problem.
Hello.I had the same problem with the rpm's from Suse. I installed using fvwm and forced the installation. I had to reboot before using kde 3.2, otherwise it wouldn't work. I just did it yesterday, but so far ok, except for the multimedia applications which I couldn't get to work. Rich
The answer is that rpm's installed via YOU are patch rpm's and most likely don't have the conflicting file in them that they fat rpm that you can ftp down or get via apt have. So that's why YOU users aren't seeing the issues that those who just upgrade via the full rpm are seeing. It's simply that the kdelib3 full rpm is broken because it contains the same file as the kdebase3 pkg that wasn't upgraded. It's simply a screw up from the pkg maintainer. -- Linux User #147972 ---===--- mailto:ben@whack.org -- "There is no need to teach that stars can fall out of the sky and land on a flat Earth in order to defend religious faith."