On 23/07/13 01:40, Patrick Shanahan wrote:

* Basil Chupin [07-22-13 10:39]:

...

...with KDE 4.11 as installed here from the Factory repo and I don't know where the problem lies. I haven't had such a hassle before with upgrades of KDE.

Everytime I try to do updates YaST I get these dependency errors:

http://susepaste.org/5435907 and

http://susepaste.org/85450595

I choose the option which ignores the dependency and the updates go thru but they come up again the next time there are updates to be done. It's getting just a tad annoying..... Why don't you try downgrading kdebase4-workspace-branding-openSUSE?

you can always reinstall the later version.

then (bug)report the problem so it can be resolved.

Good idea, Patrick. I'll try this when its daylight again :-) . BC -- Using openSUSE 12.3, KDE 4.11.0 & kernel 3.10.1-3 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

On 23/07/13 02:22, šumski wrote:

On Tuesday 23 of July 2013 00:35:32 Basil Chupin wrote:

...

...with KDE 4.11 as installed here from the Factory repo and I don't know where the problem lies. I haven't had such a hassle before with upgrades of KDE.

Everytime I try to do updates YaST I get these dependency errors: Choosing downgrade of kdebase4-runtime/kdebase4-workspace-branding-openSUSE to 12.3-5.7, should resolve the issue...

Thank you for this and it 'fixed' 2 of the errors. But trying to do updates a few minutes ago produced this- http://susepaste.org/67319439 The runtime error is still there but now there are others. When will it all stop? :-) BC -- Using openSUSE 12.3, KDE 4.11.0 & kernel 3.10.1-3 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

On 23/07/13 19:29, C wrote:

On Tue, Jul 23, 2013 at 9:13 AM, Basil Chupin wrote:

...

Thank you for this and it 'fixed' 2 of the errors.

But trying to do updates a few minutes ago produced this-

http://susepaste.org/67319439

The runtime error is still there but now there are others.

When will it all stop? :-) Hehe, when you stop using the KDE Factory repo :-) I ran into similar issues with KDE Factory... rolled back to default for 12.3 so I had a working desktop again.

Well, the desktop seems to be OK and I haven't struck any problems with the apps I normally run. 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 other thing is that these errors come up when I use YaST but zypper most of the time does not display these errors - it just 'tells' me that such and such files will not be updated. Most confusing. BC -- Using openSUSE 12.3, KDE 4.11.0 & kernel 3.10.1-3 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

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

On 24/07/13 03:06, šumski wrote:

On Tuesday 23 of July 2013 17:13:09 Basil Chupin wrote:

...

But trying to do updates a few minutes ago produced this-

http://susepaste.org/67319439 I think it would be best to lock kdebase-runtime-brandind-openSUSE and kdebase4-workspace-branding-openSUSE at current installed versions, as they are correct ones. Unfortunately , old binaries with higher build numbers didn't get deleted, so they are causing constant "resolve issues".

...

The runtime error is still there but now there are others. Which runtime error is that?

The one in the screenshot I provided (above). BC -- Using openSUSE 12.3, KDE 4.11.0 & kernel 3.10.2-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

On 25/07/13 07:13, šumski wrote:

On Wednesday 24 of July 2013 17:31:15 Basil Chupin wrote:

...

On 24/07/13 03:06, šumski wrote:

...

Which runtime error is that? The one in the screenshot I provided (above). Basil, maybe i'm missing something, but i see only YaST screenshot for which: I think it would be best to lock kdebase-runtime-brandind-openSUSE and kdebase4-workspace-branding-openSUSE at current installed versions, as they are correct ones. Unfortunately , old binaries with higher build numbers didn't get deleted, so they are causing constant "resolve issues". wrt libav*, i have no idea, i guess packman is not in sync somewhere...

Yessss.... there was a 'discussion' about packman and who is now handling it after Pascal left.... 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