Merge lp:~bjornt/landscape-client/apt-upgrade-all-packages into lp:~landscape/landscape-client/trunk
Proposed by
Björn Tillenius
Status: | Merged |
---|---|
Approved by: | Alberto Donato |
Approved revision: | 435 |
Merged at revision: | 432 |
Proposed branch: | lp:~bjornt/landscape-client/apt-upgrade-all-packages |
Merge into: | lp:~landscape/landscape-client/trunk |
Diff against target: |
273 lines (+81/-39) 3 files modified
landscape/package/changer.py (+1/-3) landscape/package/facade.py (+14/-15) landscape/package/tests/test_facade.py (+66/-21) |
To merge this branch: | bzr merge lp:~bjornt/landscape-client/apt-upgrade-all-packages |
Related bugs: |
Reviewer | Review Type | Date Requested | Status |
---|---|---|---|
Alberto Donato (community) | Approve | ||
Free Ekanayaka (community) | Approve | ||
Review via email: mp+88688@code.launchpad.net |
Description of the change
Ask Apt to upgrade the whole system, rather than marking each package
for upgrade when the server requests a general system upgrade. This
makes the system upgrade holds for dependencies.
I'm making a dist-upgrade, because the existing tests require it. It's
easy to change, if we want a normal apt-get upgrade.
To post a comment you must log in.
I believe we don't want dist-upgrade, as it can have quite disruptive effects like removing packages, or replacing postgres-8 with postgres-9 (in principle).
Also I didn't look at the code very in depth, but will this have really the same behavior as before? The important thing is to go back to the server if there are package changes that haven't been explicitly requested by the server (with install/remove messages) and that are not allowed by the auto-apply policy in effect.