Merge ~renanrodrigo/ubuntu/+source/update-notifier:esm-cache-update-xenial into ubuntu/+source/update-notifier:ubuntu/xenial-devel
Proposed by
Renan Rodrigo
Status: | Merged |
---|---|
Merged at revision: | 2391d6471e9a80747127158e2bd20adf962348b0 |
Proposed branch: | ~renanrodrigo/ubuntu/+source/update-notifier:esm-cache-update-xenial |
Merge into: | ubuntu/+source/update-notifier:ubuntu/xenial-devel |
Diff against target: |
109 lines (+29/-32) 1 file modified
data/apt_check.py (+29/-32) |
Related bugs: |
Reviewer | Review Type | Date Requested | Status |
---|---|---|---|
Ubuntu Core Development Team | Pending | ||
Review via email: mp+436035@code.launchpad.net |
Description of the change
Rely on the Pro Client apt esm cache to check for esm updates
The Pro Client is not pinnning esm repositores and adding them to the system apt anymore, but using a separate cache instead.
To post a comment you must log in.
I checked how other recent xenial uploads landed (as it is in ESM mode), but it seems they were handled just "normal" which is fine. I'm following the same path.
Since there are no git branches for xenial in the recent team owned git I've followed Renan's proposed git-ubuntu approach.
This made me do another few checks to see if that change of internal structure affects it.
I was wondering about the symlink that we've seen in later versions, but that doesn't exist at all in the xenial version - so the change of repositories can't break it either \o/.
It is now uploaded it including proper VCS info in .changes - should switch to merged once accepted.
Needed some extra steps to convince dput-ng to let it through.