Bugzilla – Bug 116213
Yast Feature
Last modified: 2005-10-04 09:23:07 UTC
In Yast a Retry Butten would be completely helpful when installing new software. If the servers or the connection precipitates remains the procedure mostly hanging. If those InterNet connection or the server is overloaded remains the procedure hanging. A "Retry"Button or a AutoRetry function would be perhaps very good. Apology for my bad Englich I used Google Translate:)
For the assignee: When downloading packages via a remote connection, YaST offers no way to resume the download once it has failed (i.e. due to a broken connection). Would be handy if there was some retry-button.
Jiri? If the DoneProvide callback returned RETRY, the packagemanager should already honour it. So it's probabely just the button missing.
There is a "Retry" button, according to the sources. Just the callbacks doesn't return 'RETRY', but only 'R' (and similar for abort button). What are the right return codes of this callback?
There's little chance to miss it ;) "r" -> RETRY "re" -> RETRY "ret" -> RETRY "retr" -> RETRY "retry" -> RETRY "R" -> RETRY "RE" -> RETRY "RET" -> RETRY "RETR" -> RETRY "RETRY" -> RETRY The same for: case CBSuggest::PROCEED: // return original error case CBSuggest::SKIP: // skip current media case CBSuggest::CANCEL: // cancel all case CBSuggest::RETRY: // retry ! Any abreviation of the enum name will do.
NB: PROCEED:"return original error" includes 'no error' as well. Proceed means 'do what seems to be appropriate'. You'll get the same behaviour, as if there is no Callback listening at all. If you'd return an unknown or empty string, it will mean PROCEED. Thus it's safe for you to return "" if ther's no advice , and otherwise 'SKIP|CANCEL|RETRY'.
Hmm, looking into the sources, the DoneProvide callback (provided the error is not 0) always ask what to do. I also tested it, if downloading package failed, user is asked, one of possibilities is RETRY. So, marking as WORKSFORME.