The sphinx tests now pass with the webkit2gtk 2.16.2 SRUs.
https://autopkgtest.ubuntu.com/packages/sphinx/zesty/amd64 https://autopkgtest.ubuntu.com/packages/sphinx/yakkety/amd64 https://autopkgtest.ubuntu.com/packages/sphinx/xenial/amd64
Apparently, xenial's webkit2gtk does not trigger sphinx autopktests though: https://people.canonical.com/~ubuntu-archive/proposed-migration/xenial/update_excuses.html#webkit2gtk
One issue is that some sphinx rdepends have failing autopkgtests, but this was likely an already existing issue. https://people.canonical.com/~ubuntu-archive/proposed-migration/zesty/update_excuses.html#sphinx https://people.canonical.com/~ubuntu-archive/proposed-migration/yakkety/update_excuses.html#sphinx
I recommend that the sphinx SRUs be accepted; otherwise all of the sphinx autopkgtests for yakkety and zesty will fail once webkit2gtk enters -updates.
The sphinx tests now pass with the webkit2gtk 2.16.2 SRUs.
https:/ /autopkgtest. ubuntu. com/packages/ sphinx/ zesty/amd64 /autopkgtest. ubuntu. com/packages/ sphinx/ yakkety/ amd64 /autopkgtest. ubuntu. com/packages/ sphinx/ xenial/ amd64
https:/
https:/
Apparently, xenial's webkit2gtk does not trigger sphinx autopktests though: /people. canonical. com/~ubuntu- archive/ proposed- migration/ xenial/ update_ excuses. html#webkit2gtk
https:/
One issue is that some sphinx rdepends have failing autopkgtests, but this was likely an already existing issue. /people. canonical. com/~ubuntu- archive/ proposed- migration/ zesty/update_ excuses. html#sphinx /people. canonical. com/~ubuntu- archive/ proposed- migration/ yakkety/ update_ excuses. html#sphinx
https:/
https:/
I recommend that the sphinx SRUs be accepted; otherwise all of the sphinx autopkgtests for yakkety and zesty will fail once webkit2gtk enters -updates.