--- Ben Rosenberg
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.
is there a way we can notify this issue to the mantainer so that he prepare a new (-28) version which is working? How can I find out who is the rpm maintainer? regards, Timur __________________________________ Do you Yahoo!? Yahoo! Search - Find what you�re looking for faster http://search.yahoo.com