I will further increase this SRU bug with information that is lacking on from the original bug proposal:
[Impact]
During an upgrade from trusty to xenial, users will be prompted to make a decision regarding the diff on unattended-upgrades. This is not a good user experience, specially because the user can make an uninformed decision of keeping the old config file, which will make unattended-upgrades to not work as we expect.
[Test case]
To reproduce the isse, you can:
1. Launch a trusty vm
2. Perform a do-release-upgrade and observe that you will be prompted with the 50unattende-upgrades change
To verify that the error is fixed:
1. Launch a trusty vm
2. Import this ppa into the system: https://launchpad.net/~lamoura/+archive/ubuntu/unattended-upgrades-ppa
3. Configure do-release-upgrade to allow using third parties during upgrade
4. Run a do-release-upgrade
5. Verify the prompt is no longer there and that we end up with the expected 50unattended-upgrades
config file
[Where problems could occur]
The changes is this package should only be surface during an upgrade operation. Because we are now delivering a new file to the system and configuring postinst to use it. Because of that, we believe this is the only scenario that could be affect in case of a regression is discovered in the package.
-------------------
Finally, if there is any additional information that I need to add to this SRU, just let me know and I will provide it
I will further increase this SRU bug with information that is lacking on from the original bug proposal:
[Impact] upgrades. This is not a good user experience, specially because the user can make an uninformed decision of keeping the old config file, which will make unattended-upgrades to not work as we expect.
During an upgrade from trusty to xenial, users will be prompted to make a decision regarding the diff on unattended-
[Test case]
To reproduce the isse, you can:
1. Launch a trusty vm upgrades change
2. Perform a do-release-upgrade and observe that you will be prompted with the 50unattende-
To verify that the error is fixed:
1. Launch a trusty vm /launchpad. net/~lamoura/ +archive/ ubuntu/ unattended- upgrades- ppa upgrades
2. Import this ppa into the system:
https:/
3. Configure do-release-upgrade to allow using third parties during upgrade
4. Run a do-release-upgrade
5. Verify the prompt is no longer there and that we end up with the expected 50unattended-
config file
[Where problems could occur]
The changes is this package should only be surface during an upgrade operation. Because we are now delivering a new file to the system and configuring postinst to use it. Because of that, we believe this is the only scenario that could be affect in case of a regression is discovered in the package.
-------------------
Finally, if there is any additional information that I need to add to this SRU, just let me know and I will provide it