Merge lp://qastaging/~mterry/update-manager/update-at-start into lp://qastaging/update-manager
Proposed by
Michael Terry
Status: | Merged |
---|---|
Approved by: | Barry Warsaw |
Approved revision: | 2441 |
Merged at revision: | 2504 |
Proposed branch: | lp://qastaging/~mterry/update-manager/update-at-start |
Merge into: | lp://qastaging/update-manager |
Diff against target: |
896 lines (+148/-397) 8 files modified
UpdateManager/UnitySupport.py (+0/-9) UpdateManager/UpdateManager.py (+22/-168) UpdateManager/UpdateProgress.py (+84/-0) UpdateManager/backend/InstallBackendAptdaemon.py (+11/-5) data/com.ubuntu.update-manager.gschema.xml.in (+0/-5) data/gtkbuilder/UpdateManager.ui (+14/-206) data/update-manager.convert (+0/-1) update-manager (+17/-3) |
To merge this branch: | bzr merge lp://qastaging/~mterry/update-manager/update-at-start |
Related bugs: |
Reviewer | Review Type | Date Requested | Status |
---|---|---|---|
Barry Warsaw (community) | Approve | ||
Michael Vogt | Pending | ||
Review via email:
|
Description of the change
Implements the 'update on start' aspect of the new spec.
This means that all ways to manually start an update are gone from the UI. We no longer warn about how long it's been since the last update, etc.
I've added a new class to handle the initial progress dialog. It just seemed cleaner to me to do it that way rather than introduce more possible states to the main dialog's class. Especially since so little of that class is relevant to the progress dialog.
The progress dialog doesn't look quite like it does in the spec yet. That will require changes to aptdaemon's progress dialog widget. But those can be done separately.
To post a comment you must log in.
Note that I also filed https:/ /code.launchpad .net/~mterry/ update- notifier/ use-no- update/ +merge/ 108377 to have update-notifier pass --no-update when launching update-manager.