Group, Sorry Im coming a bit late with this issue. Im trying to update KDE 3.1.4 to 3.2.1 using the RPMs from SuSE ftp site. As they recommend, Im installing first all the base packages. Is it normal to have so many conflicts when installing these packages? I solved several however got kdelibs3 and kdebase3 conflicting with other already installed packages and got stuck in there. Do I have to manually uninstall the old kdebase3 and kdelibs3? when I try to do this I got so many conflicts that I just leave it as it is before getting things REALLY messed up. Experiences, solutions, with this issue are welcome! (SuSE 9.0) Thanks a lot, Felipe.
On Monday 19 April 2004 12:05, Felipe Leon wrote:
Group,
Sorry Im coming a bit late with this issue. Im trying to update KDE 3.1.4 to 3.2.1 using the RPMs from SuSE ftp site. As they recommend, Im installing first all the base packages. Is it normal to have so many conflicts when installing these packages? I solved several however got [snip] Experiences, solutions, with this issue are welcome! (SuSE 9.0)
I just figured out how to get yast2 to load kde-3.2.1 directly from the ftp server. My local mirror is ftp.is.co.za So I go to yast2 - change source of installation module Add - ftp ftp: ftp.is.co.za directory on server: linux/distributions/suse/i386/supplementary/KDE/update_for_9.0/yast-source tick anonymous box Your path will probably be different for your local mirror (if you're not in South Africa, using the S.A. mirror will be dog slow), but it should end the same as mine. Click ok yes whatever, open yast software installer, and there it is - the new kde packages That should problably save you all the dep issues... -- Kind regards Hans du Plooy Newington Consulting Services hansdp at newingtoncs dot co dot za
On Monday 19 April 2004 06:15, Hans du Plooy wrote:
On Monday 19 April 2004 12:05, Felipe Leon wrote:
Group,
Sorry Im coming a bit late with this issue. Im trying to update KDE 3.1.4 to 3.2.1 using the RPMs from SuSE ftp site. As they recommend, Im installing first all the base packages. Is it normal to have so many conflicts when installing these packages? I solved several however got
[snip]
Experiences, solutions, with this issue are welcome! (SuSE 9.0)
I just figured out how to get yast2 to load kde-3.2.1 directly from the ftp server. My local mirror is ftp.is.co.za
So I go to yast2 - change source of installation module Add - ftp ftp: ftp.is.co.za directory on server: linux/distributions/suse/i386/supplementary/KDE/update_for_9.0/yast-source tick anonymous box
Your path will probably be different for your local mirror (if you're not in South Africa, using the S.A. mirror will be dog slow), but it should end the same as mine.
Click ok yes whatever, open yast software installer, and there it is - the new kde packages
That should problably save you all the dep issues...
-- Kind regards Hans du Plooy Newington Consulting Services hansdp at newingtoncs dot co dot za
Hi All, I have to chime in here. Twice, (for emphasis: not once, but twice) I diligently followed apparently rational procedures located on this topic via google, etc. My system ended up broken both times. For the record, I've customized my system a great deal. I also run plenty of non-SuSE packages -- which might explain the difficulty I had with this. It took the following procedure for me to successfully accomplish this upgrade: a) I bit the bullet, verified my backups of non-SuSE apps & data. b) Wiped the hd clean. c) Reinstalled 9.0 from scratch. d) Ran YOU to bring the system up to date. e) Added the new (ftp) installation source in YaST using a local mirror. f) "ftp.anywhere.ext" format in field #1 -->no quotes; no leading or trailing slashes; obviously, use a real site. g) "dir?/dir?/suse/i386/supplementary/KDE/update_for_9.0/yast-source" -->no leading slash in field #2, or YaST will complain; again, obviously, use a real path h) When accepted as a new source, it is added to your list. i) I re-ordered the sources list to bring the new one to the top. YMMV --> I left my other installation sources active in the event YaST needed them to solve other dependencies. I don't really *know* that YaST will access multiple sources in parallel, but it seems logical that it would... j) Select "Close" k) Select YaST "Install and Remove Software" l) Change filter (top left) to "Package Groups" m) Scroll to bottom & select "zzz All" n) Wait for the list to refresh in the right panel. o) Right-click on the first item in the right pane, follow "All in this list" and select "Update if newer version available" in the sub-menu. -->Note: the new install path created, above, only contains updates needed to accomplish the KDE 3.2 upgrade and I just ran YOU, right? Everything installed should be up to date. This manner of package selection turned out to be safe :-) in this case. p) Click "Check Dependencies" and read very carefully. q) It wanted to both update *and* obsolete the installed kpgp (two pieces: one runtime & one devel, IIRC)... In other words, an update is available (??) but, for the 3.2 upgrade, they've been rolled into another package under a different name (something 'utils?') r) To solve this, I hit "Cancel" to close the conflict window, cancelled the installation, repeated k) through n) above, but scrolled down in the right pane, right-clicked the two conflicted packages and selected "delete," clicked "Accept" and let YaST remove them as a separate process. s) When it was done, I re-opened "Install and Remove Software" and repeated l) through p), above. t) The conflict window returned with several KDE packages listed. I selected the "delete conflicting packages" options and then "Try again." u) YaST accepted my choices, displayed some automatic changes, and I clicked "accept." I've been joyfully using KDE 3.2 ever since. Now, there's 2 cents + 2 cents + 2 cents for you to stew on. IMHO, it was worth it. Stable. Clean. Pretty. Flexible. Everything's working. Of course, YMMV and I'm still re-installing my other software. good luck & regards, - Carl - - - - - - - - - - - - - - - - - - - - - - - - - - - C. E. Hartung Business Development & Support Services Dover Foxcroft, Maine, USA http://www.cehartung.com "Jello is never very interesting until it is set and sure of itself!"
Carl E. Hartung wrote:
On Monday 19 April 2004 06:15, Hans du Plooy wrote:
On Monday 19 April 2004 12:05, Felipe Leon wrote:
Group,
Sorry Im coming a bit late with this issue. Im trying to update KDE 3.1.4 to 3.2.1 using the RPMs from SuSE ftp site. As they recommend, Im installing first all the base packages. Is it normal to have so many conflicts when installing these packages? I solved several however got
[snip]
Experiences, solutions, with this issue are welcome! (SuSE 9.0)
I just figured out how to get yast2 to load kde-3.2.1 directly from the ftp server. My local mirror is ftp.is.co.za
So I go to yast2 - change source of installation module Add - ftp ftp: ftp.is.co.za directory on server: linux/distributions/suse/i386/supplementary/KDE/update_for_9.0/yast-source tick anonymous box
Your path will probably be different for your local mirror (if you're not in South Africa, using the S.A. mirror will be dog slow), but it should end the same as mine.
Click ok yes whatever, open yast software installer, and there it is - the new kde packages
That should problably save you all the dep issues...
-- Kind regards Hans du Plooy Newington Consulting Services hansdp at newingtoncs dot co dot za
Hi All,
I have to chime in here. Twice, (for emphasis: not once, but twice) I diligently followed apparently rational procedures located on this topic via google, etc. My system ended up broken both times. For the record, I've customized my system a great deal. I also run plenty of non-SuSE packages -- which might explain the difficulty I had with this. It took the following procedure for me to successfully accomplish this upgrade:
a) I bit the bullet, verified my backups of non-SuSE apps & data.
b) Wiped the hd clean.
c) Reinstalled 9.0 from scratch.
d) Ran YOU to bring the system up to date.
e) Added the new (ftp) installation source in YaST using a local mirror.
f) "ftp.anywhere.ext" format in field #1 -->no quotes; no leading or trailing slashes; obviously, use a real site.
g) "dir?/dir?/suse/i386/supplementary/KDE/update_for_9.0/yast-source" -->no leading slash in field #2, or YaST will complain; again, obviously, use a real path
h) When accepted as a new source, it is added to your list.
i) I re-ordered the sources list to bring the new one to the top. YMMV --> I left my other installation sources active in the event YaST needed them to solve other dependencies. I don't really *know* that YaST will access multiple sources in parallel, but it seems logical that it would...
j) Select "Close"
k) Select YaST "Install and Remove Software"
l) Change filter (top left) to "Package Groups"
m) Scroll to bottom & select "zzz All"
n) Wait for the list to refresh in the right panel.
o) Right-click on the first item in the right pane, follow "All in this list" and select "Update if newer version available" in the sub-menu. -->Note: the new install path created, above, only contains updates needed to accomplish the KDE 3.2 upgrade and I just ran YOU, right? Everything installed should be up to date. This manner of package selection turned out to be safe :-) in this case.
p) Click "Check Dependencies" and read very carefully.
q) It wanted to both update *and* obsolete the installed kpgp (two pieces: one runtime & one devel, IIRC)... In other words, an update is available (??) but, for the 3.2 upgrade, they've been rolled into another package under a different name (something 'utils?')
r) To solve this, I hit "Cancel" to close the conflict window, cancelled the installation, repeated k) through n) above, but scrolled down in the right pane, right-clicked the two conflicted packages and selected "delete," clicked "Accept" and let YaST remove them as a separate process.
s) When it was done, I re-opened "Install and Remove Software" and repeated l) through p), above.
t) The conflict window returned with several KDE packages listed. I selected the "delete conflicting packages" options and then "Try again."
u) YaST accepted my choices, displayed some automatic changes, and I clicked "accept."
I've been joyfully using KDE 3.2 ever since. Now, there's 2 cents + 2 cents + 2 cents for you to stew on. IMHO, it was worth it. Stable. Clean. Pretty. Flexible. Everything's working. Of course, YMMV and I'm still re-installing my other software.
good luck & regards,
- Carl
- - - - - - - - - - - - - - - - - - - - - - - - - - - C. E. Hartung Business Development & Support Services Dover Foxcroft, Maine, USA http://www.cehartung.com
"Jello is never very interesting until it is set and sure of itself!"
Ok, Im writing now from mozilla 1.5 mail on top of KDE 3.2.2! I followed a similar procedure as the one described by Carl. In my case I had the following conflicts which I ordered YaST to simply eliminate: kdebase3-SuSE susehelp susehelp_en kdeaddons3-kate kdeaddons3-konqueror I read somewhere that kdebase3-SuSE was not necessary for KDE 3.2.2 since it was sort of a "beautifier" in fact I can already see the consequences on not installing it: several icon images are lost. I did this very recently so I don't really know how my system will behave in the future. Other thing is that I cannot see anymore some desktop icons for partitions I had before and the icons for the cd and cdwritter are also lost. I hope this is nothing serious and I can just pull them back from my new kde 3.2.2 control panel with a bit more of time :-) However, if anybody sees that Im just missing a very important file or that something is extremely wrong with what I did, please let me know, Cheers and thanks for the your opinions and help! Felipe.
On 04/20/2004 04:09 AM, Felipe Leon wrote:
I read somewhere that kdebase3-SuSE was not necessary for KDE 3.2.2 since it was sort of a "beautifier" in fact I can already see the consequences on not installing it: several icon images are lost.
That is because kdebase-SuSE supplied some SuSE added icons.
Other thing is that I cannot see anymore some desktop icons for partitions I had before and the icons for the cd and cdwritter are also lost.
That is from the the SuSEwatcher program which is part of kdebase-SuSE. It "automatically" put the disk icons on your desktop. They would have still been there if you had copied them to your desktop, instead of always dynamically creating them every boot/login. For that, at this point, I would suggest just right clicking and making it 'manually'. It isn't hard. -- Joe Morris New Tribes Mission Email Address: Joe_Morris@ntm.org Web Address: http://www.mydestiny.net/~joe_morris Registered Linux user 231871 God said, I AM that I AM. I say, by the grace of God, I am what I am.
participants (4)
-
Carl E. Hartung -
Felipe Leon -
Hans du Plooy -
Joe Morris (NTM)