<rant-on>
Actually, at this point it means that I'm going to get some friggin C4
and blow this machine to hell and back because I'm just tired of fussing
with it. KDE2.0.1 will NOT install on here no matter what I do. I've
tried every way known to man to do the upgrade and now it's good and
broke. Some things work, some things don't, and some things, like kpm
don't work at all. Hell! they don't even exist on the system anymore.
AAAAAARRRRRRRRRRRRRRRRRRRG!
So, I'm most likely looking at a reinstall just so I can get this mess
sorted out.
aaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaah!
</rant-on>
Ok...I'm done...might as well get busy. I really don't care that it
didn't work but I would really like to know "why"
it didn't work and what in the world is going on. the last time I
attempted to upgrade KDE on my system it made a mess. There's got to be
a better way.
Mark
pablito wrote:
>
> doesn't that mean that you've gotta go UNINSTALL kdelibs-sound, etc., before
> going on?
> I assume you are installing the KDE upgrades that don't require glibc 2.2 or
> whatever that is in the cooker. I used gnome or icewm instead of KDE to do
> this (if you are in KDE it either won't work or you'll crash.) When I got
> to that point I used rpmdrake to uninstall the offending 2.0-5 packages.
> Then I installed kdebase or kdelibs or whatever it was. You've got to
> install the libs before the base, as I recall. At that point the useful
> kpackage utility disappeared and I then had to use rpm commands in a
> terminal window to install the rest of the packages. (I could have used the
> rpm uninstall command instead of rpmdrake but I couldn't get it right.) At
> that point I logged out, logged back in as KDE and it worked, except there
> was still no kpackage. I used rpmdrake again and found that there were some
> uninstalled miscellaneous little kde files left over from version 2.0-5,
> which I reinstalled and then kpackage reappeared.
>
> Trying to install one of the later KDE versions that require glibc 2.2 is
> much harder and I think pretty much requires downloading all of the cooker
> files.
>
> -----Original Message-----
> From: Mark Weaver <[EMAIL PROTECTED]>
> To: [EMAIL PROTECTED] <[EMAIL PROTECTED]>
> Date: Friday, December 29, 2000 7:57 AM
> Subject: [expert] One BIG anoying Pain in the A**
>
> >Ok...I've followed the directions, done everything that was to be done, and
> >still I get the same stinking, anoying, almost M$-like error. I've got ALL
> >the KDE2.0.1 RPM's downloaded and in the same dir. And STILL there's a
> >problem of one type or another. Theres something I'm just not getting.
> >
> >Anyway, heres the console message when testing the KDE RPM upgrade
> >installation;
> >
> >[root@mdw1982 KDE2.0.1]# rpm -Uvh --test *.rpm
> >error: kdebase-2.0.1-1mdk.i586.rpm cannot be installed
> >error: failed dependencies:
> > kdelibs = 2.0 is needed by kdelibs-sound-2.0-5mdk
> > kdelibs = 2.0 is needed by kdelibs-devel-2.0-5mdk
> > kdelibs = 2.0 is needed by kdelibs-sound-devel-2.0-5mdk
> >
> >I know what it looks like on the surface, but I've grabbed everything I can
> >possibly think of to satisfy any dependency issues and still the same
> message
> >persists. What now? This is SO frustrating.
> >--
> >Mark
> >
> >"If you don't share your concepts and ideals, they end up being worthless,"
> >"Sharing is what makes them powerful."
> >
> > Linus Torvalds
> >
> >
