Comment 3 for bug 1692092

Revision history for this message
Brian Murray (brian-murray) wrote :

I updated the meta-release-proposed file on the server to point at the dist-upgrader in zesty-proposed and then ran through the test from the test case. I had to modify the cached meta-release-proposed file (since the we are verifying an SRU in -proposed) on my system to verify the SRU but after that the test passed.

bdmurray@clean-xenial-amd64:~$ do-release-upgrade -p
Checking for a new Ubuntu release
Get:1 Upgrade tool signature [836 B]
Get:2 Upgrade tool [1,265 kB]
Fetched 1,266 kB in 0s (0 B/s)
authenticate 'yakkety.tar.gz' against 'yakkety.tar.gz.gpg'
extracting 'yakkety.tar.gz'

[screen is terminating]
bdmurray@clean-xenial-amd64:~$ vi ~/.cache/update-manager-core/meta-release-proposed
bdmurray@clean-xenial-amd64:~$ do-release-upgrade -p
Checking for a new Ubuntu release
Get:1 Upgrade tool signature [836 B]
Get:2 Upgrade tool [1,268 kB]
Fetched 1,269 kB in 0s (0 B/s)
authenticate 'zesty.tar.gz' against 'zesty.tar.gz.gpg'
extracting 'zesty.tar.gz'

Additionally, when using the zesty tarball I did not receive an error about the upgrade path being unsupported.