On Thursday 08 March 2001 05:41 am, Dale Kosan wrote:
> Sorry if this has been answered before, I am trying to install the new
> kde2.1 final on my Mandrake 7.2 box.I downloaded all the rpms and did a
> rpm -Uvh *.rpm --test, this is the result:
You might want to see if you get any reponses from those who've
upgraded from 2.0 to 2.1 final. I upgraded from 2.1b2 to 2.1f. 'Course
somewhere along the line I did go 2.0 to pre2.1, but it was long ago, and
did require a fresh 7.2 install to accomplish successfully :)
Generally, if the conflicts you get are only with existing files that
you're fixin to upgrade anyway, this is a situation that warrants the use
of --force. Many are reporting that 'rpm -Uvh --nodeps --force *' is
required to get the 2.1 rpms to install. I did, after fulfilling the few
dep fails I got, and I also had the conflicts with existing pkgs much the
same as yours. I've had no problems since upgrading last Sat morning.
Be cautioned tho that YMMV. I'm not advocating the use of either
--nodeps or --force unless you understand what's involved and are willing
to accept the consequences if it goes wrong. Actually that applies to any
operation that requires root privilege to run.
You could also uninstall the existing pkgs that are reported as
conflicts till you get no 'conflicts' mesgs, but that's basically what
--force does. 'Course if you uninstall some kde pkgs, you then must
install the upgrades, or re-install the old ones during that KDE/X session.
If you're unsure about all this, I'd suggest that 8.0 will be out soon
enough, and it includes kde2.1, 2.4.x kernel, a new gcc, etc.
--
Dale Earnhardt, the greatest stock car driver ever,
he's won his 8th and His Greatest Championship
Tom Brinkman [EMAIL PROTECTED] Galveston Bay
