On Saturday 07 February 2004 17:05, Tom Emerson wrote:
Through some hints and vague references tossed about around here, I finally happened across "the big secret" -- you CAN update KDE using Yast!
I //REALLY// wish SuSE would publish these sorts of "tips" -- as it is, if you go to the KDE update "pages" via the web interface, the way this stuff is presented you end up downloading (and possibly automagically trying to install?) "one subcomponent at a time" -- that just doesn't work :)
However, as someone was kind enough to mention-in-passing, the method is basically as follows:
-- in Yast, add a new FTP source -- server is ftp.pub.suse [or an appropriate mirror] -- directory is: pub/suse/I386/supplementary/KDE/update_for_9.0/yast-source NOTE: there is no "leading slash" needed [I tend to do that out of habit...] Some other posts have mentioned a couple of levels of trailing directory names, which you don't need [appearently yast adds them automatically] What you want to look for is a file called "media.1" [I believe] and point to that directory -- login should be anonymous
Now, "I think..." the first time you do this [successfully] it MAY SEEM that Yast has "hung" -- I **think** yast is actually reading the "media.1" file and parsing it to find what files, versions, and assorted gunk are actually "at" that "installation source"
You can then go into the "install and remove software" utility, select package-groups or others as appropriate, and the display of packages-installed will show installed/available versions that can be upgraded.
All this is "fine so far...", but when I went through the list and checked-to-update all the current KDE packages, the conflict resolution box came up with an error: kdebase3 conflicts with kdebase3-SUSE
So, I'm stuck here -- what is the wisdom of the list?
General wisdom is that you might have to remove kdebase3 manually first. This causes a chain of unfullfilled prerequsits and it quickly becomes a mess. I'm absolutely convinced that SuSE never EVEN ONCE tested this update via YOU for this update to 3.2, even though it worked well in the past. There are "requires" for packages the don't exist either on SUSE site or any other that you simply have to force. (arts > 1.2.0 for example). By ignoring all these and risking the obvious, I was able to get it to install, and had to manually follow up and clean up still missing items. I still have unresolved prerequesits and although its possible to do this upgrade with YOU (sort of) I personally don't recommend it. -- _____________________________________ John Andersen