|
Bugzilla – Full Text Bug Listing |
| Summary: | yast2 online update doesn't restart itself after installing pkg-management patches | ||
|---|---|---|---|
| Product: | [openSUSE] openSUSE 11.1 | Reporter: | Jiří Suchomel <jsuchome> |
| Component: | YaST2 | Assignee: | Ladislav Slezák <lslezak> |
| Status: | RESOLVED FIXED | QA Contact: | Jiri Srain <jsrain> |
| Severity: | Major | ||
| Priority: | P5 - None | CC: | coolo, dmueller, jsrain, jsuchome, lslezak, meissner |
| Version: | RC 2 | Flags: | coolo:
SHIP_STOPPER-
|
| Target Milestone: | --- | ||
| Hardware: | Other | ||
| OS: | Other | ||
| Whiteboard: | maint:running:21337 maint:released:11.1:22228 | ||
| Found By: | --- | Services Priority: | |
| Business Priority: | Blocker: | --- | |
| Marketing QA Status: | --- | IT Deployment: | --- |
| Attachments: |
proposed patch for online_update.ycp
patch for /usr/share/YaST2/clients/menu.ycp |
||
|
Description
Jiří Suchomel
2008-12-08 09:08:25 UTC
Created attachment 258544 [details]
proposed patch for online_update.ycp
In online_update.ycp, the negative return value cannot be used any more.
Created attachment 258545 [details]
patch for /usr/share/YaST2/clients/menu.ycp
In menu.ycp, don't check for return value of online-update, but rather for file created...
Hmm, fixing this with a patch is hard. But then again yast online-update is not our default, so I have mixed feelings (taking that the fab waits ;( 10:47 < coolo> what does "nothing happens" mean? does the user has to restart himself or is the old update stack continueing? 10:47 < jsuchome> but it's up to you, of course... I guess first patch with yast stack will be out soon 10:47 < jsuchome> this is not during installation, only on installed system 10:48 < jsuchome> so there's nothing to continue, yast just finishes 10:48 < jsuchome> and user can start online update manually, yes So this is just a glitch IMO and we should fix it with online update. In my opinion: YOU works well enough, and since there are other methods, we do not need to fix it in the goldmaster. OK, lowering severity. As one part of the solution, yast2-online-update can't return integer value any more. This is in yast2-online-update-2.17.13. menu.ycp is fixed in yast2-2.17.59 Coolo, I think this should be released for openSUSE as an update. Should I start with patchinfos or do we have some common one? I mean packages yast2-2.17.59 and yast2-online-update-2.17.13. yast2-2.17.59 also contains the fix for bug 450528, which was not released with openSUSE, but I expect its realease as well. swampid see whiteboard: maint:running:21337 Summing up again - the patch needs these packages: yast2-online-update >= 2.17.13 yast2 >= 2.17.59 yast2-pkg-bindings >= 2.17.31 Ladislav, there are already some new yast2 and yast2-pkg-bindings in Code11 svn, should they be included (= are they related to the new stuff added by fixing these bugs)? There are new unrelated functions which need the latest libzypp, for that reason I'd rather not submit the latest version (2.17.32). I'll submit yast2=pkg-bindings-2.17.31 to 11.1. I've already submitted yast2-online-update-2.17.13 and yast2-2.17.59 to 11.1. Please close the bug as fixed when you submit yast2-pkg-bindings yast2-pkg-bindings-2.17.31. has just been submitted to 11.1, resolving as FIXED. Update released for: gnome-packagekit, gnome-packagekit-lang, libqdialogsolver1, libqdialogsolver1-devel, libsatsolver, libsatsolver-devel, libzypp, libzypp-debuginfo, libzypp-debugsource, libzypp-devel, perl-satsolver, python-satsolver, ruby-satsolver, satsolver-tools, yast2, yast2-devel-doc, yast2-online-update, yast2-online-update-frontend, yast2-pkg-bindings, yast2-pkg-bindings-debuginfo, yast2-pkg-bindings-debugsource, zypper Products: openSUSE 11.1 (debug, i586, ppc, x86_64) |