A quick test result: looks about like Alan's surfaceflinger but this time on Mir.
Using:
apt-add-repository ppa:ci-train-ppa-service/landing-006
apt-add-repository ppa:canonical-qt5-edgers/qt5-beta1 # no typo, beta1 has only the packages that are missing from landing-006
added with
apt-add-repository ppa:canonical-qt5-edgers/qt5-beta-proper
Note: if you're using qt5-beta2 PPA instead of the two mentioned above, the results should be the same. Functionally the "final" landing PPA added with qt5-beta1 is almost identical to qt5-beta2. But if you reflash your device you may want to use landing-006 + qt5-beta1 instead (and add/remove qt5-beta-proper as needed).
A quick test result: looks about like Alan's surfaceflinger but this time on Mir.
Using: train-ppa- service/ landing- 006 qt5-edgers/ qt5-beta1 # no typo, beta1 has only the packages that are missing from landing-006
apt-add-repository ppa:ci-
apt-add-repository ppa:canonical-
added with qt5-edgers/ qt5-beta- proper
apt-add-repository ppa:canonical-
... which has qtubuntu DPR branch bzr181 https:/ /launchpad. net/~canonical- qt5-edgers/ +archive/ qt5-beta- proper/ +sourcepub/ 3958676/ +listing- archive- extra and UITK DPR branch bzr761 https:/ /launchpad. net/~canonical- qt5-edgers/ +archive/ qt5-beta- proper/ +sourcepub/ 3958707/ +listing- archive- extra
So more fixes needed.
Note: if you're using qt5-beta2 PPA instead of the two mentioned above, the results should be the same. Functionally the "final" landing PPA added with qt5-beta1 is almost identical to qt5-beta2. But if you reflash your device you may want to use landing-006 + qt5-beta1 instead (and add/remove qt5-beta-proper as needed).