-
Notifications
You must be signed in to change notification settings - Fork 6
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Adjust ESM Release file to match default unattended-upgrades behavior #43
Comments
Discussed with Adam Conrad that we don't want to misrepresent the esm archive as being an archive it isn't. We need Origin and Suite set but should not collide with the main archive. Instead we will SRU unattended-upgrades to additionally recognize the ESM archive and enable it by default. So the values we want are: (Suite: precise-security might be more conceptually correct, but we are concerned that presenting a value that doesn't match the archive file path could cause tool confusion.) |
I deployed this charm and these are the results (10.55.60.98 is my test deployment server):
The "
|
@panlinux I changed the template to use the Origin value as Label too. AFAIU the label is just a description, but it makes more sense for it to match the origin than the suite. |
unattended-upgrades by default matches on the release and security pockets of only the official Ubuntu release. This relies on the following fields in the archive Release file for a correct match:
Origin: Ubuntu
Suite: precise-security
According to STS, these are not present in the Release file for the ESM archive. Please add them.
The text was updated successfully, but these errors were encountered: