Merge lp:~bjornt/landscape-client/lxd-update-fail into lp:~landscape/landscape-client/trunk
Status: | Merged |
---|---|
Approved by: | Adam Collard |
Approved revision: | 961 |
Merged at revision: | 962 |
Proposed branch: | lp:~bjornt/landscape-client/lxd-update-fail |
Merge into: | lp:~landscape/landscape-client/trunk |
Diff against target: |
151 lines (+107/-0) 2 files modified
landscape/package/reporter.py (+19/-0) landscape/package/tests/test_reporter.py (+88/-0) |
To merge this branch: | bzr merge lp:~bjornt/landscape-client/lxd-update-fail |
Related bugs: |
Reviewer | Review Type | Date Requested | Status |
---|---|---|---|
Alberto Donato (community) | Approve | ||
Adam Collard (community) | Approve | ||
🤖 Landscape Builder | test results | Approve | |
Review via email: mp+320213@code.launchpad.net |
Commit message
Don't report packages that are coming from backports.
The reason for this is that backports are enabled by default from
xenial, but landscape doesn't handle that well, since we don't support
pinning properly.
If we report packages from backports, it means that Landscape will
upgrade to those version if you use an upgrade profile or select all
upgrades to their latest versions.
Description of the change
Don't report packages that are coming from backports.
The reason for this is that backports are enabled by default from
xenial, but landscape doesn't handle that well, since we don't support
pinning properly.
If we report packages from backports, it means that Landscape will
upgrade to those version if you use an upgrade profile or select all
upgrades to their latest versions.
Testing instructions:
Use this branch for a xenial machine that has lxd installed
Register it with Landscape
Ensure that Landscape doesn't off to upgrade lxd to 2.8
Command: TRIAL_ARGS=-j4 make check /ci.lscape. net/job/ latch-test- xenial/ 3638/
Result: Success
Revno: 961
Branch: lp:~bjornt/landscape-client/lxd-update-fail
Jenkins: https:/