Updating KDE via YOU -- conflict kdebase3/kdebase3-SUSE
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? -- Yet another Blog: http://osnut.homelinux.net
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
On Sun, 2004-02-08 at 03:20, John Andersen wrote:
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.
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.
Try going into YAST -> Software -> system update -> Update Options -> Select "Only update installed packages" This worked fine for me yesterday - there were two conflicts (not serious -from other stuff i had installed) but the system updated perfectly Tim
On Sunday 08 February 2004 12:37 pm, Tim's Suse List wrote:
On Sun, 2004-02-08 at 03:20, John Andersen wrote:
[originally I noted & asked...]
[using YOU to update to KDE 3, it notes a conflict w/KDEbase against KDEbase-SuSE]
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.
Try going into YAST -> Software -> system update -> Update Options -> Select "Only update installed packages"
This worked fine for me yesterday - there were two conflicts (not serious -from other stuff i had installed) but the system updated perfectly
Thanks for your input -- one thing I noticed as I stepped through the procedure again, it marked the package containing "kmail" as "to delete" -- I /suspect/ that the "...kontact" package supercedes this [and presumably includes kmail at that point] but I've ALSO seen a recent "whups..." announcement regarding kmail 1.6 [pop-based mail tends to get deleted from the local host after download, rather than saved...] so I'm curious if the package is somehow marked (at SuSE) as "unsafe" or something... -- Yet another Blog: http://osnut.homelinux.net
Op zondag 8 februari 2004 23:00, schreef Tom Emerson:
This worked fine for me yesterday - there were two conflicts (not serious -from other stuff i had installed) but the system updated perfectly
Thanks for your input -- one thing I noticed as I stepped through the procedure again, it marked the package containing "kmail" as "to delete" -- I /suspect/ that the "...kontact" package supercedes this [and presumably includes kmail at that point] but I've ALSO seen a recent "whups..." announcement regarding kmail 1.6 [pop-based mail tends to get deleted from the local host after download, rather than saved...] so I'm curious if the package is somehow marked (at SuSE) as "unsafe" or something...
It's just replaced by kdepim3-network (or mail, don't remember by heart). -- Richard Bos Without a home the journey is endless
On Sunday 08 February 2004 03:05, Tom Emerson wrote: [snip]
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?
I chose to ignore the conflict, on both computers that upgraded using YOU. kdebase3-SuSE provides some graphics, icons and a lot of configuration files that I would miss if not having them installed. I did not examine exactly which files are in conflict but my guess it's not critical. I've noticed no problems since upgrading. -- Med vennlig hilsen / Kind regards (( Torkild Ulvøy Resheim, Senior Systemutvikler / Software Engineer )) Emma EDB AS, Trondheim, Norway. http://www.emmaedb.no |----|_ Private pages: http://resheim.no - "Any sufficiently advanced | | ) bug is indistinguishable from a feature." |____|´
participants (5)
-
John Andersen -
Richard Bos -
Tim's Suse List -
Tom Emerson -
Torkild Ulvøy Resheim