http://www.mandrakeforum.com/article.php3?sid=20010105073750 If you're as addicted as me to these KDE 2.1 updates, here's my latest experience. I used nt (Webdownloader) to grab the 20010103 rpm's out'a the mix on this mirror by pasting ftp://sunsite.uio.no/pub/unix/Linux/Mandrake-devel/unsupported/i586/*200101013* into nt. This d/l'd into a dir by themselves: kdeaddutils-2.1-0.20010103.1mdk.i586.rpm kdeaddutils-devel-2.1-0.20010103.1mdk.i586.rpm kdeadmin-2.1-0.20010103.1mdk.i586.rpm kdegraphics-2.1-0.20010103.1mdk.i586.rpm kdegraphics-devel-2.1-0.20010103.1mdk.i586.rpm kdelibs-2.1-0.20010103.1mdk.i586.rpm kdelibs-devel-2.1-0.20010103.1mdk.i586.rpm kdelibs-sound-2.1-0.20010103.1mdk.i586.rpm kdelibs-sound-devel-2.1-0.20010103.1mdk.i586.rpm kdepim-2.1-0.20010103.1mdk.i586.rpm I already was at the 20010101 level of KDE 2.1 upgrades. So, on these new rpms I ran: rpm -Uvh --test * which returned that there was a conflict with 'kafta' in /usr/bin/ and /usr/lib/menu/ So I renamed those kafta files as old-kafta and uninstalled the 1229..kafta..rpm. I did this after runnin 'rpm -qpil' on kdeaddutils-devel-2.1-0.20010103.1mdk , after rpmfind.net indicated kafta was now supplied by the latest kdeaddutils...rpm (and it is). Now '--test' ran without returning any deps, so I 'rpm -Uvh'd the 20010103 rpms in my list above. All is well, I've been usin 20010103 for a few hours ... no problems. BTW, I noticed there also a new Kdevelop rpm at the ftp link above, kdevelop-2.1-0.20010101.1mdk It installs Kdevelop 1.4 which unlike the previous Kdevelop 2.0 rpms, runs fine, no more seg11's. I guess they gave up on 2.0 and decided to get 1.x workin with KDE2 ;) -- Tom Brinkman [EMAIL PROTECTED] Galveston Bay
