On Wed, Jul 7, 2010 at 7:33 AM, Stephan Kulow <coolo@novell.com> wrote:
Am Mittwoch 07 Juli 2010 schrieb Greg Freemyer:
On Wed, Jul 7, 2010 at 5:19 AM, Stephan Kulow <coolo@novell.com> wrote:
Hi,
After we rebuilt RC2 from the 11.3 project and fixed a handful of bugs, I see no reason to delay 11.3 GM, so I'll prepare everything for the landing.
Greetings, Stephan
I hope you delay a day or two.
If not upgrade via "yast2 wagon" will not work for the11.3 lifetime (ie. all 18 months). At least for now it does not appear fixable via online updates due to how wagon is used..
========= background
Are you familiar with
https://bugzilla.novell.com/show_bug.cgi?id=613820
Distribution upgrade from 11.2 => 11.3 via "yast2 wagon" is broken. Last tested 12 hrs ago, but a proposed fix just went into a obs home directory a few hours ago. There seems to be a lot of confusion in that bug what wagon is about. I appreciate your effort getting it fixed/usable, but I don't think fixing the bug will make it a supported upgrade path.
Greetings, Stephan
I have successfully upgraded from RC1 to RC2 with wagon, so the basic package is fine, it is just the bug in the "renew upgrade stack" that is a problem. It was a supported upgrade path for 11.1 => 11.2, so it not working at all would be a reversion. And yast2 wagon is exactly the kind GUI based upgrade tool that reviewers will like to see. If it does not make it into 11.3, it really needs to get the attention of the next release manager (you?) early on. 1) It should be part of the default yast pattern, not require a separate install. 2) It should have a package description that does not reference service packs. 3) It should have some GUI friendly way to invoke it without "alt-f2 / kdesu -c yast2 wagon". 4) It should grow the ability to disable all the old repos and add the new ones. With all the above, it would easily be the preferred upgrade path for all users due to ease of use. Currently, it adds little functionality over zypper dup, but I still think it is more user friendly than zypper dup if for no reason other than it automates the "renew upgrade stack" step which at least for 11.1 => 11.2 was recommended as a end-user step. (ie. zypper in zypper after updating the repos and before zypper dup.) Greg -- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org For additional commands, e-mail: opensuse-factory+help@opensuse.org