openSUSE 13.1 using TumbleWeed
Today's zypper dup results in the following:
*************************************
toshiba-lt:~ # zypper dup Warning: You are about to do a distribution upgrade with all enabled repositories. Make sure these repositories are compatible before you continue. See 'man zypper' for more information about this command. Loading repository data... Reading installed packages... Computing distribution upgrade...
The following 7 NEW packages are going to be installed: kernel-default-devel-3.14.0-23.3.gfa168d7 kernel-desktop-3.14.0-23.3.gfa168d7 kernel-desktop-devel-3.14.0-23.3.gfa168d7 kernel-devel-3.14.0-23.2.gfa168d7 kernel-source-3.14.0-23.2.gfa168d7 kernel-syms-3.14.0-23.2.gfa168d7 kernel-xen-devel-3.14.0-23.2.gfa168d7
The following 3 packages are going to be REMOVED: kdeconnect-kde libpublictransporthelper11 plasmoid-flights
The following 142 packages are going to be upgraded: MPlayer amarok branding-openSUSE digikam-doc elfutils gfxboot-branding-openSUSE gmplayer gstreamer gstreamer-0_10 gstreamer-0_10-plugins-base gstreamer-lang gstreamer-plugins-bad gstreamer-plugins-base gtk2-engine-oxygen gtk2-theme-oxygen k3b kde-gtk-config-lang kdeartwork4-icons kdeartwork4-wallpapers kdeartwork4-wallpapers-weather kdebase4-openSUSE kdebase4-runtime-branding-openSUSE kdebase4-workspace-branding-openSUSE kdegames4-carddecks-default kdelibs4-branding-openSUSE ...
The following 123 packages are going to be downgraded: NetworkManager-kde4-libs NetworkManager-kde4-libs-lang NetworkManager-novellvpn-kde4 NetworkManager-openconnect-kde4 NetworkManager-openvpn-kde4 NetworkManager-pptp-kde4 NetworkManager-strongswan-kde4 NetworkManager-vpnc-kde4 akonadi akonadi-runtime ...
The following 127 packages are going to change vendor: NetworkManager-kde4-libs obs://build.opensuse.org/openSUSE:Tumbleweed -> openSUSE NetworkManager-novellvpn-kde4 obs://build.opensuse.org/openSUSE:Tumbleweed -> openSUSE NetworkManager-openconnect-kde4 obs://build.opensuse.org/openSUSE:Tumbleweed -> openSUSE NetworkManager-openvpn-kde4 obs://build.opensuse.org/openSUSE:Tumbleweed -> openSUSE NetworkManager-pptp-kde4 obs://build.opensuse.org/openSUSE:Tumbleweed -> openSUSE NetworkManager-strongswan-kde4 obs://build.opensuse.org/openSUSE:Tumbleweed -> openSUSE NetworkManager-vpnc-kde4 obs://build.opensuse.org/openSUSE:Tumbleweed -> openSUSE ...
142 packages to upgrade, 123 to downgrade, 7 new, 3 to remove, 127 to change vendor. Overall download size: 534.6 MiB. After the operation, additional 685.8 MiB will be used. Continue? [y/n/? shows all options] (y): n toshiba-lt:~ #
Is it normal for packages to be changed back to the "current" repo after having been moved to TW? I have set the TW repo to a higher priority so I would expect packages once moved to TW to stay there.
Ken Schneider - Factory writes:
Is it normal for packages to be changed back to the "current" repo after having been moved to TW? I have set the TW repo to a higher priority so I would expect packages once moved to TW to stay there.
See over in the KDE list. This is somehow related to the branding of KDE, which following the link of Tumbleweed to KDE:Current doesn't provide openSUSE branding anymore.
Regards, Achim.
On 04/07/2014 01:21 PM, Achim Gratz pecked at the keyboard and wrote:
Ken Schneider - Factory writes:
Is it normal for packages to be changed back to the "current" repo after having been moved to TW? I have set the TW repo to a higher priority so I would expect packages once moved to TW to stay there.
See over in the KDE list. This is somehow related to the branding of KDE, which following the link of Tumbleweed to KDE:Current doesn't provide openSUSE branding anymore.
Regards, Achim.
Ah yes, I forgot about the change (my good memory) and thought it would effect TW.
Thanks. :-)
* Ken Schneider - openSUSE suse-list3@bout-tyme.net [04-07-14 13:52]:
On 04/07/2014 01:21 PM, Achim Gratz pecked at the keyboard and wrote:
Ken Schneider - Factory writes:
Is it normal for packages to be changed back to the "current" repo after having been moved to TW? I have set the TW repo to a higher priority so I would expect packages once moved to TW to stay there.
See over in the KDE list. This is somehow related to the branding of KDE, which following the link of Tumbleweed to KDE:Current doesn't provide openSUSE branding anymore.
Regards, Achim.
Ah yes, I forgot about the change (my good memory) and thought it would effect TW.
I _bypass_ such problems, I have seen before *many* downgrades, by using "zypper -v up" until such time as a resolution or work-a-round has been announced. Today adding a lock "*branding-openSUSE", works.
On Mon, Apr 07, 2014 at 02:57:58PM -0400, Patrick Shanahan wrote:
- Ken Schneider - openSUSE suse-list3@bout-tyme.net [04-07-14 13:52]:
On 04/07/2014 01:21 PM, Achim Gratz pecked at the keyboard and wrote:
Ken Schneider - Factory writes:
Is it normal for packages to be changed back to the "current" repo after having been moved to TW? I have set the TW repo to a higher priority so I would expect packages once moved to TW to stay there.
See over in the KDE list. This is somehow related to the branding of KDE, which following the link of Tumbleweed to KDE:Current doesn't provide openSUSE branding anymore.
Regards, Achim.
Ah yes, I forgot about the change (my good memory) and thought it would effect TW.
I _bypass_ such problems, I have seen before *many* downgrades, by using "zypper -v up" until such time as a resolution or work-a-round has been announced. Today adding a lock "*branding-openSUSE", works.
This is currently being worked on, hopefully we have it fixed now...
greg k-h
* Greg KH gregkh@linux.com [04-07-14 17:55]:
On Mon, Apr 07, 2014 at 02:57:58PM -0400, Patrick Shanahan wrote:
- Ken Schneider - openSUSE suse-list3@bout-tyme.net [04-07-14 13:52]:
On 04/07/2014 01:21 PM, Achim Gratz pecked at the keyboard and wrote:
Ken Schneider - Factory writes:
Is it normal for packages to be changed back to the "current" repo after having been moved to TW? I have set the TW repo to a higher priority so I would expect packages once moved to TW to stay there.
See over in the KDE list. This is somehow related to the branding of KDE, which following the link of Tumbleweed to KDE:Current doesn't provide openSUSE branding anymore.
Regards, Achim.
Ah yes, I forgot about the change (my good memory) and thought it would effect TW.
I _bypass_ such problems, I have seen before *many* downgrades, by using "zypper -v up" until such time as a resolution or work-a-round has been announced. Today adding a lock "*branding-openSUSE", works.
This is currently being worked on, hopefully we have it fixed now...
Just tested on one box and appears it *does* work. Will try three more are report.
tks,
* Patrick Shanahan paka@opensuse.org [04-07-14 18:20]:
- Greg KH gregkh@linux.com [04-07-14 17:55]:
On Mon, Apr 07, 2014 at 02:57:58PM -0400, Patrick Shanahan wrote:
- Ken Schneider - openSUSE suse-list3@bout-tyme.net [04-07-14 13:52]:
On 04/07/2014 01:21 PM, Achim Gratz pecked at the keyboard and wrote:
Ken Schneider - Factory writes:
Is it normal for packages to be changed back to the "current" repo after having been moved to TW? I have set the TW repo to a higher priority so I would expect packages once moved to TW to stay there.
See over in the KDE list. This is somehow related to the branding of KDE, which following the link of Tumbleweed to KDE:Current doesn't provide openSUSE branding anymore.
Regards, Achim.
Ah yes, I forgot about the change (my good memory) and thought it would effect TW.
I _bypass_ such problems, I have seen before *many* downgrades, by using "zypper -v up" until such time as a resolution or work-a-round has been announced. Today adding a lock "*branding-openSUSE", works.
This is currently being worked on, hopefully we have it fixed now...
Just tested on one box and appears it *does* work. Will try three more are report.
Success. Worked on all four boxes I tried.
tks,
On 04/07/2014 05:55 PM, Greg KH pecked at the keyboard and wrote:
On Mon, Apr 07, 2014 at 02:57:58PM -0400, Patrick Shanahan wrote:
- Ken Schneider - openSUSE suse-list3@bout-tyme.net [04-07-14 13:52]:
On 04/07/2014 01:21 PM, Achim Gratz pecked at the keyboard and wrote:
Ken Schneider - Factory writes:
Is it normal for packages to be changed back to the "current" repo after having been moved to TW? I have set the TW repo to a higher priority so I would expect packages once moved to TW to stay there.
See over in the KDE list. This is somehow related to the branding of KDE, which following the link of Tumbleweed to KDE:Current doesn't provide openSUSE branding anymore.
Regards, Achim.
Ah yes, I forgot about the change (my good memory) and thought it would effect TW.
I _bypass_ such problems, I have seen before *many* downgrades, by using "zypper -v up" until such time as a resolution or work-a-round has been announced. Today adding a lock "*branding-openSUSE", works.
This is currently being worked on, hopefully we have it fixed now...
greg k-h
Yes after the earlier dup'ing I see the packages want to which back to TW with the current dup. Just a quick question, would it be easier on the TW folks if the repo stopped providing updates for KDE and we added the KDE 'current' repo?
On Mon, Apr 07, 2014 at 08:10:04PM -0400, Ken Schneider - Factory wrote:
On 04/07/2014 05:55 PM, Greg KH pecked at the keyboard and wrote:
On Mon, Apr 07, 2014 at 02:57:58PM -0400, Patrick Shanahan wrote:
- Ken Schneider - openSUSE suse-list3@bout-tyme.net [04-07-14 13:52]:
On 04/07/2014 01:21 PM, Achim Gratz pecked at the keyboard and wrote:
Ken Schneider - Factory writes:
Is it normal for packages to be changed back to the "current" repo after having been moved to TW? I have set the TW repo to a higher priority so I would expect packages once moved to TW to stay there.
See over in the KDE list. This is somehow related to the branding of KDE, which following the link of Tumbleweed to KDE:Current doesn't provide openSUSE branding anymore.
Regards, Achim.
Ah yes, I forgot about the change (my good memory) and thought it would effect TW.
I _bypass_ such problems, I have seen before *many* downgrades, by using "zypper -v up" until such time as a resolution or work-a-round has been announced. Today adding a lock "*branding-openSUSE", works.
This is currently being worked on, hopefully we have it fixed now...
greg k-h
Yes after the earlier dup'ing I see the packages want to which back to TW with the current dup. Just a quick question, would it be easier on the TW folks if the repo stopped providing updates for KDE and we added the KDE 'current' repo?
The goal of Tumbleweed is that you do not have to add random other repos in order to get the latest updates. The issue here is that the KDE developers moved their own repos around a bit, and I had to fix up the links to them for Tumbleweed. Not a big deal, and thanks to the KDE developers, who found the issues that I had in the Tumbleweed repo, it's all now working.
thanks,
greg k-h
On 04/08/2014 05:08 PM, Greg KH pecked at the keyboard and wrote:
On Mon, Apr 07, 2014 at 08:10:04PM -0400, Ken Schneider - Factory wrote:
On 04/07/2014 05:55 PM, Greg KH pecked at the keyboard and wrote:
On Mon, Apr 07, 2014 at 02:57:58PM -0400, Patrick Shanahan wrote:
- Ken Schneider - openSUSE suse-list3@bout-tyme.net [04-07-14 13:52]:
On 04/07/2014 01:21 PM, Achim Gratz pecked at the keyboard and wrote:
Ken Schneider - Factory writes: > Is it normal for packages to be changed back to the "current" repo > after having been moved to TW? I have set the TW repo to a higher > priority so I would expect packages once moved to TW to stay there.
See over in the KDE list. This is somehow related to the branding of KDE, which following the link of Tumbleweed to KDE:Current doesn't provide openSUSE branding anymore.
Regards, Achim.
Ah yes, I forgot about the change (my good memory) and thought it would effect TW.
I _bypass_ such problems, I have seen before *many* downgrades, by using "zypper -v up" until such time as a resolution or work-a-round has been announced. Today adding a lock "*branding-openSUSE", works.
This is currently being worked on, hopefully we have it fixed now...
greg k-h
Yes after the earlier dup'ing I see the packages want to which back to TW with the current dup. Just a quick question, would it be easier on the TW folks if the repo stopped providing updates for KDE and we added the KDE 'current' repo?
The goal of Tumbleweed is that you do not have to add random other repos in order to get the latest updates. The issue here is that the KDE developers moved their own repos around a bit, and I had to fix up the links to them for Tumbleweed. Not a big deal, and thanks to the KDE developers, who found the issues that I had in the Tumbleweed repo, it's all now working.
thanks,
greg k-h
And thank you for all of your work, not only on TW but primarily on the kernel. I wish my health allowed me to give back.
-
Achim Gratz -
Greg KH -
Ken Schneider - Factory -
Ken Schneider - openSUSE
-
Patrick Shanahan