Thx for your reply... Now .... it's time to decide what folders i must download from here ftp://ftp.suse.com/pub/suse/i386/supplementary/KDE/update_for_9.1/ I think that base and applications is fins isn't it? Also it is necessary to download all the applications' rpms?? When i am going to use the procedure u described earlier all the rpm must be in the same directory right?? Thx a lot have a nice day --- "Matt T." <Matt@Boons.net> wrote:
On Tuesday 28 September 2004 01:08, Alaios wrote:
Thx..for your reply... i prefer downloading the rpms because i can distibute them easier to friens with slow internet access..
Are u sure what u suggest me will work? Thx a lot Have a nice day
--- "Henk A.M. Weebers" <ham.weebers@hccnet.nl> wrote:
Op maandag 27 september 2004 18:44, schreef Alaios:
Hi i have suse 9.1 . I want to upgrade kde 3.2 to kde 3.3 I have started downloading the packages from
ftp://ftp.suse.com/pub/suse/i386/supplementary/KDE/update_for_9.1
How i can upgrade my kde? Thx a lot
cd to the download directory cd base rpm -Uhv *rpm cd ../applications rpm -Uhv *rpm cd ..internationalization rpm -Uhv *rpm
hmmm, let me add a little more to this, which IMHO avoids a lot of headache:
1) first I do copy (or link) all rpms in the same directory. Only if they are in the same directory I can test them all with "rpm -Uvh --test" for dependencies before I actually install them. (Otherwise you can test only the rpms in base, because the other ones in the other directories do need the ones in base, and will always complain a lot.)
2) open a konsole and cd to this directory, which contains all rpms (or links to them).
3) rpm -Uvh --test *.rpm
This will give you most probably some errors, missing dependencies, etc. (you can do this a normal user, you do not have to be root for this test)
3a) if there are missing dependencies, then install them, then go back to 3) and test again
3b) if you cannot find the rpm for a missing dependencies, and it affects an rpm you do not really need, then move this rpm out into a different directory. (example: digikam might need something, or amarok-gstreamer might need gstreamer, and you do not find the missing rpm, but you can run amarok using arts, or you do not have a digital camera, so you do not really need amarok-gstreamer or digikam, then just move them into a "not installed" directory.)
then go back to 3) and test again
4) Once rpm -Uvh --test *.rpm runs through without complaining, then you are ready to do the real install.
5) Log out of your kde session.
6) Switch to a console, by using CTRL-ALT-F2 (or F3 etc.)
7) Log in as root.
8) do an "init 3" (this will unload the x server and with it whatever else is still loaded from kde / qt )
9) cd to the directory with all the rpms
10) now do a "rpm -Uvh *.rpm"
11) watch rpm at work for a while
12) Once rpm is finished, do an init 5
13) Log in again, and enjoy kde 3.3
You can also do a search on the suse lists, there are plenty of discussions about the best way to upgrade kde, with a lot of good instructions, which are probably better than this one. There are also some great tools, which can make your life easier, such as apt or red carpet.
However if you have downloaded the rpms already anyway, I think the way I propose here should be OK - It always worked for me :-)
HTH, Matt
An other (better) way is to download yast-source too. Add the yast-source to the yast instalation source. Updat fules whith yast.
????
succes Henk
-- To unsubscribe, email: suse-kde-unsubscribe@suse.com For additional commands, email: suse-kde-help@suse.com Please do not cross-post to suse-linux-e
__________________________________ Do you Yahoo!? Yahoo! Mail - 50x more storage than other providers! http://promotions.yahoo.com/new_mail