On 24/07/13 00:56, C wrote:
On Tue, Jul 23, 2013 at 3:28 PM, Basil Chupin wrote:
But it's getting these damn dependency errors when some updates need to be done and the choices one is given asking what one wants to do to overcome these errors are the mind-boglers :-( . In some cases option (X+1) is the exact same as option (X) - more weirdness :-( . The dependency errors are often linked to branched code. You take an app in github or wherever, branch it to work on the next release, build on both the trunk and the branch.. then even if that particular bit wasn't changed (codewise) it still gets a new build number. YaST sees it as a different/lower version because the build number is different... bingo bango, you have a downgrade required when it's actually the same code.
That's not always the case... but I've seen it often enough to guess that this is a good portion of the issues with adding Factory and updating.
C.
Well I stopped worrying about them. I now just ignore them by choosing the option which suggests, "Ignore the dependency mess, let it rip and takes your chances." :-) . Re the k3b and k3b-codecs updates, I simply locked these 2 files which has given Factory the two finger salute :-) . BC -- Using openSUSE 12.3, KDE 4.11.0 & kernel 3.10.3-1 on a system with- AMD FX 8-core 3.6/4.2GHz processor 16GB PC14900/1866MHz Quad Channel Corsair "Vengeance" RAM Gigabyte AMD3+ m/board; Gigabyte nVidia GTX550Ti 1GB DDR5 GPU -- To unsubscribe, e-mail: opensuse-kde+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-kde+owner@opensuse.org