Yast and KDE 3.3.2 update
HI! Every time I start yast to refresh the KDE 3.3.2 upgrade (update selections "KDE desktop" and "KDE development") on my Suse 9.0, it either - installs kdegraphics3 3.3.2, cryptplug 0.3.16 and kdenetwork3-mail 3.1.4 - uninstalls kgamma 1.0.1 or - installs kdepim3 3.3.2, kgamma 1.0.1 - uninstalls cryptplug 0.3.16, kdenetwork3-mail 3.1.4 Each time, it alternates between those 2 possibilities. But which one is correct? I guess, the 2nd. And why does it do this? Thanks! Thomas
On Wednesday 15 December 2004 07:00 am, Thomas Börkel wrote:
HI!
Every time I start yast to refresh the KDE 3.3.2 upgrade (update selections "KDE desktop" and "KDE development") on my Suse 9.0, it
either
- installs kdegraphics3 3.3.2, cryptplug 0.3.16 and kdenetwork3-mail 3.1.4 - uninstalls kgamma 1.0.1
or
- installs kdepim3 3.3.2, kgamma 1.0.1 - uninstalls cryptplug 0.3.16, kdenetwork3-mail 3.1.4
Each time, it alternates between those 2 possibilities.
But which one is correct? I guess, the 2nd.
And why does it do this?
Thanks!
Thomas =========
Thomas, Since neither cryptplug or kgamma are part of the 9.2 package, I'm going to say that those can be removed as they both have probably become part of another package. Are those files leftovers from an update you have done or something you've installed? You want kdepim3, kdenetwork3-mail & kdegraphics3 installed as those are important, if you use kmail, korganizer and many things graphic related in kde. regards, Lee -- --- KMail v1.7.2 --- SuSE Linux Pro v9.2 --- Registered Linux User #225206 "Don't let the fear of striking out keep you from playing the game!"
HI! BandiPat wrote:
Every time I start yast to refresh the KDE 3.3.2 upgrade (update selections "KDE desktop" and "KDE development") on my Suse 9.0, it
either
- installs kdegraphics3 3.3.2, cryptplug 0.3.16 and kdenetwork3-mail 3.1.4 - uninstalls kgamma 1.0.1
or
- installs kdepim3 3.3.2, kgamma 1.0.1 - uninstalls cryptplug 0.3.16, kdenetwork3-mail 3.1.4
Each time, it alternates between those 2 possibilities.
Since neither cryptplug or kgamma are part of the 9.2 package, I'm going to say that those can be removed as they both have probably become part of another package. Are those files leftovers from an update you have done or something you've installed?
Not that I know of. I have upgraded KDE 3.1 to 3.2 to 3.3.0 to 3.3.2.
You want kdepim3, kdenetwork3-mail & kdegraphics3 installed as those are important, if you use kmail, korganizer and many things graphic related in kde.
But kdenetwork3-mail has version 3.1.4. Isn't that a leftover of KDE 3.1? Thomas
On Wednesday 15 Dec 2004 20:52, Thomas Börkel wrote:
You want kdepim3, kdenetwork3-mail & kdegraphics3 installed as those are important, if you use kmail, korganizer and many things graphic related in kde.
But kdenetwork3-mail has version 3.1.4. Isn't that a leftover of KDE 3.1?
Yes it is. All you want out of those packages is kdegraphics3 and kdepim3 . cryptplug, kdenetwork-mail, and kgamma have all been superceded. It seems like YaST has a few bugs in this regard, at least in SuSE 9.0 (which I have too and regularly get this) -- Colin Pinkney http://www.cpinkney.org.uk
On Wednesday 15 December 2004 03:52 pm, Thomas Börkel wrote:
HI!
BandiPat wrote: [...]
Since neither cryptplug or kgamma are part of the 9.2 package, I'm going to say that those can be removed as they both have probably become part of another package. Are those files leftovers from an update you have done or something you've installed?
Not that I know of. I have upgraded KDE 3.1 to 3.2 to 3.3.0 to 3.3.2.
You want kdepim3, kdenetwork3-mail & kdegraphics3 installed as those are important, if you use kmail, korganizer and many things graphic related in kde.
But kdenetwork3-mail has version 3.1.4. Isn't that a leftover of KDE 3.1?
Thomas ===========
Yes it is Thomas, my bad. I was thinking of the file and forgot about the version you mentioned. Another newer version of that should be installed already with your 3.3.2 files. Seems odd that YaST2 would become so confused with all that. I can't say I've ever seen that happen. Maybe you need to rebuild your rpm database? rpm --rebuilddb That might help eliminate some of the confusion. Lee
participants (3)
-
BandiPat -
Colin Pinkney -
Thomas Börkel