On Thursday 08 June 2006 19:09, BandiPat wrote:
On Thursday 08 June 2006 20:46, Aaron J. Shafenberg wrote:
Lee,
I guess I'm a little confused as to what you mean... are you saying that there are KDE files that need to be fixed or that there are SUSE files that need to be fixed first and then I'll be able to update to 3.5.3? sorry if I sound really dumb about this, I'm new and don't understand Linux very well yet; however I want to learn more. Thanks for the patience!
[...]
Aaron J. Shafenberg ajsSUSEuser@shafenberg.com
==========
Try to remember not to top post your replies. Standard procedure is to write your reply below the other message. The files in 10.1 are broken. If you aren't on the suse-e list, you probably haven't heard about them. There have been many mails about it and many disappointments with 10.1 because of it. Some fixed files are suppose to be released Friday to fix some of those problems.
Problem is, you still may have to update your KDE files manually. When they built the new KDE 3.5.3 files, they used a lower build number than the files supplied on the 10.1 install discs. Because of that, the updater will look at the version/build numbers, see that newer files (higher build versions) are already installed from your discs and not update for you or even show you the new files in the updater yast2 module. Don't know why this happened or why the builders decided to do that, but they did.
Bottom line on that part is, the user has to make a decision. Do they want to throw off the system and update to KDE 3.5.3 or leave it as it was installed and let things progress from their installed 3.5.1 files.
regards, Lee
Lee, Thanks for the update about the replies... so I should just wait until the files are fixed, and then update to 3.5.3 if I decide to do so? -- Aaron J. Shafenberg ajsSUSEuser@shafenberg.com