On 16/06/14 12:07, Basil Chupin 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 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: http://susepaste.org/43543122 The list of repositories in YaST at this point in time was: http://susepaste.org/41360598 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. Trying to document anything further would only cause more confusion than what was caused by the above :-) so I will stop here - except to say that with the repos now back to: http://susepaste.org/39239947 the errors (shown above) produced by zypper are back again. There are 3 interesting points about the above (at least for me): A) While zypper shows these errors YaST Update Packages if Newer Ones Available (or whatever this is called) shows no dependency errors; and B) Why do we have- * Main Repository OSS; * Main Update Repository; * Main Repository NON-OSS; and * Update Repository NON-OSS (what are each supposed to contain, and what is their purpose?); and C) How does KDE:/Current now fit in into all of the above?!
But there has not been any change in KinfoCenter re the version of the kernel I am using: still shows kernel 3.14.4-2 and not which is actually in use, 3.15.0-1.
/boot contains 3 kernels: 3.14.4-1, 3.14.4-2, and 3.15.0-1.
After a new kernel is installed I always run the command 'grub2-mkconfig -o /boot/grub2/grub.cfg' (and as I also have a separate 'btldr' partition form which I boot other systems I also run this command with 'grub2-mkconfig -o /mnt/btld/boot/grub2/grub.cfg'). Doing so in the past has always given me the correct kernel version in kinfocenter.
Now, I really do not know if this has anything to do with KDE or with the kernel but I am asking the above here, in KDE, because kinfocenter is part of KDE, right? But if I am wrong tell me and I will ask re this in the kernel list.
Re this KinfoCenter hassle, it's for another thread at some stage because it involves the order of the kernels which are shown in /boot - and the problem with the dependency errors is more important. 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