| 2017-04-28 23:19:18 |
Adam Conrad |
bug |
|
|
added bug |
| 2017-04-28 23:19:34 |
Adam Conrad |
bug |
|
|
added subscriber Steve Langasek |
| 2017-05-02 17:38:45 |
Brian Murray |
nominated for series |
|
Ubuntu Precise |
|
| 2017-05-02 17:38:45 |
Brian Murray |
bug task added |
|
unattended-upgrades (Ubuntu Precise) |
|
| 2017-05-02 17:38:52 |
Brian Murray |
unattended-upgrades (Ubuntu Precise): status |
New |
Triaged |
|
| 2017-05-02 17:38:55 |
Brian Murray |
unattended-upgrades (Ubuntu Precise): importance |
Undecided |
High |
|
| 2017-05-03 12:52:42 |
Adam Conrad |
unattended-upgrades (Ubuntu Precise): status |
Triaged |
Fix Committed |
|
| 2017-05-03 12:52:44 |
Adam Conrad |
bug |
|
|
added subscriber Ubuntu Stable Release Updates Team |
| 2017-05-03 12:52:49 |
Adam Conrad |
bug |
|
|
added subscriber SRU Verification |
| 2017-05-03 12:52:55 |
Adam Conrad |
tags |
|
verification-needed |
|
| 2017-05-03 13:19:32 |
Launchpad Janitor |
unattended-upgrades (Ubuntu): status |
New |
Confirmed |
|
| 2017-05-03 13:19:39 |
Dominique Poulain |
bug |
|
|
added subscriber Dominique Poulain |
| 2017-05-03 15:49:00 |
Steve Langasek |
description |
When the dust has settled on the ESM archive Release file format[1], unattended-upgrades needs to be tweaked to match.
[1] https://github.com/CanonicalLtd/archive-auth-mirror/issues/43 |
[SRU Justification]
When the dust has settled on the ESM archive Release file format[1], unattended-upgrades needs to be tweaked to match.
[1] https://github.com/CanonicalLtd/archive-auth-mirror/issues/43
Since the ESM archive contains packages updated by the Ubuntu Security team, we should ensure the behavior of unattended-upgrades applies the same default policy to both.
[Test case]
1. run 'sudo apt-get install ubuntu-advantage-tools unattended-upgrades'
2. run 'sudo ubuntu-advantage enable-esm <creds>' with your private creds enable the ESM archive
3. run 'sudo apt-get update'
4. create a faked-up entry in /var/lib/apt/lists/esm.ubuntu.com_ubuntu_dists_precise_main_binary-amd64_Packages for the unattended-upgrades package with a higher version number
5. ?? |
|
| 2017-05-03 16:17:16 |
Mathieu Trudel-Lapierre |
description |
[SRU Justification]
When the dust has settled on the ESM archive Release file format[1], unattended-upgrades needs to be tweaked to match.
[1] https://github.com/CanonicalLtd/archive-auth-mirror/issues/43
Since the ESM archive contains packages updated by the Ubuntu Security team, we should ensure the behavior of unattended-upgrades applies the same default policy to both.
[Test case]
1. run 'sudo apt-get install ubuntu-advantage-tools unattended-upgrades'
2. run 'sudo ubuntu-advantage enable-esm <creds>' with your private creds enable the ESM archive
3. run 'sudo apt-get update'
4. create a faked-up entry in /var/lib/apt/lists/esm.ubuntu.com_ubuntu_dists_precise_main_binary-amd64_Packages for the unattended-upgrades package with a higher version number
5. ?? |
[Impact]
ESM users relying on unattended upgrades.
[Test cases]
This requires a system installed with Ubuntu 12.04 and Ubuntu Advantage credentials.
1) install ubuntu-advantage-tools and unattended upgrades
2) run 'sudo ubuntu-advantage enable-esm'; supply credentials for Ubuntu Advantage
3) run 'sudo apt-get update'
4) fake up the contents of /var/lib/apt/lists/esm.ubuntu.com_ubuntu_dists_precise_main_binary-amd64_Packages to list a newer version of unattended-upgrades
5) run 'sudo unattended-upgrades --debug --apt-debug'
[Regression potential]
---
When the dust has settled on the ESM archive Release file format[1], unattended-upgrades needs to be tweaked to match.
[1] https://github.com/CanonicalLtd/archive-auth-mirror/issues/43 |
|
| 2017-05-03 17:34:50 |
Steve Langasek |
description |
[Impact]
ESM users relying on unattended upgrades.
[Test cases]
This requires a system installed with Ubuntu 12.04 and Ubuntu Advantage credentials.
1) install ubuntu-advantage-tools and unattended upgrades
2) run 'sudo ubuntu-advantage enable-esm'; supply credentials for Ubuntu Advantage
3) run 'sudo apt-get update'
4) fake up the contents of /var/lib/apt/lists/esm.ubuntu.com_ubuntu_dists_precise_main_binary-amd64_Packages to list a newer version of unattended-upgrades
5) run 'sudo unattended-upgrades --debug --apt-debug'
[Regression potential]
---
When the dust has settled on the ESM archive Release file format[1], unattended-upgrades needs to be tweaked to match.
[1] https://github.com/CanonicalLtd/archive-auth-mirror/issues/43 |
[SRU Justification]
When the dust has settled on the ESM archive Release file format[1], unattended-upgrades needs to be tweaked to match.
[1] https://github.com/CanonicalLtd/archive-auth-mirror/issues/43
Since the ESM archive contains packages updated by the Ubuntu Security team, we should ensure the behavior of unattended-upgrades applies the same default policy to both.
[Test case]
1. run 'sudo apt-get install ubuntu-advantage-tools unattended-upgrades'
2. run 'sudo ubuntu-advantage enable-esm <creds>' with your private creds to enable the ESM archive
3. run 'sudo apt-get update'
4. create a faked-up entry in /var/lib/apt/lists/esm.ubuntu.com_ubuntu_dists_precise_main_binary-amd64_Packages for the unattended-upgrades package with a higher version number
5. run 'sudo unattended-upgrades --debug --apt-debug' and verify that no unattended-upgrades package is installed.
6. install unattended-upgrades from -proposed.
7. again create a faked-up entry in /var/lib/apt/lists/esm.ubuntu.com_ubuntu_dists_precise_main_binary-amd64_Packages for the unattended-upgrades package with a higher version number
8. run 'sudo unattended-upgrades --debug --aptdebug' and verify that it tries to install a new unattended-upgrades package (though this will fail).
[Regression potential]
--- |
|
| 2017-05-03 17:38:53 |
Steve Langasek |
description |
[SRU Justification]
When the dust has settled on the ESM archive Release file format[1], unattended-upgrades needs to be tweaked to match.
[1] https://github.com/CanonicalLtd/archive-auth-mirror/issues/43
Since the ESM archive contains packages updated by the Ubuntu Security team, we should ensure the behavior of unattended-upgrades applies the same default policy to both.
[Test case]
1. run 'sudo apt-get install ubuntu-advantage-tools unattended-upgrades'
2. run 'sudo ubuntu-advantage enable-esm <creds>' with your private creds to enable the ESM archive
3. run 'sudo apt-get update'
4. create a faked-up entry in /var/lib/apt/lists/esm.ubuntu.com_ubuntu_dists_precise_main_binary-amd64_Packages for the unattended-upgrades package with a higher version number
5. run 'sudo unattended-upgrades --debug --apt-debug' and verify that no unattended-upgrades package is installed.
6. install unattended-upgrades from -proposed.
7. again create a faked-up entry in /var/lib/apt/lists/esm.ubuntu.com_ubuntu_dists_precise_main_binary-amd64_Packages for the unattended-upgrades package with a higher version number
8. run 'sudo unattended-upgrades --debug --aptdebug' and verify that it tries to install a new unattended-upgrades package (though this will fail).
[Regression potential]
--- |
[SRU Justification]
When the dust has settled on the ESM archive Release file format[1], unattended-upgrades needs to be tweaked to match.
[1] https://github.com/CanonicalLtd/archive-auth-mirror/issues/43
Since the ESM archive contains packages updated by the Ubuntu Security team, we should ensure the behavior of unattended-upgrades applies the same default policy to both.
[Test case]
1. run 'sudo apt-get install ubuntu-advantage-tools unattended-upgrades'
2. run 'sudo ubuntu-advantage enable-esm <creds>' with your private creds to enable the ESM archive
3. run 'sudo apt-get update'
4. create a faked-up entry in /var/lib/apt/lists/esm.ubuntu.com_ubuntu_dists_precise_main_binary-amd64_Packages for the unattended-upgrades package with a higher version number
5. run 'sudo unattended-upgrades --debug --dry-run' and verify that no unattended-upgrades package is installed.
6. install unattended-upgrades from -proposed.
7. again create a faked-up entry in /var/lib/apt/lists/esm.ubuntu.com_ubuntu_dists_precise_main_binary-amd64_Packages for the unattended-upgrades package with a higher version number
8. run 'sudo unattended-upgrades --debug --dry-run' and verify that it offers to install a new unattended-upgrades package.
[Regression potential]
Worst-case scenario is a bug that prevents future security updates from being applied correctly. This is not a concern for precise because there will be no further security updates /except/ those enabled by this SRU, but this SRU should also be included in all later stable releases. |
|
| 2017-05-03 21:49:06 |
Steve Langasek |
tags |
verification-needed |
verification-done-precise |
|
| 2017-05-04 16:23:12 |
Launchpad Janitor |
unattended-upgrades (Ubuntu Precise): status |
Fix Committed |
Fix Released |
|
| 2017-05-04 16:23:19 |
Brian Murray |
removed subscriber Ubuntu Stable Release Updates Team |
|
|
|
| 2017-05-08 19:17:17 |
Adam Conrad |
unattended-upgrades (Ubuntu Trusty): status |
New |
Fix Committed |
|
| 2017-05-08 19:17:22 |
Adam Conrad |
bug |
|
|
added subscriber Ubuntu Stable Release Updates Team |
| 2017-05-08 19:17:28 |
Adam Conrad |
tags |
verification-done-precise |
verification-done-precise verification-needed |
|
| 2017-05-08 19:24:13 |
Adam Conrad |
unattended-upgrades (Ubuntu Xenial): status |
New |
Fix Committed |
|
| 2017-05-08 19:25:22 |
Adam Conrad |
unattended-upgrades (Ubuntu Yakkety): status |
New |
Fix Committed |
|
| 2017-05-08 19:26:46 |
Adam Conrad |
unattended-upgrades (Ubuntu Zesty): status |
New |
Fix Committed |
|
| 2017-05-12 00:12:59 |
Steve Langasek |
description |
[SRU Justification]
When the dust has settled on the ESM archive Release file format[1], unattended-upgrades needs to be tweaked to match.
[1] https://github.com/CanonicalLtd/archive-auth-mirror/issues/43
Since the ESM archive contains packages updated by the Ubuntu Security team, we should ensure the behavior of unattended-upgrades applies the same default policy to both.
[Test case]
1. run 'sudo apt-get install ubuntu-advantage-tools unattended-upgrades'
2. run 'sudo ubuntu-advantage enable-esm <creds>' with your private creds to enable the ESM archive
3. run 'sudo apt-get update'
4. create a faked-up entry in /var/lib/apt/lists/esm.ubuntu.com_ubuntu_dists_precise_main_binary-amd64_Packages for the unattended-upgrades package with a higher version number
5. run 'sudo unattended-upgrades --debug --dry-run' and verify that no unattended-upgrades package is installed.
6. install unattended-upgrades from -proposed.
7. again create a faked-up entry in /var/lib/apt/lists/esm.ubuntu.com_ubuntu_dists_precise_main_binary-amd64_Packages for the unattended-upgrades package with a higher version number
8. run 'sudo unattended-upgrades --debug --dry-run' and verify that it offers to install a new unattended-upgrades package.
[Regression potential]
Worst-case scenario is a bug that prevents future security updates from being applied correctly. This is not a concern for precise because there will be no further security updates /except/ those enabled by this SRU, but this SRU should also be included in all later stable releases. |
[SRU Justification]
When the dust has settled on the ESM archive Release file format[1], unattended-upgrades needs to be tweaked to match.
[1] https://github.com/CanonicalLtd/archive-auth-mirror/issues/43
Since the ESM archive contains packages updated by the Ubuntu Security team, we should ensure the behavior of unattended-upgrades applies the same default policy to both.
[Test case]
1. run 'sudo apt-get install ubuntu-advantage-tools unattended-upgrades ca-certificates'
2. run 'sudo ubuntu-advantage enable-esm <creds>' with your private creds to enable the ESM archive
3. run 'sudo apt-get update'
4. create a faked-up entry in /var/lib/apt/lists/esm.ubuntu.com_ubuntu_dists_precise_main_binary-amd64_Packages for the unattended-upgrades package with a higher version number
5. run 'sudo unattended-upgrades --debug --dry-run' and verify that no unattended-upgrades package is installed.
6. install unattended-upgrades from -proposed.
7. again create a faked-up entry in /var/lib/apt/lists/esm.ubuntu.com_ubuntu_dists_precise_main_binary-amd64_Packages for the unattended-upgrades package with a higher version number
8. run 'sudo unattended-upgrades --debug --dry-run' and verify that it offers to install a new unattended-upgrades package.
[Regression potential]
Worst-case scenario is a bug that prevents future security updates from being applied correctly. This is not a concern for precise because there will be no further security updates /except/ those enabled by this SRU, but this SRU should also be included in all later stable releases. |
|
| 2017-05-12 00:23:51 |
Steve Langasek |
description |
[SRU Justification]
When the dust has settled on the ESM archive Release file format[1], unattended-upgrades needs to be tweaked to match.
[1] https://github.com/CanonicalLtd/archive-auth-mirror/issues/43
Since the ESM archive contains packages updated by the Ubuntu Security team, we should ensure the behavior of unattended-upgrades applies the same default policy to both.
[Test case]
1. run 'sudo apt-get install ubuntu-advantage-tools unattended-upgrades ca-certificates'
2. run 'sudo ubuntu-advantage enable-esm <creds>' with your private creds to enable the ESM archive
3. run 'sudo apt-get update'
4. create a faked-up entry in /var/lib/apt/lists/esm.ubuntu.com_ubuntu_dists_precise_main_binary-amd64_Packages for the unattended-upgrades package with a higher version number
5. run 'sudo unattended-upgrades --debug --dry-run' and verify that no unattended-upgrades package is installed.
6. install unattended-upgrades from -proposed.
7. again create a faked-up entry in /var/lib/apt/lists/esm.ubuntu.com_ubuntu_dists_precise_main_binary-amd64_Packages for the unattended-upgrades package with a higher version number
8. run 'sudo unattended-upgrades --debug --dry-run' and verify that it offers to install a new unattended-upgrades package.
[Regression potential]
Worst-case scenario is a bug that prevents future security updates from being applied correctly. This is not a concern for precise because there will be no further security updates /except/ those enabled by this SRU, but this SRU should also be included in all later stable releases. |
[SRU Justification]
When the dust has settled on the ESM archive Release file format[1], unattended-upgrades needs to be tweaked to match.
[1] https://github.com/CanonicalLtd/archive-auth-mirror/issues/43
Since the ESM archive contains packages updated by the Ubuntu Security team, we should ensure the behavior of unattended-upgrades applies the same default policy to both.
[Test case]
1. run 'sudo apt-get install ubuntu-advantage-tools unattended-upgrades ca-certificates'
2. run 'sudo ubuntu-advantage enable-esm <creds>' with your private creds to enable the ESM archive
3. run 'sudo apt-get update'
4. create a faked-up entry in /var/lib/apt/lists/esm.ubuntu.com_ubuntu_dists_precise_main_binary-amd64_Packages for the unattended-upgrades package with a higher version number
5. Run 'sudo sed -i -e"s/precise/$(lsb_release -c | cut -f2)/" /var/lib/apt/lists/esm.ubuntu.com_ubuntu_dists_precise_InRelease'
6. run 'sudo unattended-upgrades --debug --dry-run' and verify that no unattended-upgrades package is installed.
7. install unattended-upgrades from -proposed.
8. again create a faked-up entry in /var/lib/apt/lists/esm.ubuntu.com_ubuntu_dists_precise_main_binary-amd64_Packages for the unattended-upgrades package with a higher version number
9. Again run 'sudo sed -i -e"s/precise/$(lsb_release -c | cut -f2)/" /var/lib/apt/lists/esm.ubuntu.com_ubuntu_dists_precise_InRelease'
10. run 'sudo unattended-upgrades --debug --dry-run' and verify that it offers to install a new unattended-upgrades package.
[Regression potential]
Worst-case scenario is a bug that prevents future security updates from being applied correctly. This is not a concern for precise because there will be no further security updates /except/ those enabled by this SRU, but this SRU should also be included in all later stable releases. |
|
| 2017-05-12 00:24:07 |
Steve Langasek |
description |
[SRU Justification]
When the dust has settled on the ESM archive Release file format[1], unattended-upgrades needs to be tweaked to match.
[1] https://github.com/CanonicalLtd/archive-auth-mirror/issues/43
Since the ESM archive contains packages updated by the Ubuntu Security team, we should ensure the behavior of unattended-upgrades applies the same default policy to both.
[Test case]
1. run 'sudo apt-get install ubuntu-advantage-tools unattended-upgrades ca-certificates'
2. run 'sudo ubuntu-advantage enable-esm <creds>' with your private creds to enable the ESM archive
3. run 'sudo apt-get update'
4. create a faked-up entry in /var/lib/apt/lists/esm.ubuntu.com_ubuntu_dists_precise_main_binary-amd64_Packages for the unattended-upgrades package with a higher version number
5. Run 'sudo sed -i -e"s/precise/$(lsb_release -c | cut -f2)/" /var/lib/apt/lists/esm.ubuntu.com_ubuntu_dists_precise_InRelease'
6. run 'sudo unattended-upgrades --debug --dry-run' and verify that no unattended-upgrades package is installed.
7. install unattended-upgrades from -proposed.
8. again create a faked-up entry in /var/lib/apt/lists/esm.ubuntu.com_ubuntu_dists_precise_main_binary-amd64_Packages for the unattended-upgrades package with a higher version number
9. Again run 'sudo sed -i -e"s/precise/$(lsb_release -c | cut -f2)/" /var/lib/apt/lists/esm.ubuntu.com_ubuntu_dists_precise_InRelease'
10. run 'sudo unattended-upgrades --debug --dry-run' and verify that it offers to install a new unattended-upgrades package.
[Regression potential]
Worst-case scenario is a bug that prevents future security updates from being applied correctly. This is not a concern for precise because there will be no further security updates /except/ those enabled by this SRU, but this SRU should also be included in all later stable releases. |
[SRU Justification]
When the dust has settled on the ESM archive Release file format[1], unattended-upgrades needs to be tweaked to match.
[1] https://github.com/CanonicalLtd/archive-auth-mirror/issues/43
Since the ESM archive contains packages updated by the Ubuntu Security team, we should ensure the behavior of unattended-upgrades applies the same default policy to both.
[Test case]
1. run 'sudo apt-get install ubuntu-advantage-tools unattended-upgrades ca-certificates'
2. run 'sudo ubuntu-advantage enable-esm <creds>' with your private creds to enable the ESM archive
3. run 'sudo apt-get update'
4. create a faked-up entry in /var/lib/apt/lists/esm.ubuntu.com_ubuntu_dists_precise_main_binary-amd64_Packages for the unattended-upgrades package with a higher version number
5. run 'sudo sed -i -e"s/precise/$(lsb_release -c | cut -f2)/" /var/lib/apt/lists/esm.ubuntu.com_ubuntu_dists_precise_InRelease'
6. run 'sudo unattended-upgrades --debug --dry-run' and verify that no unattended-upgrades package is installed.
7. install unattended-upgrades from -proposed.
8. again create a faked-up entry in /var/lib/apt/lists/esm.ubuntu.com_ubuntu_dists_precise_main_binary-amd64_Packages for the unattended-upgrades package with a higher version number
9. again run 'sudo sed -i -e"s/precise/$(lsb_release -c | cut -f2)/" /var/lib/apt/lists/esm.ubuntu.com_ubuntu_dists_precise_InRelease'
10. run 'sudo unattended-upgrades --debug --dry-run' and verify that it offers to install a new unattended-upgrades package.
[Regression potential]
Worst-case scenario is a bug that prevents future security updates from being applied correctly. This is not a concern for precise because there will be no further security updates /except/ those enabled by this SRU, but this SRU should also be included in all later stable releases. |
|
| 2017-05-12 00:24:22 |
Steve Langasek |
tags |
verification-done-precise verification-needed |
verification-done-precise verification-done-xenial verification-needed |
|
| 2017-05-12 00:33:01 |
Steve Langasek |
tags |
verification-done-precise verification-done-xenial verification-needed |
verification-done-precise verification-done-xenial verification-failed-trusty verification-needed |
|
| 2017-05-12 00:33:31 |
Steve Langasek |
tags |
verification-done-precise verification-done-xenial verification-failed-trusty verification-needed |
verification-done-precise verification-done-xenial verification-needed |
|
| 2017-05-12 00:39:00 |
Steve Langasek |
tags |
verification-done-precise verification-done-xenial verification-needed |
verification-done-precise verification-done-trusty verification-done-xenial verification-needed |
|
| 2017-05-12 00:59:47 |
Steve Langasek |
tags |
verification-done-precise verification-done-trusty verification-done-xenial verification-needed |
verification-done-precise verification-done-trusty verification-done-xenial verification-done-yakkety verification-needed |
|
| 2017-05-12 01:06:13 |
Steve Langasek |
tags |
verification-done-precise verification-done-trusty verification-done-xenial verification-done-yakkety verification-needed |
verification-done-precise verification-done-trusty verification-done-xenial verification-done-yakkety verification-done-zesty verification-needed |
|
| 2017-05-12 01:09:58 |
Steve Langasek |
unattended-upgrades (Ubuntu): status |
Confirmed |
Fix Committed |
|
| 2017-05-12 11:37:09 |
Launchpad Janitor |
unattended-upgrades (Ubuntu): status |
Fix Committed |
Fix Released |
|
| 2017-05-16 20:16:19 |
Launchpad Janitor |
unattended-upgrades (Ubuntu Trusty): status |
Fix Committed |
Fix Released |
|
| 2017-05-18 18:06:15 |
Launchpad Janitor |
unattended-upgrades (Ubuntu Yakkety): status |
Fix Committed |
Fix Released |
|
| 2017-05-18 18:11:10 |
Launchpad Janitor |
unattended-upgrades (Ubuntu Zesty): status |
Fix Committed |
Fix Released |
|
| 2017-05-18 20:51:30 |
Launchpad Janitor |
unattended-upgrades (Ubuntu Xenial): status |
Fix Committed |
Fix Released |
|
