You are not logged in.

Dear visitor, welcome to KDE-Forum.org. If this is your first visit here, please read the Help. It explains in detail how this page works. To use all features of this page, you should consider registering. Please use the registration form, to register here or read more information about the registration process. If you are already registered, please login here.

1

Thursday, February 12th 2004, 6:46am

Upgrade KDE 3.1.4 => 3.2

I'm running SUSE 9 and am trying to upgrade from KDE 3.1.4 to 3.2.  I'm also pretty new to Linux.

To test the 'base' packages, I run:
rpm -Uvh --test *.rpm

I get the following:

error: Failed dependencies:
         kdebase3-SuSE <= 9.0 conflicts with kdebase3-3.2.0-7
         libkateinterfaces.so is needed by (installed) kdeaddons3-kate-3.1.4-35
         libkmultitabbar.so.0 is needed by (installed) kdeaddons3-kate-3.1.4-35
         libkonqsidebarplugin.so.0 is needed by (installed) kdeaddons3-konqueror-3.1.4-35

I know I need to remove kdebase3-SuSE, so that's not a problem.  But what about the libs for kdeaddons3?  All three files currently exist.....I don't understand what this is telling me.

Can anyone please explain?

Thanks...

2

Thursday, February 12th 2004, 2:13pm

I found that with SuSE 8.1 I had to FORCE the installation. This is not always the best idea with installations, but if you feel uncomfortable with such a plan perhaps you may want to upgrade to 3.1.5. There is a speed difference and security patches, however KDE 3.2 is much better. :)

Just use a this command:

rpm -Uvh --nodeps --force *.rpm

Install the BASE files and go from there.



Good luck. :D
SpEcIeS

3

Monday, February 16th 2004, 7:09am

Quoted

rpm -Uvh --nodeps --force *.rpm


Isn't that going to open a whole new can of worms? I remember doing that a couple of years ago and I had some series problems after! :cry: Also I am sure there must be a way to script the installation, so that if there is a dependency it checks in the installation directory to see if the required rpm is there and apply that one first.

Just a thought.
The Best Games are for Download @ GCCLINUX

4

Saturday, February 21st 2004, 3:59pm

login under failsafe mode

switch to root (su)

move to the directory which contains the rpm files

/sbin/yast --install *.rpm

yast should now install all the rpms and solve any conflicts or dependencies

5

Monday, February 23rd 2004, 12:17am

Forgive a newbie question....

I *think* I upgraded to kde 3.2. I updated all the kde packages from the ftp.mirror.ac.uk mirror and YAST seemed happy enough. Some things have definitely changed from my 3.1 version BUT the 'KDE is loading' screen is still displaying the 3.1 version number. This has got me slighly worried, am I running 3.2, 3.1 or some screwed up kludge of the two.

Is there some way that I can make sure that

1. All the 3.2 packages are properly installed.
2. I'm actually using them.

and are there any additional actions I should perform to clear out remenants of the older KDE installation?

Thank you for any advice,

G

138

Trainee

Posts: 81

Location: Helsinki, Finland

  • Send private message

6

Monday, February 23rd 2004, 1:45am

Hello,

One easy way to check KDE version is from help menu, about KDE, does it say 3.1.* or 3.2. About checking installed packages one might try this on konsole:
rpm -qa | grep -i kde
Siili teki maalin.

7

Wednesday, March 3rd 2004, 9:59am

The steps for upgrading KDE to 3.2 is pretty well explained at http://linux01.gwdg.de/apt4rpm/kde31to32.html.

But for that, you should have apt4rpm: http://linux01.gwdg.de/apt4rpm/

Apt4rpm is an Apt-get (from debian fame) clone that use RPM files instead of DEBs. It should solve all of your dependency problems. I have followed their tutorial and it worked 3 times without a hitch :wink: .

8

Thursday, March 4th 2004, 3:52pm

I do have the thing. I want to upgrade from 3.1.4 to 3.2. but have not been able to find a propper way of doing it. I am an absolute beginner in Linux.
Is there anybody who can give straight forward instructions (step by step) - (thinking of a person who doesn't know what ./configure and so on means)
I want to run the new Quanta and need 3.2 to have all the features I need.
I am running SUSE 9.0 Pro :cry: Please help.
John di Stefano
john@ducksolutions.com

m4ktub

Intermediate

Posts: 257

Location: Lisbon, Portugal

Occupation: Software Engineer

  • Send private message

9

Thursday, March 4th 2004, 4:49pm

Quoted

Original von Govsan

Forgive a newbie question....

I *think* I upgraded to kde 3.2. I updated all the kde packages from the ftp.mirror.ac.uk mirror and YAST seemed happy enough. Some things have definitely changed from my 3.1 version BUT the 'KDE is loading' screen is still displaying the 3.1 version number. This has got me slighly worried, am I running 3.2, 3.1 or some screwed up kludge of the two.

Is there some way that I can make sure that

1. All the 3.2 packages are properly installed.
2. I'm actually using them.

and are there any additional actions I should perform to clear out remenants of the older KDE installation?

Thank you for any advice,

G


KDE 3.2 uses the same ~/.kde dir so you may have settings there that override the 'kde-config --prefix' settings. Have you installed a custom splash screen?
Try to change the splash screen trough kcontrol under Appearence & themes (Fedora).

airmikeyy

Unregistered

10

Wednesday, April 7th 2004, 4:23am

3.2.1

when i type rpm -Uvh *.rpm i get this error quanta-3.2 failed

11

Wednesday, July 28th 2004, 8:31pm

Quoted

Original von john@ducksolutions.com

I do have the thing. I want to upgrade from 3.1.4 to 3.2. but have not been able to find a propper way of doing it. I am an absolute beginner in Linux.
Is there anybody who can give straight forward instructions (step by step) - (thinking of a person who doesn't know what ./configure and so on means)
I want to run the new Quanta and need 3.2 to have all the features I need.
I am running SUSE 9.0 Pro :cry: Please help.


hmm, are you sure it's a job for an absolute beginnner?
It's not so straight forward to do due to many dependencies in libraries etc and you may get a wrong impression of Linux for failure in such a move.