I did prepare in Bileto: https://launchpad.net/~ci-train-ppa-service/+archive/ubuntu/2585 https://launchpad.net/~ci-train-ppa-service/+archive/ubuntu/2586
Associated autopkgtests ran fine: https://bileto.ubuntu.com/excuses/2585/xenial.html
Also the openssh tests of the QA Test suite (https://git.launchpad.net/qa-regression-testing) ran fine in Xenial/Yakkety VMs.
And finally the test for the explicit issue we are fixing here was confirmed to be fixed on the Bileto PPAs.
Adding SRU Template now, but unfortunately (no core dev) I can't sponsor them myself, but the debdiff to do so can be picked from the tested Bileto ppas at: https://objectstorage.prodstack4-5.canonical.com/v1/AUTH_39a8dbb93caf4ec889f8a1b7f69885db/bileto-2585/2017-03-15_13:33:40/xenial_openssh_content.diff https://objectstorage.prodstack4-5.canonical.com/v1/AUTH_39a8dbb93caf4ec889f8a1b7f69885db/bileto-2586/2017-03-15_13:33:46/yakkety_openssh_content.diff
Eventually for Sponsorsing the easiest might be via bileto itself, IIRC one with permissions could also just hit "publish" on the two tickets - that might be the easiest way: https://bileto.ubuntu.com/#/ticket/2585 https://bileto.ubuntu.com/#/ticket/2586
The autopkgtest showed some issues I want to look into first, therefore (except if you know all these) do not sponsor yet. That also gives us time to have the fixed sync to appear in zesty.
I did prepare in Bileto: /launchpad. net/~ci- train-ppa- service/ +archive/ ubuntu/ 2585 /launchpad. net/~ci- train-ppa- service/ +archive/ ubuntu/ 2586
https:/
https:/
Associated autopkgtests ran fine: https:/ /bileto. ubuntu. com/excuses/ 2585/xenial. html
Also the openssh tests of the QA Test suite (https:/ /git.launchpad. net/qa- regression- testing) ran fine in Xenial/Yakkety VMs.
And finally the test for the explicit issue we are fixing here was confirmed to be fixed on the Bileto PPAs.
Adding SRU Template now, but unfortunately (no core dev) I can't sponsor them myself, but the debdiff to do so can be picked from the tested Bileto ppas at: /objectstorage. prodstack4- 5.canonical. com/v1/ AUTH_39a8dbb93c af4ec889f8a1b7f 69885db/ bileto- 2585/2017- 03-15_13: 33:40/xenial_ openssh_ content. diff /objectstorage. prodstack4- 5.canonical. com/v1/ AUTH_39a8dbb93c af4ec889f8a1b7f 69885db/ bileto- 2586/2017- 03-15_13: 33:46/yakkety_ openssh_ content. diff
https:/
https:/
Eventually for Sponsorsing the easiest might be via bileto itself, IIRC one with permissions could also just hit "publish" on the two tickets - that might be the easiest way: /bileto. ubuntu. com/#/ticket/ 2585 /bileto. ubuntu. com/#/ticket/ 2586
https:/
https:/
The autopkgtest showed some issues I want to look into first, therefore (except if you know all these) do not sponsor yet. That also gives us time to have the fixed sync to appear in zesty.