On Sun, 4 Mar 2001 [EMAIL PROTECTED] wrote:

> Ken,
> 
> Your reply cast a lot of light on the situation, but also led me into
> making a judgement, for which I need encouragement. 
> 
> To recap, I want to upgrade from KD1 to KDE2 as a prelude to an
Ah! I'd missed that you were upgrading! I thought you had a different
desktop. Sorry for this, also sorry about the delay in replying, I blame
the timezones.

> installation of KDEOffice. Attempts to use rmp -Uvh on the KDE2
> packages simply returned dependency errors, which you explained were
> caused when an application depended on the old version I wanted to
> remove as part of the update. For example, "libjscript.so.2 is needed
> by kdebase-1.1.2-48" means that that the old kdebase version 1 depends
> on libjscript. 
> 
> So you suggested that I remove the old applications, such as rpm -e
> kdebase. However, as you suspected, it has dependencies, such as 
>       kdebase is needed by autorun-2.61-5
>       kdebase is needed by kdebase-3d-screensavers-1.1.2-48
> 
> After reading man rpm I concluded I might push ahead and issue a
> single command:
>        rpm -e app1 app1 app3 ...  
> 
> However, can I be confidence that that some of these applications are
> not vital the functioning of my system? My guess is not because all
> seem to be KDE programs, but how can I be sure?
> 
Welcome to the joys of being your own sysadmin.

> How to I know that when I install new versions of the KDE applications
> after removing the old that the dependent applications will know to
> use the new versions?
>   
Well, if you've removed the old ones, they're gone. If something needs
e.g. libxyzzy >= 1.0 and you offer it libxyzzy 2.5 it "ought" to work,
but the 'dependent applications' either got removed (-e app3 etc) or you
took a risk with -nodeps (your follow-up mail). 

What you need to do is 
(a) list what will be broken (autorun, 3d-screensavers, everything)
(b) list what is in each of these packages [rpm -ql]
(c) decide if they matter to you
(d) if they do, check the kde2 packages have a replacement.

I'd particularly make sure you have the kdenetwork package available if
you are using kppp to dial out, and also that you've made a note of the
settings to connect to your ISP.

>From memory, when I was trying to upgrade to kde2 (beta) from kde1 my
process was
1. back up the data, e.g. mailboxes if you use kmail.
2. copy all the kde1 and other affected rpms to somewhere safe, so I could
back-out.
3. remove each package individually, taking time to find a sequence that
avoids playing with 'nodeps' or other overrides. (ok, there might be a
loop with kdelibs and kdesupport that requires -nodeps)
4. install kde2 packages using the inverse sequence to '3'.
and in my case
5. remove the kde2 beta packages, because kmail wouldn't run
6. reinstall the kde1 packages
7. restore the data.

Yes, it was a pain, but the overall apply/test/backout-if-necessary
process worked on the 2 occasions I tried it. In the event, I had to
install an upgraded distro because the hard drive failed, and the distro
(Mandrake 7.2) came with a functioning set of packages.

Which reminds me, if you have 64Mb or less, you may find the performance
of kde2 is not acceptable. The classic gotcha - if you want something (in
this case koffice) you have to use suitable hardware.

> On a secondarily question, I was not entirely clear about your
> explanation of qt1 vs qt2, but in any case, qt-2 seems to be
> installed, for when I now run:
> 
>     rpm -qi qt | less
> 
> I get:
> 
>   Name        : qt     Relocations: /usr/lib/qt-2.2.2 
>   Version     : 2.2.2  Vendor: Red Hat, Inc.
>   Release     : 2      Build Date: Fri Nov 17 07:50:12 2000
>   Install date: Sat Mar  3 19:59:12 2001     
>   ...
looks like qt2 is installed, then. I think the intention of changing the
names was so that developers working on qt2 could have a working version
of qt1 to fall back to, but I could be wrong.

You're going to need plenty of time and coffee, but you will learn a lot
about life, the universe, and rpms. (grin)

> 
> Haines Brown
> 

As always, backup, test, then blame the users.

Ken

-
To unsubscribe from this list: send the line "unsubscribe linux-newbie" in
the body of a message to [EMAIL PROTECTED]
Please read the FAQ at http://www.linux-learn.org/faqs

Reply via email to