Re: [SLE] Slightly irritated
On Tuesday 25 June 2002 8:52 am, you wrote:
Hi All
I know that we have been there already but please someone humour me and tell me how I can update date KDE using the files that I have already downloaded on my machine. (SuSE 8.0) Have tried yast2 and fou4s but maybe I'm using the wrong options or something.
Since I assume that they are all rpm's, you could use kpackage or do it from the command line -
rpm -Uvh /path/to/mypackage.rpm
David
Thanks to all those who have responded, so far. I should now add that I've tried "rpm -Fvh ..." and "rpm -Uvh ..." and get dependency and conflict errors. I am going to try apt-get (if I can find, configure and use it, thanks Tabanna). Eddie
On Tuesday 25 June 2002 16:01, Eddie Howson wrote:
Thanks to all those who have responded, so far. I should now add that I've tried "rpm -Fvh ..." and "rpm -Uvh ..." and get dependency and conflict errors. I am going to try apt-get (if I can find, configure and use it, thanks Tabanna).
When you executing "rpm", are you: rpm -Uvh /path/to/package.rpm or rpm -Uvh /pat/to/*.rpm ? have you tried the last one? Regards, Verdi
Eddie
On Tue, Jun 25, 2002 at 09:01:31AM +0100, Eddie Howson wrote:
Thanks to all those who have responded, so far. I should now add that I've tried "rpm -Fvh ..." and "rpm -Uvh ..." and get dependency and conflict errors. I am going to try apt-get (if I can find, configure and use it, thanks Tabanna).
Hopefully you put the files you downloaded into a structure like this: Stuff from the /base in /some/path/base /dev in /some/path/dev /apps in /some/path/apps If you have that structure, then in that order (base, dev, apps) do: enter directory rpm -Uvh --nodeps --force *.rpm run SuSEconfig go to next Is what I did to upgrade to 3.0.1 (on 8.0) and it worked perfectly. Or almost anyway. It did result in *everything* kde being installed, since I'd donwloaded to complete set. It don't worry me much, as I have plenty space ;) But FWIW I guess using -F instead would be fine. The dependencies will keep rpm from doing this unless you --force --nodeps, because it does the install file by file, and it doesn't know that rpm "a"'s dependencies will be solved by rpm "b" because it gets the list of files alphanumerically from the shell expansion of '*' (something like that anyway) I don't think doing the upgrade in the pairs of 'base', 'dev', 'apps' is *strictly* neccessary. But I think it makes good sense, cause you can have SuSEconfig check up on the stuff, and that reduces the probability of snafu... Word of warning: Backup your desktop/eyecandy settings. And also, when I did this, some of the configfiles in my ~ ended up being owned by root, so when you're done, check ownership/permissions. hth Jon Clausen
On Tuesday 25 June 2002 13.49, Jon Clausen wrote:
Hopefully you put the files you downloaded into a structure like this: Stuff from the /base in /some/path/base /dev in /some/path/dev
You don't actually need the devel packages unless you intend to compile things. They are not needed for the everyday use of KDE.
/apps in /some/path/apps
Also, I don't see the point of separating the rpms into different directories if you're going to install the lot anyway. Put everything you're going to install into one directory and rpm -Uvh *.rpm, and let rpm sort out the dependencies.
If you have that structure, then in that order (base, dev, apps) do: enter directory rpm -Uvh --nodeps --force *.rpm
Don't use --nodeps --force unless you're very, very sure of what you're doing. Especially --force could end up overwriting files you don't want to be overwritten. Don't rely on the package maintainer being infallible. If there's an error, it's probably a good idea to try to find out what the error means.
run SuSEconfig
Why? I've never run SuSEconfig when I install/upgrade KDE, and it works fine anyway. //Anders -- `When I use a word,' Humpty Dumpty said in rather a scornful tone, `it means just what I choose it to mean -- neither more nor less.'
* Anders Johansson (andjoh@cicada.linux-site.net) [020625 07:23]: :: ::Also, I don't see the point of separating the rpms into different directories ::if you're going to install the lot anyway. Put everything you're going to ::install into one directory and rpm -Uvh *.rpm, and let rpm sort out the ::dependencies. Because this is what was recommended to make sure that nothing got screwed up. It was recommended to a few on this list from actual KDE developers. Granted this method was for 2.1.1 when I started doing it..but it's served well so I kept doing it and haven't had the issues that some have had with KDE updates. *shrug* ::Why? I've never run SuSEconfig when I install/upgrade KDE, and it works fine ::anyway. Well, your lucky. And it can't hurt to have SuSEconfig make sure everything is setup correctly. Having it reindex the man pages and other fuctions of SuSEconfig isn't a bad idea. But it is something that optional. -=Ben --=====-----=====-- mailto:ben@whack.org --=====-- Tell me what you believe..I tell you what you should see. -DP --=====-----=====--
On Tue, Jun 25, 2002 at 04:17:57PM +0200, Anders Johansson wrote:
On Tuesday 25 June 2002 13.49, Jon Clausen wrote:
Hopefully you put the files you downloaded into a structure like this: Stuff from the /base in /some/path/base /dev in /some/path/dev
You don't actually need the devel packages unless you intend to compile things. They are not needed for the everyday use of KDE.
True. This would be the generic approach, and I'm not about to argue with whoever recommended this sequence to me. Obviously they know this *way* better than I'll ever hope to. But yeah you don't need dev, if you're not going to compile stuff... Let Eddie decide what *he* needs.
/apps in /some/path/apps
Also, I don't see the point of separating the rpms into different directories if you're going to install the lot anyway. Put everything you're going to install into one directory
Maybe separation is a nonissue. Maybe it's to do with apps depending on dev/base, and dev depending on base, and it makes sense installing in that sequence? *Even* if you --force...
and rpm -Uvh *.rpm,
If you *have* downloaded the lot, it could be kind of laborious to verify which rpms were already installed. So how about using -F instead?
and let rpm sort out the dependencies.
Which was already tried, and reported to fail. Am I mistaken in that dependencies *will* fail in this situation, because of catch 22?
If you have that structure, then in that order (base, dev, apps) do: enter directory rpm -Uvh --nodeps --force *.rpm
Don't use --nodeps --force unless you're very, very sure of what you're doing.
Certainly. When I upped KDE, it didn't much matter to me anyway, because I hadn't fully moved from 7.3 - it did, however work quite nicely. Also, I could have missed it, but I don't recall any problems reported as a result of this way to upgrade kde...(?)
Especially --force could end up overwriting files you don't want to be overwritten. Don't rely on the package maintainer being infallible. If there's an error, it's probably a good idea to try to find out what the error means.
Always. Though from what I understand from the messages about this topic, the errors basically amount to catch 22. But sure, stuff can go wrong. Hence my "words of warning"... back up your .files, check ownerships/permissions afterwards. Certainly something *did* sort of, kind of go wrong for me. But if the worst that happens (my experience) is that some files end up being owned by root, it's not really that bad... I hope it didn't come across as if I was saying "If it won't install, just --force it <yeehaw>" because that's certainly not how I meant it. What I meant was, that in this particular case I've had success with it myself, and I'm not aware of anyone experiencing problems...
run SuSEconfig
Why? I've never run SuSEconfig when I install/upgrade KDE, and it works fine anyway.
Why not? cheers, Jon Clausen
On Tuesday 25 June 2002 22.33, Jon Clausen wrote:
Maybe separation is a nonissue. Maybe it's to do with apps depending on dev/base, and dev depending on base, and it makes sense installing in that sequence? *Even* if you --force...
If there's a requirement on the sequence of packages (there isn't, except for dependencies) then rpm would handle it if you install all of them in the same command.
If you *have* downloaded the lot, it could be kind of laborious to verify which rpms were already installed. So how about using -F instead?
Sure, why not. There's no difference in the method of installation between -U and -F except, as you say, that -F will only grab the packages already installed on the system, so -F would work as well.
and let rpm sort out the dependencies.
Which was already tried, and reported to fail. Am I mistaken in that dependencies *will* fail in this situation, because of catch 22?
Nope, it wasn't tried as far as I can tell. As I read the messages on this topic, all that was tried was to rpm -Uvh each package separately. The only way this can fail if the other method succeeds (as far as I can see, perhaps I should add) is if there are too many packages, so they won't all fit in the parameter array.
Certainly. When I upped KDE, it didn't much matter to me anyway, because I hadn't fully moved from 7.3 - it did, however work quite nicely. Also, I could have missed it, but I don't recall any problems reported as a result of this way to upgrade kde...(?)
yet
Especially --force could end up overwriting files you don't want to be overwritten. Don't rely on the package maintainer being infallible. If there's an error, it's probably a good idea to try to find out what the error means.
Always. Though from what I understand from the messages about this topic, the errors basically amount to catch 22. But sure, stuff can go wrong. Hence my "words of warning"... back up your .files, check ownerships/permissions afterwards. Certainly something *did* sort of, kind of go wrong for me. But if the worst that happens (my experience) is that some files end up being owned by root, it's not really that bad...
If you have a new package (I know this happens with ximian packages) that "owns" a file previously owned by another package it won't install if you just rpm -Uvh it. It will install if you --force it, but the file will be overwritten. That may be what you want, but then again it may not. Caveat installer. //Anders -- `When I use a word,' Humpty Dumpty said in rather a scornful tone, `it means just what I choose it to mean -- neither more nor less.'
participants (5)
-
Anders Johansson -
Ben Rosenberg -
Eddie Howson -
Jon Clausen -
Verdi March