Merge ~sespiros/ubuntu-security-tools/+git/ubuntu-security-tools:esm-chroot-names-3 into ubuntu-security-tools:master
Status: | Merged |
---|---|
Merged at revision: | 4533396465317ea642a286fe8b9e81a676bd42aa |
Proposed branch: | ~sespiros/ubuntu-security-tools/+git/ubuntu-security-tools:esm-chroot-names-3 |
Merge into: | ubuntu-security-tools:master |
Diff against target: |
94 lines (+21/-21) 1 file modified
build-tools/umt (+21/-21) |
Related bugs: |
Reviewer | Review Type | Date Requested | Status |
---|---|---|---|
Alex Murray | Approve | ||
Eduardo Barretto | Pending | ||
Review via email: mp+424782@code.launchpad.net |
Commit message
Reverting previous changes to chroot name handling for a potentially better approach.
1) A bug was fixed in umt so that ESM releases gets properly detected from the file path and matched against the release_list in .ubuntu-
2) Since chroot names cannot have a '/' (similarly to the paths when downloading a package for an ESM release), '/' is replaced with '_' to match release names.
3) With 1,2 in place, chroot names for ESM can follow the standard convention of <release>-<arch> so that they are detected automatically from umt. The difference now is that <release> can be any of the form esm-X_<
LGTM but I think perhaps it would be nicer to avoid all the duplicated code for the chroot release name - see suggestion inline.