On 23/06/14 07:13, Roman Bysh wrote:
On 06/22/2014 05:08 PM, Roman Bysh wrote:
On 14/06/14 21:57, šumski wrote:
On Saturday 14 of June 2014 08:25:26 Basil Chupin wrote:
For days now I have not been able to fully upgrade some of the KDE files because, for example, I get this (captured a few moments ago)-
http://susepaste.org/76846225 zypper dup --from kde411 should resolve this. at least it appears your branding packages come from standard/update repo, not KDE:Current
Cheers, Hrvoje Thanks to Mathias, Roman and Sumski for the advice on how to solve the dependency errors.
I did what Sumski suggested and indeed it did bring nornality back and at least now I am showing that I am running KDE 4.13.2. Thank you.
However, the question still remains: why can't the means be found to have these dependency errors solved automatically by, say, YaST? I don't know the technical details but if someone has the knowledge and the ability to write something like YaST then surely making it capable of resolving this is possible :-) . Doing the above solved the problem of the dependency errors for
On 16/06/14 12:07, Basil Chupin wrote: that one time but it has returned a day or so after when more updates/upgrades became available.
It is only now that I have found some time to look into this matter and here is what I found.
I normally use zypper the first thing when I boot the system to check for updates/upgrades - YaST is used infrequently. This pic show what zypper shows re the errors today after I ran zypper refresh>zypper up:
The list of repositories in YaST at this point in time was:
I did some deselection and reselection of repos in YaST - with corresponding 'zypper clean -a' in command line mode - and found the following:
1) this would be obvious to all those who already know about it- YaST will only refresh the repositories if it finds that they are outside some, unknown to me, period of time of the repositories's caches created by zypper. In other words, use 'zypper clean -a' on a command line and then go into YaST and YaST will 'refresh' the repos; but first use 'zypper refresh' and then go into YaST and YaST doesn't refresh anything;
2) the dependency errors are caused by repositories-
a) Main Repository OSS;
b) Main Update Repository;
c) Main Repository NON-OSS; and
d) Update Repository NON-OSS.
I followed what Roman Bysh suggested (see http://susepaste.org/41360598 above) and then went about disabling/enabling repositories with the following result"
i) with the KDE:/Current repos disabled, and disabling Main Update Repo, zypper still showed all the errors;
ii) as above but with Main Update OSS repo disabled the errors in zypper disappeared.
I then enabled the 2 KDE:/Current repos and the error re k3b came back, and disabling Main Update NON-OSS repo did nothing to remove this error- it was still there. Did you install k3b-codecs with k3b from Packman? This should force
On 06/22/2014 04:09 AM, Basil Chupin wrote: the update to use k3b from Packman. That's what I have done.
You can also go into Yast find the problem package, click on the Versions tab to check problem package version. I have also used this process.
Follow Up
I have Packman priority set to 98 and KDE Current set to 99.
See above (the URL http://susepaste.org/41360598) which shows that Packman is at level 95 and the Current repos at 97 (with the Main/Update repos for OSS and NON-OSS at 99). BC -- Using openSUSE 13.1, KDE 4.13.2 & kernel 3.15.1-1 on a system with- AMD FX 8-core 3.6/4.2GHz processor 16GB PC14900/1866MHz Quad Channel RAM Gigabyte AMD3+ m/board; Gigabyte nVidia GTX660 GPU -- To unsubscribe, e-mail: opensuse-kde+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-kde+owner@opensuse.org