On Sunday 05 February 2006 13:54, Erik Jakobsen wrote:
Well to that I'll say, that I use the information mentioned on this URL: http://www.novell.com/coolsolutions/feature/16592.html
Hi Erik, You didn't include a link to the article in your original post, but I was able to locate it with Google. I've already quoted this excerpt once, but it is important and apparently needs repeating: "It's worth a note, however, to mention that because a lot of these packages are bleeding edge, slight system instability may occur from performing the updates listed here." and the feedback comment, too: "This is very interesting, but hardly something that should go into "newbies," unless one enjoys the thought of newbies trashing their systems. Just to see what would happen, I tried this in the lab. The desktop became unuseable, forcing a reimage on the test machine." My point here is this: There were clear warnings provided that your system and desktop could become unstable by following the procedure described in the article.
Even SuSE provided kde upgrades (not YOU updates), are somewhat experimental and supportless.
That's a pity.
The unofficial SUSE supplementary packages come with a README.txt file in the base directory. It includes the following disclaimer and warnings: "We publish these packages as a service to the community... there is no warranty... If you wish to use a newer version of a package and if you insist on having properly working updates at hand if there is a security update, then please use a newer SuSE Linux version. If you feel a little bit adventurous, then these packages will suit your needs." Again, you have been warned about breakage resulting from introducing "bleeding edge," "unofficial" and "unsupported" packages into your system. Now it starts to get really interesting (not for you, but from a troubleshooting perspective):
Thus, provided you are using the official, original, rpms, just tell Yast to reinstall that "xorg-x11-libs...rpm", again, regardless of it being already installed.
Would be nice if you would give me advice on how to do it. I have thought in the same direction, but doesn't know exactly how, and another case is that it will be a huge job,
????????????????????????????????????????????????????????????
as I have updated all possible packages marked red or blue ????????????????????????????????????????????????????????????
as shown in the article above.
If you don't understand what the red and blue are telling you, this could explain a *lot* of your problems. That article will cause you to break your system even if you know what you are doing. Not understanding what the red and blue is telling you makes the problem worse... it's like mistaking your gas pedal for the brake pedal in your car. :-/ Red = you already have the "latest" available version installed. It means *do not update" (I think if you select it, YaST will interpret your instructions as a request to *downgrade* the package... the opposite of what you want.) Blue = an updated version is available, meaning you can update it if you want.
I will say, that this is the second time I encounter this behaviour. First time I gave up repair the installed 10.0.
We have an old saying: "Third time is a charm" :-)
At first it worked splendid, but when I look through the Yast->Software management->Package Group->zzz-All the second time, ??????????????????????????????????????????????????? and mark the red and blue packages it runs wrong, ??????????????????????????????????????????????????? due to a reason I don't know.
:-) I do :-)
Thought it was nice having found the pahe mentioned above, but it may be wrong, and there may be something, that I don't understand ?.
Yes. You need to study the rpm package database management system. When you understand how rpm works, the tools in YaST are very, very helpful. When you *don't* understand them, upgrades like the one you are attempting are difficult to manage without breaking your system. regards, - Carl