http://bugzilla.novell.com/show_bug.cgi?id=613820
http://bugzilla.novell.com/show_bug.cgi?id=613820#c26
--- Comment #26 from Greg Freemyer
It is not easy to test :-(
1) As of now there is still nothing in the above repo because the build service is busy (probably with GM). Within an hour the package should be in this repo: http://www.suse.de/~mvidner/wagon
2) The package will not be considered because of a vendor change. I had a dependency problem with snmp which put me into the package dialog where I was able to manually change the yast2-wagon selection to the fixed package. This will not be necessary if the package is built in the official repo (Factory or 11.3 or update).
Martin, I just re-read the last line of your comment. Are you saying that if the fix goes into the 11.3 "update" repo only and a 11.2 upgrader adds the 11.3 OSS, NON-OSS, and UPDATE repos prior to running Wagon it should work? I tend not to run the "zypper dup" / "wagon" upgrades with the update repo active, so that methodology never crossed my mind until right now. (especially since it can't be tested during the factory timeframe.) If that is the way this works out, we will need to ensure that is reflected on: http://en.opensuse.org/Wagon And any other release notes etc. I still very much would have preferred this get into the OSS repo, especially since running Wagon with just the 11.3 OSS repo as it currently stands breaks the full yast stack. Fortunately the fix is to drop down to CLI and do a "zypper dup" to complete the upgrade, so there is a reasonable workaround. Greg -- Configure bugmail: http://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.