This is probably a stupid question but I cannot find the answer anywhere. I am attempting to upgrade KDE on my SuSE 8.2 system. How can I install all the rpms at once rather than one at a time, which takes for ever. Can you do it through YaST. I remember on YaST 1 you could point it at a directory and install all the rpms in there. I cannot do it with YaST 2 however. Nick
On Sat, 2 Aug 2003 15:38:29 +0100
nick murphy
How can I install all the rpms at once rather than one at a time, which takes for ever.
(1) Put all the rpm's in the same directory and run: rpm -Uvh *.rpm (2) Run: SuSEconfig Charles -- "Even more amazing was the realization that God has Internet access. I wonder if He has a full newsfeed?" (By Matt Welsh)
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 On Saturday 02 August 2003 09:38 am, nick murphy wrote:
This is probably a stupid question but I cannot find the answer anywhere. I am attempting to upgrade KDE on my SuSE 8.2 system. How can I install all the rpms at once rather than one at a time, which takes for ever. Can you do it through YaST. I remember on YaST 1 you could point it at a directory and install all the rpms in there. I cannot do it with YaST 2 however.
Nick
Ok, what you need to do is use the ever popular hot key/sign ( * ). First make sure that only the rpms you want to install are in the same folder/directory by themsleves. I have mine in a directory on my /home named downloads and then specific folders, such as xine-stuff, kde-stuff, games, gcc-stuff, etc.. So once you have all you rpm's in the dedicated directory, then you want to issue this command: rpm -Uhv *.rpm This will most likely fail because it will go in alphabetical order and certain packages will complain about unmet dependencies or their are given conflicts such as some files can't be removed, etc... Don't sweat it. There are two flags you can use together, "--nodeps" and "--force". So, most likely you'll have to issue: rpm -Uhv *.rpm --nodeps --force And this should work fine. Then you need to run "SuSEconfig" to establish symlinks (aka alias or aka shortcuts/pointers). This will also update the data base and generally get everything sync'ed up. There was a time that one needed to clear out some temp files. This isn't really necessary anymore but sometimes it does help. If you system should act a bit strange then you might want to try the following after logging out of the users account and then being at the kde logging screen. Crtl+alt+F1, enter in root, then the root passward. Then type "init 3" or "telinit 3". This will shut down the X server. After this type "rm -fr /tmp/* (note if you have any files you don't want deleted move before you do this to another location). Then enter "rm -fr /tmp/.*" this will get rid of all the dot (.) files as well. The type "cd /home/<user>" to move into the user directory (not absolutely needed but save type long directory names, etc). You'll need to do this for all the users accounts (if you have more than one - like yourself, wife, or children, or just anyother users). Now in the home dir type "rm -fr .mcop" and then "rm .mcoprc". the "cd .kde" followed by "rm *-<host name>". In my case the host name is "Crusher-1" so I would type "rm *-Crusher-1". If your unsure what the host name is then type in "ls" when in the ".kde" directory. In my case it's "socket-Crusher-1" and "tmp-Crusher-1", These files are/were symlinked to files in the /tmp directory, which are no longer there. When done go back to the "/" directory and type "init 5" or "telinit 5" and this restarts the Xserver and KDM (the kde login screen). After it gets up, type "crtl+alt+F1" and then "exit" or "logout"... Hit "crtl+alt+F7" and you're back the the kde login screen. All the needed files you deleted will be recreated when you login into your users account. Forgive me if I'm over simplifying or being redundant, I don't know your experience level. HTH, Curtis. -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.2.2-rc1-SuSE (GNU/Linux) iD8DBQE/K9umiqnGhdjCOJsRAkOoAJ9QRjF3F/ePm8dn8PDdSpnMbbQMfwCfSUs9 72ScDNUsTRVkbFm6UTFfeqo= =ZGly -----END PGP SIGNATURE-----
On Sat, 2003-08-02 at 17:41, Curtis Rey wrote:
rpm -Uhv *.rpm
This will most likely fail because it will go in alphabetical order and certain packages will complain about unmet dependencies or their are given conflicts such as some files can't be removed, etc... Don't sweat it.
There are two flags you can use together, "--nodeps" and "--force".
So, most likely you'll have to issue:
rpm -Uhv *.rpm --nodeps --force
And this should work fine.
Please stop saying this. You are advising people to break their systems. --force will allow rpm to overwrite files owned by other packages, and --nodeps will ignore missing dependencies. --nodeps may be useful if you know what you're doing, --force is never useful. At the very least, --force will ruin your rpm database, at worst it could fundamentally destroy your entire system. It's much better to find correct rpms
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 On Saturday 02 August 2003 10:52 am, Anders Johansson wrote:
On Sat, 2003-08-02 at 17:41, Curtis Rey wrote:
rpm -Uhv *.rpm
This will most likely fail because it will go in alphabetical order and certain packages will complain about unmet dependencies or their are given conflicts such as some files can't be removed, etc... Don't sweat it.
There are two flags you can use together, "--nodeps" and "--force".
So, most likely you'll have to issue:
rpm -Uhv *.rpm --nodeps --force
And this should work fine.
Please stop saying this. You are advising people to break their systems. --force will allow rpm to overwrite files owned by other packages, and --nodeps will ignore missing dependencies.
--nodeps may be useful if you know what you're doing, --force is never useful. At the very least, --force will ruin your rpm database, at worst it could fundamentally destroy your entire system. It's much better to find correct rpms
Ok, I will defer to your judgment on this. However, I have yet to have a problem in this area. However, I was unaware of the risks and appologize in this instance. Might you give a brief example of the danger. TIA, Curtis. -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.2.2-rc1-SuSE (GNU/Linux) iD8DBQE/K+dkiqnGhdjCOJsRAh9UAJ40WKqjAFS2Mbt8f/0FTuZ9CLnSLACfT0e/ k0vgAbZrlGFpAV+wS13sM4M= =84GC -----END PGP SIGNATURE-----
On Saturday 02 August 2003 17:31, Curtis Rey wrote:
On Saturday 02 August 2003 10:52 am, Anders Johansson wrote:
On Sat, 2003-08-02 at 17:41, Curtis Rey wrote:
rpm -Uhv *.rpm
This will most likely fail because it will go in alphabetical order and certain packages will complain about unmet dependencies or their are given conflicts such as some files can't be removed, etc... Don't sweat it.
There are two flags you can use together, "--nodeps" and "--force".
So, most likely you'll have to issue:
rpm -Uhv *.rpm --nodeps --force
And this should work fine.
Please stop saying this. You are advising people to break their systems. --force will allow rpm to overwrite files owned by other packages, and --nodeps will ignore missing dependencies.
--nodeps may be useful if you know what you're doing, --force is never useful. At the very least, --force will ruin your rpm database, at worst it could fundamentally destroy your entire system. It's much better to find correct rpms
Ok, I will defer to your judgment on this. However, I have yet to have a problem in this area. However, I was unaware of the risks and appologize in this instance. Might you give a brief example of the danger.
TIA, Curtis.
Thanks for all the help. Nick
On Sat, 2003-08-02 at 18:31, Curtis Rey wrote:
Ok, I will defer to your judgment on this. However, I have yet to have a problem in this area. However, I was unaware of the risks and appologize in this instance. Might you give a brief example of the danger.
ktamaga in the supplementary KDE section contained *all* of /opt/kde3, including great portions of kdebase and/or kdelibs, with --force you would overwrite those. A package can contain for example /boot/vmlinuz, it could contain /lib/libc.so.6, it could contain anything and with --force you wouldn't see any warnings, you'd just overwrite it.
participants (4)
-
Anders Johansson
-
Charles Philip Chan
-
Curtis Rey
-
nick murphy