Hi all,
Well, so much for the KDE update in Tumbleweed. Due to some problems with it (i.e. I messed up and accidentally updated some packages to the 4.6.3 version while the rest were at 4.6.2), I've reverted it all, so soon everyone will see a big "downgrade" to the openSUSE 11.4 version of the KDE packages.
I'll watch the 4.6.3 update and wait for that to settle down before adding it to Tumbleweed again.
Sorry for the churn, but hey, due to the magic of zypper, this all "just works" even for downgrades.
If anyone has any questions about this, please let me know.
thanks,
greg k-h
On 05/06/2011 01:07 AM, Greg KH wrote:
Hi all,
Well, so much for the KDE update in Tumbleweed. Due to some problems with it (i.e. I messed up and accidentally updated some packages to the 4.6.3 version while the rest were at 4.6.2), I've reverted it all, so soon everyone will see a big "downgrade" to the openSUSE 11.4 version of the KDE packages.
I'll watch the 4.6.3 update and wait for that to settle down before adding it to Tumbleweed again.
Sorry for the churn, but hey, due to the magic of zypper, this all "just works" even for downgrades.
If anyone has any questions about this, please let me know.
thanks,
greg k-h
I am a bit confused about a good policy for having repositories enabled when I run "zypper dup --from Tumbleweed" (particularly when this sort of reversion occurs).
I believe that generally I should have these (for example) repos enabled, all same prority, when I run the update command: Tumbleweed Tumbleweed Packman Miscellaneous Tumbleweed repos (e.g. for VirtualBox) openSUSE 11.4 oss openSUSE 11.4 non-oss openSUSE 11.4 Updates openSUSE 11.4 contrib
And a healthy respect for a policy of "look before you leap".
Would you endorse that approach or would you recommend some other approach?
Thanks John A
On Fri, May 06, 2011 at 05:44:16AM +1000, John Andrews (swerdna) wrote:
I am a bit confused about a good policy for having repositories enabled when I run "zypper dup --from Tumbleweed" (particularly when this sort of reversion occurs).
I believe that generally I should have these (for example) repos enabled, all same prority, when I run the update command: Tumbleweed Tumbleweed Packman Miscellaneous Tumbleweed repos (e.g. for VirtualBox) openSUSE 11.4 oss openSUSE 11.4 non-oss openSUSE 11.4 Updates openSUSE 11.4 contrib
And a healthy respect for a policy of "look before you leap".
Would you endorse that approach or would you recommend some other approach?
Yes I would, _but_ I wouldn't worry about the '--from Tumbleweed' part.
Just do a simple: zypper dup and you should be fine.
That's what I do here with my machines, both the test ones for Tumbleweed, as well as my main development ones (desktop and laptop.)
Hope this helps,
greg k-h
On 05/06/2011 06:20 AM, Greg KH wrote:
On Fri, May 06, 2011 at 05:44:16AM +1000, John Andrews (swerdna) wrote:
I am a bit confused about a good policy for having repositories enabled when I run "zypper dup --from Tumbleweed" (particularly when this sort of reversion occurs).
I believe that generally I should have these (for example) repos enabled, all same prority, when I run the update command: Tumbleweed Tumbleweed Packman Miscellaneous Tumbleweed repos (e.g. for VirtualBox) openSUSE 11.4 oss openSUSE 11.4 non-oss openSUSE 11.4 Updates openSUSE 11.4 contrib
And a healthy respect for a policy of "look before you leap".
Would you endorse that approach or would you recommend some other approach?
Yes I would,_but_ I wouldn't worry about the '--from Tumbleweed' part.
Just do a simple: zypper dup and you should be fine.
That's what I do here with my machines, both the test ones for Tumbleweed, as well as my main development ones (desktop and laptop.)
Hope this helps,
greg k-h
Yes, very helpful, thanks
John A
-
Greg KH -
John Andrews (swerdna)