To continue my ongoing battle with MandrakeUpdate and rpm, have a look a this
lot, cut 'n pasted straight from my terminal:

[root@localhost grpmi]# rpm -Uvh kdelibs-2.0.1-2mdk.i586.rpm
error: failed dependencies:
        kdelibs = 2.0 is needed by kdelibs-sound-2.0-5mdk
        kdelibs = 2.0 is needed by kdelibs-devel-2.0-5mdk
        kdelibs = 2.0 is needed by kdelibs-sound-devel-2.0-5mdk
[root@localhost grpmi]# rpm -Uvh kdelibs-devel-2.0.1-2mdk.i586.rpm
error: failed dependencies:
        kdelibs = 2.0.1 is needed by kdelibs-devel-2.0.1-2mdk
        kdelibs-devel = 2.0 is needed by kdelibs-sound-devel-2.0-5mdk
[root@localhost grpmi]# rpm -Uvh kdelibs-sound-2.0.1-2mdk.i586.rpm
error: failed dependencies:
        kdelibs = 2.0.1 is needed by kdelibs-sound-2.0.1-2mdk
        kdelibs-sound = 2.0 is needed by kdelibs-sound-devel-2.0-5mdk
[root@localhost grpmi]# rpm -Uvh kdelibs-sound-devel-2.0.1-2mdk.i586.rpm
error: failed dependencies:
        kdelibs-sound = 2.0.1 is needed by kdelibs-sound-devel-2.0.1-2mdk
        kdelibs = 2.0.1 is needed by kdelibs-sound-devel-2.0.1-2mdk
        kdelibs-devel = 2.0.1 is needed by kdelibs-sound-devel-2.0.1-2mdk

It's a perfect vicious circle - you can't install a until b is present, but b
requires c, which needs a. The only way I can see to install this lot is for
something, somewhere along the line, to be forced to install. Which is
supposed to be a Bad Thing (tm). Any guesses on which one to force first? My
guess is kdelibs, but that's just because it has the shortest name ...

Maybe there is something to this Debian stuff after all ...

--
Michel Clasquin
[EMAIL PROTECTED]/unisa.ac.za
http://www.geocities.com/clasqm

This message was posted from a Microsoft-free PC

Reply via email to