Updating KDE to 3.1.4 on SuSE Professional 8.0
I tried to install KDE 3.1.4 (the rpm's SuSE provides as the KDE update for 8.0 8 (why didn't they work? I'll never understand)) but the rpm to install first (which is qt3 3.2.3) already showed missing dependencies. Even if I try to start with qt3 3.0.5 I receive messages about missing libraries. Is there an installation instruction where I can go through and see exactly what I need on SuSE Professional 8.0 with KDE 3.0.5 to do the update or do I have to go through the whole mess on my own, figuring out every missing dependency and searching for every lib and rpm on the net? I'll tried to ignore all dependencies and force rpm to install KDE 3.1.4 on a VMware machine where I can easily rollback the installation. The result was (what I expected somehow) that some applications (like YaST2) didn't start anymore. Can someone provide help!! It would be very appreciated! Mit freundlichem Gruss / Sincerely Andreas Woithon
Andreas Woithon schrieb am Dienstag, 16. Dezember 2003 17:14: Hi Andreas,
I tried to install KDE 3.1.4 (the rpm's SuSE provides as the KDE update for 8.0 8 (why didn't they work? I'll never understand)) but the rpm to install first (which is qt3 3.2.3) already showed missing dependencies. Even if I try to start with qt3 3.0.5 I receive messages about missing libraries. Is there an installation
dependency and searching for every lib and rpm on the net? I'll tried to ignore all dependencies and force rpm to install KDE 3.1.4 on a
--force in the fewest cases is a good idea. I would recover the state as of before.
result was (what I expected somehow) that some applications (like YaST2) didn't start anymore.
see what I mean ;-)
Can someone provide help!! It would be very appreciated!
I would start with qt and see what dependencies are not resolved. Resolve them. It may be possible that you have to deinstall some packages before installing new (because there are circle dependencies, on my system especially for the devel packages). Write them down and reinstall them (the new version) right away after you installed the "parent" package. You may also copy all packages in one directory and do a rpm -Fhv * in that directory. You may get fewer dependency failures in that way. These dpendencies are not being fullfilled by KDE/QT packages. If you do the work now you have a clean system thereafter. cu Stefan
Am Dienstag, 16. Dezember 2003 19:24 schrieb Stefan Schlörholz:
It may be possible that you have to deinstall some packages before installing new (because there are circle dependencies, on my system especially for the devel packages).
How can I identify these circle dependencies? -- Mit freundlichem Gruss / Sincerely Andreas Woithon
Andreas Woithon schrieb am Dienstag, 16. Dezember 2003 21:32:
Am Dienstag, 16. Dezember 2003 19:24 schrieb Stefan Schlörholz:
Hello Andreas,
It may be possible that you have to deinstall some packages before installing new (because there are circle dependencies, on my system especially for the devel packages).
How can I identify these circle dependencies?
if you, for instance, upgrade to qt-3.2 and it shows that qt-3.0.5 is needed by qt-devel-3.0.5 one things that the best idea is to upgrade qt-devel to qt-devel-3.2 first. You then get the dependency that qt-3.2 is needed by qt-devel-3.2. You see there is no chance to upgrade qt that way. Either -deinstall qt-devel first, upgrade qt thereafter and finally upgrade qt-devel or -copy (at least) qt and qt-devel in one directory and do a "rpm -Fhv *" in that directory. rpm then checks for dependencies of all packages to be installed. In that way you do not need to deinstall packages before upgrading another one. I know of other circle dependencies: kdelibs3/kdelibs3-devel, kdebase3/ kdebase3-devel, ... You see, most liekly it is the -devel packages causing these problems. AFAIK there is no elegant way to check for circle dependencies. cu and let us know what you did to make it work Stefan
participants (3)
-
Andreas Woithon -
Andreas Woithon
-
Stefan Schlörholz