KDE 3.0.0 -> 3.0.3 update problem...
Good day, SuSE 8.0 Professional. How do I manually update KDE 3.0.0 to the latest 3.0.3? I get a dependency problem on the very first package. I just got the latest KDE-packages from .../suplementary The KDE homepage supscribes that I should first install qt, then arts, then kdelibs3. The SuSE homepage supscribes that I should update using rpm -U So I log in as root and try to update qt3: linux:~/Desktop/KDE303/Binary/base # rpm -U qt3-3.0.5-46.rpm error: failed dependencies: qt3 = 3.0.3 is needed by qt3-non-mt-3.0.3-14 qt3 = 3.0.3 is needed by qt3-devel-3.0.3-15 linux:~/Desktop/KDE303/Binary/base # I think that perhaps the two mentioned packages should first be updated from 3.0.3 to 3.0.5, so I try: linux:~/Desktop/KDE303/Binary/development # rpm -U qt3-non-mt-3.0.5-60.rpm error: failed dependencies: qt3 = 3.0.5 is needed by qt3-non-mt-3.0.5-60 linux:~/Desktop/KDE303/Binary/development # It seems like a kind of a circular dependency problem. I can't upgrade qt3-3.0.3 to qt3-3.0.5 because some other 3.0.3-packages depend on qt3-3.0.3 - but I can't upgrade the other 3.0.3-packages to 3.0.5 because their 3.0.5-packages depend on qt3-3.0.5 Now I'm lost, and I actually don't get it. Can anyone tell me how I'm supposed to pull this update off manually? Please be gentle. I'm not the most technical person around. Best regards Johnny :o)
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 On Sunday 01 September 2002 10:59 am, you wrote:
So I log in as root and try to update qt3:
linux:~/Desktop/KDE303/Binary/base # rpm -U qt3-3.0.5-46.rpm error: failed dependencies: qt3 = 3.0.3 is needed by qt3-non-mt-3.0.3-14 qt3 = 3.0.3 is needed by qt3-devel-3.0.3-15 linux:~/Desktop/KDE303/Binary/base #
Right. What's happening is you're trying to remove/reinstall QT (update), but other packages are saying WAIT, we NEED QT (through rpm), you shouldn't deinstall it! True, but they're about to get get a =newer= one, not lose it, (and they'll in fact be updated too). So use --nodeps. - -- Concept, n.: Any "idea" for which an outside consultant billed you more than $25,000. -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.0.6 (GNU/Linux) Comment: For info see http://www.gnupg.org iEYEARECAAYFAj1ySk8ACgkQnQ18+PFcZJvp1gCeOhSKjjqU29cBh1KxAW/BKy8Q QVwAn1MRJHOWy5h1FIZ46h+I4d/cggj7 =pnFZ -----END PGP SIGNATURE-----
On Sunday 01 September 2002 19:11, Carl wrote:
On Sunday 01 September 2002 10:59 am, you wrote:
So I log in as root and try to update qt3:
linux:~/Desktop/KDE303/Binary/base # rpm -U qt3-3.0.5-46.rpm error: failed dependencies: qt3 = 3.0.3 is needed by qt3-non-mt-3.0.3-14 qt3 = 3.0.3 is needed by qt3-devel-3.0.3-15 linux:~/Desktop/KDE303/Binary/base #
Right. What's happening is you're trying to remove/reinstall QT (update), but other packages are saying WAIT, we NEED QT (through rpm), you shouldn't deinstall it! True, but they're about to get get a =newer= one, not lose it, (and they'll in fact be updated too). So use --nodeps.
Thank you :o) That seems to work, and the updated KDE 3.0.3 comes up and runs just nicely (as far as I can see). It was a bit of a hazzle though to make sure to update the KDE dependencies. But I did like this with every package: First i rpm -U (No --nodeps) If the package was updated without dependency errors, then fine. If there were dependency errors, I would note the dependencies and rpm -U --nodeps the same package again, and then go on to rpm -U the dependency packages - same scheme. I wonder. If I have a whole slew of packages installed that I want to update, and I'm not sure what packages those are, could I then update all installed packages in one command like this?: rpm -F --nodeps *.rpm Or perhaps... for package in *.rpm; do rpm -F --nodeps $package; done Would that update only the packages that are already installed? By the way. The rpm man pages shows a '+' after the package name, but I can't see anywhere what that's for. I don't use the '+', and it works anyway. What's the '+' for? Best regards Johnny :o)
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 On Monday 02 September 2002 01:11 am, you wrote:
But I did like this with every package:
First i rpm -U (No --nodeps)
If the package was updated without dependency errors, then fine.
If there were dependency errors, I would note the dependencies and rpm -U --nodeps the same package again, and then go on to rpm -U the dependency packages - same scheme.
That's actually a safer method than most people use. But supposedly with K in Supplementary, all dependencies are there.
I wonder. If I have a whole slew of packages installed that I want to update, and I'm not sure what packages those are, could I then update all installed packages in one command like this?:
rpm -F --nodeps *.rpm
Don't use -F or -I. Always use -Uvh to install anything. Most people go to the directory then rpm -Uvh --nodeps * . Ben recommends (and I do too): Install base then dev then apps. 1. After each installation of a group such as base you should run SuSEconfig. 2. After all three groups are installed you should remove these things... A. All KDE related directories and files in /tmp B. .mcop in your home directory C. The two temp files in .kde that are pointing to files that you've removed in /tmp. Some people here recommend an automatic dependency resolver for installing rpms called apt. I looked at it and it is nice, but like afio it is too complex, and thus fairly inaccessable to someone who is busy. (or mathematically-challenged like me) I wish K's package manager actually worked. I wish Suse would put out a hotshit backup utility, so we could be in the 21st century, rather than tarring what we absolutely must have. -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.0.6 (GNU/Linux) Comment: For info see http://www.gnupg.org iEYEARECAAYFAj1zi0oACgkQnQ18+PFcZJscTQCcDe7pDJCvFgJe8lDkJk1BEjM+ 0jcAn3gknLQ5owJiJW7f4t8BNHpyzgWW =cqAn -----END PGP SIGNATURE-----
On Monday 02 September 2002 18:01, Carl wrote:
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1
On Monday 02 September 2002 01:11 am, you wrote:
But I did like this with every package:
First i rpm -U (No --nodeps)
If the package was updated without dependency errors, then fine.
If there were dependency errors, I would note the dependencies and rpm -U --nodeps the same package again, and then go on to rpm -U the dependency packages - same scheme.
That's actually a safer method than most people use. But supposedly with K in Supplementary, all dependencies are there.
I wonder. If I have a whole slew of packages installed that I want to update, and I'm not sure what packages those are, could I then update all installed packages in one command like this?:
rpm -F --nodeps *.rpm
Don't use -F or -I. Always use -Uvh to install anything. Most people go to the directory then rpm -Uvh --nodeps * . Ben recommends (and I do too): Install base then dev then apps. 1. After each installation of a group such as base you should run SuSEconfig. 2. After all three groups are installed you should remove these things... A. All KDE related directories and files in /tmp B. .mcop in your home directory C. The two temp files in .kde that are pointing to files that you've removed in /tmp.
Why is -F a bad idea? Do I misunderstand the rpm man page? It says that -F updates a package if a previous version is already installed. As upposed to -U which, as I understand it, updates no matter what. What good things do SuSEconfig do? (I didn't run SuSEconfig at all, and it seems to work fine just the same.) I didn't remove any of the things you suggest. What do I risc by leaving them? Thanks for a lot of good answers :o) Best regards Johnny :o)
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 . When you reply to a list, please only quote those things that are relevent. :) On Monday 02 September 2002 12:20 pm, you wrote:
Why is -F a bad idea? Do I misunderstand the rpm man page? It says that -F updates a package if a previous version is already installed. As upposed to -U which, as I understand it, updates no matter what.
Well, as I can't read my man pages (gdbm fatal: read error) I can't look it up. I think F is Freshen. Some of us have tried all kinds of options, and we have our habits. Maybe F's fine, but sometimes you try something neat, and it all comes falling down.
What good things do SuSEconfig do? (I didn't run SuSEconfig at all, and it seems to work fine just the same.)
Suse and some other distros have made a meta-layer, which is used to configure the system. Unices are so complex that this is how Yast keeps track of what's going on, and Suseconfig makes other changes that are proper when you adjust something. Suseconfig is run after every Yast modification, and you should run it whenever you make changes by hand, to make the whole system contiguous. In 7.3 its core file is /etc/rc.config but use of that was minimised in 8, to bring to LSB.
I didn't remove any of the things you suggest. What do I risc by leaving them?
Non-functionality and/or subtle, queer behaviour. - -- Those who can't write, write manuals. -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.0.6 (GNU/Linux) Comment: For info see http://www.gnupg.org iEYEARECAAYFAj1zq/MACgkQnQ18+PFcZJsDfgCfQy5wLCOXxtdgzZi3+dN0lVSN OdYAnRaupCn2N1+qxWeZ9R/MhgXt/KIe =It2s -----END PGP SIGNATURE-----
On Monday 02 September 2002 08.11, Johnny Ernst Nielsen wrote:
By the way. The rpm man pages shows a '+' after the package name, but I can't see anywhere what that's for. I don't use the '+', and it works anyway.
What's the '+' for?
The '+' just means "one or more" of whatever precedes it. If the man page says [package name]+ it means you can have one or more package names on the command line. It's taken from the so-called regular expressions, where '*' means "zero or more" and '+' means "one or more". It's not very common in man pages, but regular expressions tend to crop up here and there in linux/unix so it could be good to know. regards Anders
participants (3)
-
Anders Johansson -
Carl -
Johnny Ernst Nielsen