On Tuesday 11 November 2008 11:49:52 pm David C. Rankin wrote: ..............<delete earlier messages>........
Hi David,
Thanks for replying and especially how to navigate Yast for upgrades. Evidently I am having the same problem wiith Yast as I am with Smart. In trying to upgrade KDE3 it says I need 41 packages but I have 256 conflicts and wants to downgrade just about everything that conflicts with the newer package.
Something wrong going on here. Have no idea what it is riight now.
Bob S
Bob,
Usually that means either (1) You don't have all the repositories added that you need in order to satisfy the dependencies or (2) you have loaded one of those strange packages that causes the anomaly. First, for KDE, you should be fine for the update with:
http://download.opensuse.org/repositories/KDE:/KDE3/openSUSE_11.0/ http://download.opensuse.org/repositories/KDE:/Community/openSUSE_11.0/ http://download.opensuse.org/repositories/KDE:/Backports/ http://download.opensuse.org/repositories/KDE:/Playground/
in addition to your normal
http://download.opensuse.org/distribution/11.0/repo/oss/ http://download.opensuse.org/distribution/11.0/repo/non-oss/ http://download.opensuse.org/update/11.0/
Hi again David. FYI Iam running 10.3 not 11. I did alter the repository versions as required. OK, I disabled all repositories escept for the ones you describe aabove. I had already disabled Packman previously
For the second situation, look at what the dependency conflict is. A lot of times, the dependency problem will boil down to "install package xxxxx even though it will change the vendor". I have seen hundreds of dependency conflict generated this way. All that means is that an updated package is was packaged by someone else other than the packager of the current rpm. A change in vendor for an updated version of the package is OK. If that is the problem, then select the solution that installs what you need even though it will change the vendor.
If it is one of the mplayer, libxine, xine-lib type problems, then the easiest way to get back to a solid config on whatever set of packages you are dealing with is do disable packman and any other repository holding conflicting packages and making sure you have the following enabled:
http://download.opensuse.org/distribution/11.0/repo/oss/ http://download.opensuse.org/distribution/11.0/repo/non-oss/ http://download.opensuse.org/update/11.0/
Only these are enabled
The upgrade/downgrade the packages back to the openSuSE version to establish a good baseline of supported rpms, then add back the other repositories and upgrade a few packages at a time until you identify what package/rpm was causing the dependency problem. Once I find the culprit, I usually just set my installed package (if I like the version) to "Protect -- Do Not Modify" in yast to make sure that the package will not be changed by the 3rd party repository on update in the future.
If your still having problems with dependencies, you can save the conflict list to a text file and post the dependency problems here and we can help. IIRC, the option to save the list is under the "Advanced" button when you are presented with the resolver solutions in Yast.
See the attached list below. Just don't understand why all of those packages must be downgraded or the newer ones not installed. Never had this kind of problem before and I do use Packman, especially for the crippled SuSE video packages.
I completely update KDE3 relatively frequently without any problems. Currently I'm on 3.5.9 and I'm happy with it. I need to start a separate post on 3.5.10 to see if it is good to go. About a week ago someone was complaining about problems with it. So we will see. For your information, I have the following repositories added:
....<deleted>.......
Bob S