Merge ~powersj/ubuntu/+source/logcheck:xenial-1357880 into ~usd-import-team/ubuntu/+source/logcheck:ubuntu/xenial-devel
| Status: | Merged |
|---|---|
| Merge reported by: | Nish Aravamudan |
| Merged at revision: | 8861f4bb8f34585e2670aa1a0e521787b8f17a1d |
| Proposed branch: | ~powersj/ubuntu/+source/logcheck:xenial-1357880 |
| Merge into: | ~usd-import-team/ubuntu/+source/logcheck:ubuntu/xenial-devel |
| Diff against target: |
74 lines (+23/-27) 3 files modified
debian/changelog (+6/-0) debian/control (+2/-1) rulefiles/linux/ignore.d.server/dhclient (+15/-26) |
| Related bugs: |
| Reviewer | Review Type | Date Requested | Status |
|---|---|---|---|
| Nish Aravamudan | 2017-08-04 | Approve on 2017-08-07 | |
| Andreas Hasenack (community) | 2017-07-20 | Approve on 2017-07-20 | |
| Canonical Server Team | 2017-07-24 | Pending | |
|
Review via email:
|
|||
This proposal supersedes a proposal from 2017-07-19.
| Andreas Hasenack (ahasenack) wrote : | # |
| Joshua Powers (powersj) wrote : | # |
Resubmitted against xenial-devel
- 8861f4b... by Joshua Powers on 2017-07-20
| Andreas Hasenack (ahasenack) wrote : | # |
Looks good. Verified:
- one commit per change, plus changelog and metadata (maintainer)
- same fix is upstream (https:/
- fix works as expected (followed the SRU test case)
- also induced dhclient errors, to see if they would be let through and show up in the logcheck report, and they were
- checked SRU package version and that it will upgrade to Xenial+1
+1
| Joshua Powers (powersj) wrote : | # |
Thanks @ahasenack
Need a sponsor now, please :)
| Nish Aravamudan (nacc) wrote : | # |
$ git ubuntu lint powersj/
E: Version (1.3.17ubuntu0.1) does not match expected version (1.3.17ubuntu0.
Some lint checks failed. Please investigate.
This is a false positive because "vivid" shows up in the active series list.
@Robie, do we want to hardcode that "vivid" is not active in our series functions?
| Robie Basak (racb) wrote : | # |
AIUI, Vivid was active because of the phone. In the past, I've asked for accommodation for Vivid in calculating version numbers in SRUs because otherwise we'd be giving (minor) trouble to phone developers who may want to SRU the same package in Vivid.
This seems unlikely for the phone now, particularly for logcheck. But I don't see a particular reason for the lint to make an exception here. It's being consistent, and that consistency is easier to teach new developers. It's also easier to review: I'm not sure I'd reject 1.3.17ubuntu0.1 in an SRU review, but 1.3.17ubuntu0.
| Nish Aravamudan (nacc) wrote : | # |
On Wed, Aug 2, 2017 at 4:01 PM, Robie Basak <email address hidden> wrote:
> AIUI, Vivid was active because of the phone. In the past, I've asked for accommodation for Vivid in calculating version numbers in SRUs because otherwise we'd be giving (minor) trouble to phone developers who may want to SRU the > same package in Vivid.
This is a good point, it's consistent to require the 16.04.1 since
vivid version == xenial version.
>
> This seems unlikely for the phone now, particularly for logcheck. But I don't see a particular reason for the lint to make an exception here. It's being consistent, and that consistency is easier to teach new developers. It's also easier to
> review: I'm not sure I'd reject 1.3.17ubuntu0.1 in an SRU review, but 1.3.17ubuntu0.
Yep, so maybe it's *not* a false positive :)
| Joshua Powers (powersj) wrote : | # |
> > review: I'm not sure I'd reject 1.3.17ubuntu0.1 in an SRU review, but
> 1.3.17ubuntu0.
> considering edge cases in order to conclude that 1.3.17ubuntu0.1 is OK.
>
> Yep, so maybe it's *not* a false positive :)
Would you like me to update the version such that lint works or is this good to go?
| Nish Aravamudan (nacc) wrote : | # |
Upload tagged and sponsored.


Could you please re-target this against ubuntu/ xenial- devel?