You're missing the yast-source at the end. The general rule is: view the target directory in a web browser to verify it has what you want, then lop off the /suse/i586 (since Yast will add it). If /suse/i586 isn't there, the target directory isn't usable by Yast. And (I missed this the first time) don't start the path with a slash when you provide it to Yast.
Paul Abrahams
Tried these with and without the / at the end, nada: ftp://ftp.unina.it/pub/linux/distributions/SuSE/ftp.suse.com/suse/i386/supplementary/KDE/update_for_9.0/yast-source ftp://ftp.suse.com/pub/suse/i386/supplementary/KDE/update_for_9.0/yast-source/suse/i586/ ftp://ftp.gwdg.de/pub/suse/i386/supplementary/KDE/update_for_9.0/ ftp://mirror.mcs.anl.gov/pub/suse/i386/supplementary/KDE/update_for_9.0/yast-source/suse/i586/ BTW: Why doesn't YaST test for the presence of /suse/i586/ in the string and if found then not add it? And why not test for // and if found replace it with a single slash? As a helful app these would seem to be obvious and simple solutions to predictable problems. Meanwhile I have yet to find any location that YaST can successfully use to upgrade to KDE 3.2 Why is this such a hassle? It sure seems a simple need for SuSE to facilitate. It is really an unnecessary waste of a user's time. Sigh ... dmc