Merge lp:~ahasenack/landscape-client/17.03-backports-fix into lp:~landscape/landscape-client/17.03
Status: | Merged |
---|---|
Approved by: | Andreas Hasenack |
Approved revision: | 944 |
Merged at revision: | 941 |
Proposed branch: | lp:~ahasenack/landscape-client/17.03-backports-fix |
Merge into: | lp:~landscape/landscape-client/17.03 |
Diff against target: |
178 lines (+115/-11) 3 files modified
debian/changelog (+8/-11) landscape/package/reporter.py (+19/-0) landscape/package/tests/test_reporter.py (+88/-0) |
To merge this branch: | bzr merge lp:~ahasenack/landscape-client/17.03-backports-fix |
Related bugs: |
Reviewer | Review Type | Date Requested | Status |
---|---|---|---|
🤖 Landscape Builder | test results | Approve | |
Adam Collard (community) | Approve | ||
Alberto Donato (community) | Approve | ||
Review via email: mp+321115@code.launchpad.net |
Commit message
Backport fix for #1668583 (don't report backport packages) from trunk r962.
Description of the change
Backport fix for #1668583 (don't report backport packages) from trunk r962.
We want 17.03 client builds to populate ppa:landscape/
The current LP recipe for builds out of this 17.03 branch is:
# bzr-builder format 0.3 deb-version {debupstream}
lp:~landscape/landscape-client/17.03
This means that with a plain "17.03" in debian/changelog, we would get a package like this:
17.03-0~941
Which could make one think this is trunk r941 if you just look at that version without the context of which branch it was built from.
Therefore, I also changed the "debupstream" version of the package in debian/changelog so it's clear this is still client r940 from trunk *plus* the r962 fix.
In the end, the recipe will give us a build with a version like this:
17.03~bzr940-0~941
It's still not super clear where this build came from, though. We could use "17.03~
+1