Merge ~ahasenack/ubuntu/+source/update-notifier:trusty-update-notifier-esm-aware into ubuntu/+source/update-notifier:ubuntu/trusty-devel
Status: | Approved | ||||
---|---|---|---|---|---|
Approved by: | Andreas Hasenack | ||||
Approved revision: | 5bb0d847fa516e05c3a2cbe33a5cf4f3567a35a0 | ||||
Proposed branch: | ~ahasenack/ubuntu/+source/update-notifier:trusty-update-notifier-esm-aware | ||||
Merge into: | ubuntu/+source/update-notifier:ubuntu/trusty-devel | ||||
Diff against target: |
28 lines (+8/-1) 2 files modified
data/apt_check.py (+1/-1) debian/changelog (+7/-0) |
||||
Related bugs: |
|
Reviewer | Review Type | Date Requested | Status |
---|---|---|---|
Bryce Harrington (community) | Approve | ||
Canonical Server packageset reviewers | Pending | ||
Review via email: mp+386205@code.staging.launchpad.net |
Description of the change
The linked SRU bug has testing instructions and other information.
I'd just like to highlight here as well that the UbuntuESMApps change is just to future-proof the client (if such a thing as future-proofing exists in software ;). At the moment, ESM for Apps only exists for xenial iiuc. Therefore, I have no way of testing it for trusty. At most, I could apply the same change to a xenial package, and then test it, but ubuntu-notifier doesn't know much about ESM in its xenial encarnation, since the ESM srus have been focused on trusty only so far.
PPA: https:/
There was an error fetching revisions from git servers. Please try again in a few minutes. If the problem persists, contact Launchpad support.
While testing the esm for apps bit with a hack, to fake lsb-release into thinking it's a xenial system, I found out that the current patck is mixing esm-infra and esm-apps security updates into just esm-infra:
"""
3 of these updates are provided through UA Infrastructure ESM.
"""
The statement above is mixing both repositories, but stating that it's only counting infra.
I'll suggest to just remove "Infrastructure" from that phrasing.