Terry wrote:
> I have been having sooooooo many problems upgrading to
> KDE 2.1.1 from KDE 2.0.1 running under LM 7.2 .. I
> have tried every single installation instruction that
> someone has posted, and none of them work (even KDE's
> instructions!) .. i even uninstalled KDE 2.0.1 and
> then tried to install 2.1.1, and still get dependency
> errors. And when I install the RPM's, I have to use
> the --nodeps option, regardless. Everything seems to
> work fine, but when I reboot, the graphical logon
> screen for KDE starts to appear, then disappears, and
> I'm stuck at the console. Can anyone help? This is
> getting to be VERY frustrating!!
>
> Terry Sheltra
Terry....when you have a dependancy error then you need to
make sure that the file specified in the error gets installed
on your system. To do that you need to locate the .rpm file
that the file specified in the error is part of and install
it. This needs to be done for every file that is specified
in the dependency error messages that are displayed by the
rpm program.
If you use --nodeps to force rpm to install a package that is
giving you a dependancy error then that package will be
broken and not work untill the dependency is resolved.
The --nodeps switch can be used to make reluctant .rpm files
install, but the package will only work properly if the
dependency you forced rpm to ignore is bogus. But, how do
you know if a dependency is bogus? On my system the last
remaining dependency that was not allowing 2.1.1 to install
was kdesu. A search of my rpm database showed that kdesu was
installed (and I use kdesu all the time so I already knew it
was on the system).
I figured that this was a bogus dependency. So with all
other dependencies already resolved I went ahead and
installed the 2.1.1 .rpms with the --nodeps switch. Then
after doing a 'rpm --rebuilddb', running the update-menus
program and rebooting the system, version 2.1.1 of KDE worked.
--
Alan
