Hi all on a spare computer today I loaded openSUSE 11.3 x86_64 with KDE 4.4 on it. First thing I did after installing all updates was follow the multi-media and restricted format installation guide for 11.3 found at:
Once when Packman had an incorrect dependency in a specific package. Try installing those packages ONE AT A TIME to see which one is causing the dependency hiccup.
The SECOND time I encountered this was when I had an inappropriate i586 package installed, and when trying to resolve the dependency problems, the openSUSE software management would have this difficulty.
How about checking to see if you have any 32-bit packages installed that could be causing this? What do you get from typing:
Hi oldcpu thanks for your reply. I have looked in YaST at each individial package that is listed to install in the guide and when I came to libxine1 I found that there was no 64 bit version for packman under versions: http://img844.imageshack.us/img844/9703/snapshot1j.png
I could not update from Packman today yet. This actually happens quite often. That updates are there but _64 bit packages are missing. All you can do is wait it out. Don’t install 32 bit in place of your 64
Hi caf thanks for reply i’ll wait it out. Hopefully it gets fixed soon. Is it a possibility to go and download and install the 64 bit rpm’s manually from the repo?
Thanks
That’s also my experience. Most of the times this has happened, it was fixed in a day. Meanwhile the KDE 45 repos are flooded with KDE packages depending on Qt47, whilst that is not yet in the same repos. We’ll see.
My guess is it may need all of its 64-bit dependencies in place before it shows up as a possible update? There may be a dependency missing so it can not yet be resolved as an update.
A agree with caf4926 and Knurpht, that it is best to wait it out.
I confess, cynical lazy person that I can be at times, I often wait for a week or more before I apply new updates. I like others to encounter the problems (if any) before I do, and hence I read their comments on the forum and thus don’t waste my time when there is a glitch … (although that is not exactly true, as I often join the problem solving thread, and hence end up spending time after all … )
… ergo my wait and see approach is not really a wait and see approach. Another oldcpu self contradiction.