[opensuse-kde] PLEASE can we get this sorted out and fixed?
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 but this is not the full list of the dependency errors because if I select not to install the 'problem' files I get *more* dependency errors leading to more incomprehensible choices! :-( What has triggered this post is that I have upgraded to kernel 3.15.0-1 yesterday, and have been upgrading the kernel as a new stable one becomes available, but when I looked at Gecko>Computer>KinfoCenter I find that it is showing that I am still running kernel 3.14.4-2! Now come on! :-( Can't this dependency hell be solved once and for all times? (The above captured image was when using YaST but when using zypper I just get a list of files which will not be upgraded/updated (<whatever> - I'm not getting into the 'upgrade' VS 'update' argument thanks). BC -- Using openSUSE 13.1, KDE 4.13.1 & kernel 3.15.0-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
Am Samstag, 14. Juni 2014, 16:25:26 schrieb Basil Chupin:
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)-
Please poste/paste the output of "zypper lr -P" <-- capital P there. Cheers MH -- To unsubscribe, e-mail: opensuse-kde+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-kde+owner@opensuse.org
On 14/06/14 16:36, Mathias Homann wrote:
Am Samstag, 14. Juni 2014, 16:25:26 schrieb Basil Chupin:
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)- Please poste/paste the output of "zypper lr -P" <-- capital P there.
Cheers MH
Output of above is: http://susepaste.org/59954593 and output of zypper lr -pu is: attached because susepaste has decided for some stooopid reason only known to itself that I am a spammer by trying to "create" a new file (stooopid susepaste :-( ). BC -- Over the years you've helped raise awareness of a number of issues but the main one has been what a pain in the arse you are.
There is your problem, you're using the KDE:Extra that is linking against KDE:Current, which is newer than what "stock 13.1" uses. Either swap that KDE:Extra against one that doesnt build against KDE:Current, or include KDE:Current with the same priority as youe KDE:Extra. Cheers MH Am Samstag, 14. Juni 2014, 17:11:39 schrieb Basil Chupin:
On 14/06/14 16:36, Mathias Homann wrote:
Am Samstag, 14. Juni 2014, 16:25:26 schrieb Basil Chupin:
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)-
Please poste/paste the output of "zypper lr -P" <-- capital P there.
Cheers MH
Output of above is:
and output of zypper lr -pu is:
attached because susepaste has decided for some stooopid reason only known to itself that I am a spammer by trying to "create" a new file (stooopid susepaste :-( ).
BC
-- To unsubscribe, e-mail: opensuse-kde+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-kde+owner@opensuse.org
On 14/06/14 17:48, Mathias Homann wrote:
There is your problem, you're using the KDE:Extra that is linking against KDE:Current, which is newer than what "stock 13.1" uses. Either swap that KDE:Extra against one that doesnt build against KDE:Current, or include KDE:Current with the same priority as youe KDE:Extra.
Cheers MH
Am Samstag, 14. Juni 2014, 17:11:39 schrieb Basil Chupin:
On 14/06/14 16:36, Mathias Homann wrote:
Am Samstag, 14. Juni 2014, 16:25:26 schrieb Basil Chupin:
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)- Please poste/paste the output of "zypper lr -P" <-- capital P there.
Cheers MH Output of above is:
and output of zypper lr -pu is:
attached because susepaste has decided for some stooopid reason only known to itself that I am a spammer by trying to "create" a new file (stooopid susepaste :-( ).
BC
I must be misreading your response, but both the KDE:Current and KDE:Extra *ARE* at the same priority level - #99. Nor do I understand, "Either swap that KDE:Extra against one that doesnt build against KDE:Current..". What the heck do each one build "against"? :-) BC -- Using openSUSE 13.1, KDE 4.13.1 & kernel 3.15.0-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
Am Samstag, 14. Juni 2014, 20:39:37 schrieb Basil Chupin:
On 14/06/14 17:48, Mathias Homann wrote:
There is your problem, you're using the KDE:Extra that is linking against KDE:Current, which is newer than what "stock 13.1" uses. Either swap that KDE:Extra against one that doesnt build against KDE:Current, or include KDE:Current with the same priority as youe KDE:Extra.
Cheers MH
Am Samstag, 14. Juni 2014, 17:11:39 schrieb Basil Chupin:
On 14/06/14 16:36, Mathias Homann wrote:
Am Samstag, 14. Juni 2014, 16:25:26 schrieb Basil Chupin:
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)-
Please poste/paste the output of "zypper lr -P" <-- capital P there.
Cheers MH
Output of above is:
and output of zypper lr -pu is:
attached because susepaste has decided for some stooopid reason only known to itself that I am a spammer by trying to "create" a new file (stooopid susepaste :-( ).
BC
I must be misreading your response, but both the KDE:Current and KDE:Extra *ARE* at the same priority level - #99.
...didn't see that the repo that is labeled KDE411 in your list is actually KDE:Current... In fact your repo setup looks fine, except for one thing... You shouldn't mix videolan and packman. That can cause all kind of issues. Cheers MH -- To unsubscribe, e-mail: opensuse-kde+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-kde+owner@opensuse.org
On 06/14/2014 07:22 AM, Mathias Homann wrote:
I must be misreading your response, but both the KDE:Current and KDE:Extra *ARE* at the same priority level - #99.
...didn't see that the repo that is labeled KDE411 in your list is actually KDE:Current...
In fact your repo setup looks fine, except for one thing... You shouldn't mix videolan and packman. That can cause all kind of issues.
Cheers MH I agree. Delete the videlan repo and use packman only for your multimedia. I remember when I was updating via zypper some packages in openSUSE were downgraded.
I would select the kdebase4-workspace-branding-openSUSE to be downgraded. That be said, _disable_ the _Current_ repos including Extra. Run the openSUSE update first. When it has finished. I would log out and log in. Then enable your Current repos. The update to 4.13 will run without incident. Even with the update to 4.13x some packages may get downgraded. -- Cheers! Roman -------------------------------------------- openSUSE -- Get it! Discover it! Share it! -------------------------------------------- http://linuxcounter.net/ #179293 -- To unsubscribe, e-mail: opensuse-kde+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-kde+owner@opensuse.org
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
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 :-) . 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. BC -- Using openSUSE 13.1, KDE 4.13.2 & kernel 3.15.0-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
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
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:
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. -- Cheers! Roman -- To unsubscribe, e-mail: opensuse-kde+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-kde+owner@opensuse.org
On 06/22/2014 05:08 PM, Roman Bysh wrote:
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:
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. -- Cheers! Roman -- To unsubscribe, e-mail: opensuse-kde+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-kde+owner@opensuse.org
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
On 23/06/14 16:44, Basil Chupin wrote: [pruned]
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).
Forgot to add: the option Allow Vendor Change is *OFF*. 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
On 23/06/14 07:08, 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.
Yes, Roman, both k3b and its codecs come from packman.links2linux.de. 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
On 06/23/2014 02:38 AM, Basil Chupin wrote:
On 23/06/14 07:08, 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.
Yes, Roman, both k3b and its codecs come from packman.links2linux.de.
BC Good to know.
Take a look at the first Yast screenshot from the first email. The second line: uninstallable providers kdebase4-workspace-libs-4.11.10-11.1.i586[kde411] Do you have a 32-bit workspace library installed? If you do - you can switch it in Yast by way of the "Versions" tab. Cheers! Roman -------------------------------------------- openSUSE -- Get it! Discover it! Share it! -------------------------------------------- http://linuxcounter.net/ #179293 -- To unsubscribe, e-mail: opensuse-kde+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-kde+owner@opensuse.org
On 25/06/14 04:57, Roman Bysh wrote:
On 06/23/2014 02:38 AM, Basil Chupin wrote:
On 23/06/14 07:08, Roman Bysh wrote:
On 06/22/2014 04:09 AM, Basil Chupin wrote:
[pruned]
Did you install k3b-codecs with k3b from Packman? This should force 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. Yes, Roman, both k3b and its codecs come from packman.links2linux.de.
BC Good to know.
Take a look at the first Yast screenshot from the first email. The second line:
uninstallable providers kdebase4-workspace-libs-4.11.10-11.1.i586[kde411]
Do you have a 32-bit workspace library installed?
If you do - you can switch it in Yast by way of the "Versions" tab.
Thanks, Roman, for seeing this one......but the mystery deepens even further because the 32-bit version is nowhere in sight! :-) See here: http://susepaste.org/69154415 The correct 64-bit version hs always been installed and, as far as I am aware, I do not have any 32-bit apps installed. The only place where reference to 32-bit comes in is when I compile the nVidia driver and I am asked if I want the 32-bit support compiled. I just started having a look at the list of KDE files in YaST and came across this which I find very strange as I haven't used KDE3 since it was replaced zonks ago by KDE4: http://susepaste.org/99161546 and because I don't around installing things which I don't need I am wondering how these KDE3 files got installed and by whom? BC -- Using openSUSE 13.1, KDE 4.13.2 & kernel 3.15.1-2 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
* Basil Chupin <blchupin@iinet.net.au> [06-25-14 21:51]: [...]
I just started having a look at the list of KDE files in YaST and came across this which I find very strange as I haven't used KDE3 since it was replaced zonks ago by KDE4:
and because I don't around installing things which I don't need I am wondering how these KDE3 files got installed and by whom?
rpm -q --last --whatrequires kdelibs3 -- (paka)Patrick Shanahan Plainfield, Indiana, USA @ptilopteri http://en.opensuse.org openSUSE Community Member facebook/ptilopteri http://wahoo.no-ip.org Photo Album: http://wahoo.no-ip.org/gallery2 Registered Linux User #207535 @ http://linuxcounter.net -- To unsubscribe, e-mail: opensuse-kde+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-kde+owner@opensuse.org
On 26/06/14 13:10, Patrick Shanahan wrote:
* Basil Chupin <blchupin@iinet.net.au> [06-25-14 21:51]: [...]
I just started having a look at the list of KDE files in YaST and came across this which I find very strange as I haven't used KDE3 since it was replaced zonks ago by KDE4:
and because I don't around installing things which I don't need I am wondering how these KDE3 files got installed and by whom? rpm -q --last --whatrequires kdelibs3
Thanks Patrick. The 'offending' app is kde3-kaffeine.*.x86_64 ! An x86_64 app requiring some 32-bit file? OK, I can see that but........ Anyway, seeing as I never use kaffeine I zapped this kde3-kaffeine (and associated file), then ran 'zypper clean -a'>'zypper refresh'>'zypper up' and got the same result: The following ...... files will not be upgraded' :-( . Nothing has changed...... BC -- Using openSUSE 13.1, KDE 4.13.2 & kernel 3.15.1-2 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
* Basil Chupin <blchupin@iinet.net.au> [06-25-14 23:43]:
On 26/06/14 13:10, Patrick Shanahan wrote:
* Basil Chupin <blchupin@iinet.net.au> [06-25-14 21:51]: [...] [...]
and because I don't around installing things which I don't need I am wondering how these KDE3 files got installed and by whom? rpm -q --last --whatrequires kdelibs3
Thanks Patrick.
The 'offending' app is kde3-kaffeine.*.x86_64 ! An x86_64 app requiring some 32-bit file? OK, I can see that but........
Anyway, seeing as I never use kaffeine I zapped this kde3-kaffeine (and associated file), then ran 'zypper clean -a'>'zypper refresh'>'zypper up' and got the same result: The following ...... files will not be upgraded' :-( . Nothing has changed......
My post *only* addressed the quoted question. I don't understand why one would install kde3-kaffeine with kaffeine being available and it would not have been installed w/o *specific* selection. -- (paka)Patrick Shanahan Plainfield, Indiana, USA @ptilopteri http://en.opensuse.org openSUSE Community Member facebook/ptilopteri http://wahoo.no-ip.org Photo Album: http://wahoo.no-ip.org/gallery2 Registered Linux User #207535 @ http://linuxcounter.net -- To unsubscribe, e-mail: opensuse-kde+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-kde+owner@opensuse.org
On 26/06/14 21:22, Patrick Shanahan wrote:
* Basil Chupin <blchupin@iinet.net.au> [06-25-14 23:43]:
On 26/06/14 13:10, Patrick Shanahan wrote:
* Basil Chupin <blchupin@iinet.net.au> [06-25-14 21:51]: [...] [...]
and because I don't around installing things which I don't need I am wondering how these KDE3 files got installed and by whom? rpm -q --last --whatrequires kdelibs3 Thanks Patrick.
The 'offending' app is kde3-kaffeine.*.x86_64 ! An x86_64 app requiring some 32-bit file? OK, I can see that but........
Anyway, seeing as I never use kaffeine I zapped this kde3-kaffeine (and associated file), then ran 'zypper clean -a'>'zypper refresh'>'zypper up' and got the same result: The following ...... files will not be upgraded' :-( . Nothing has changed...... My post *only* addressed the quoted question.
I don't understand why one would install kde3-kaffeine with kaffeine being available and it would not have been installed w/o *specific* selection.
Exactly. I never use kaffeine nor amarok nor MPlayer. I only ever now use VLC (used to run xine years ago) so have never had the burning desire to install kaffeine let alone the kde3 version! What installed it I have no idea. But that's not the point: after removing kde3-kaffeine zypper still insists that there are dependency problems. BC -- Using openSUSE 13.1, KDE 4.13.2 & kernel 3.15.1-2 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
participants (5)
-
Basil Chupin -
Mathias Homann -
Patrick Shanahan -
Roman Bysh -
šumski