Merge lp://qastaging/~ubuntu-sdk-team/ubuntu-ui-toolkit/pilotTracing into lp://qastaging/ubuntu-ui-toolkit/staging

FAILED: Continuous integration, rev:1305
http://jenkins.qa.ubuntu.com/job/ubuntu-sdk-team-ubuntu-ui-toolkit-staging-ci/1170/
Executed test runs:
    UNSTABLE: http://jenkins.qa.ubuntu.com/job/generic-deb-autopilot-utopic-touch/6206
    SUCCESS: http://jenkins.qa.ubuntu.com/job/ubuntu-sdk-team-ubuntu-ui-toolkit-staging-utopic-amd64-ci/1003
    SUCCESS: http://jenkins.qa.ubuntu.com/job/ubuntu-sdk-team-ubuntu-ui-toolkit-staging-utopic-armhf-ci/1002
        deb: http://jenkins.qa.ubuntu.com/job/ubuntu-sdk-team-ubuntu-ui-toolkit-staging-utopic-armhf-ci/1002/artifact/work/output/*zip*/output.zip
    SUCCESS: http://jenkins.qa.ubuntu.com/job/ubuntu-sdk-team-ubuntu-ui-toolkit-staging-utopic-i386-ci/1002
    UNSTABLE: http://jenkins.qa.ubuntu.com/job/generic-deb-autopilot-runner-mako/5827
    SUCCESS: http://jenkins.qa.ubuntu.com/job/generic-mediumtests-builder-utopic-armhf/7458
        deb: http://jenkins.qa.ubuntu.com/job/generic-mediumtests-builder-utopic-armhf/7458/artifact/work/output/*zip*/output.zip
    SUCCESS: http://s-jenkins.ubuntu-ci:8080/job/touch-flash-device/15053

Click here to trigger a rebuild:
http://s-jenkins.ubuntu-ci:8080/job/ubuntu-sdk-team-ubuntu-ui-toolkit-staging-ci/1170/rebuild

FAILED: Continuous integration, rev:1306
http://jenkins.qa.ubuntu.com/job/ubuntu-sdk-team-ubuntu-ui-toolkit-staging-ci/1174/
Executed test runs:
    FAILURE: http://jenkins.qa.ubuntu.com/job/generic-deb-autopilot-utopic-touch/6218/console
    SUCCESS: http://jenkins.qa.ubuntu.com/job/ubuntu-sdk-team-ubuntu-ui-toolkit-staging-utopic-amd64-ci/1007
    SUCCESS: http://jenkins.qa.ubuntu.com/job/ubuntu-sdk-team-ubuntu-ui-toolkit-staging-utopic-armhf-ci/1006
        deb: http://jenkins.qa.ubuntu.com/job/ubuntu-sdk-team-ubuntu-ui-toolkit-staging-utopic-armhf-ci/1006/artifact/work/output/*zip*/output.zip
    SUCCESS: http://jenkins.qa.ubuntu.com/job/ubuntu-sdk-team-ubuntu-ui-toolkit-staging-utopic-i386-ci/1006
    FAILURE: http://jenkins.qa.ubuntu.com/job/generic-deb-autopilot-runner-mako/5839/console
    SUCCESS: http://jenkins.qa.ubuntu.com/job/generic-mediumtests-builder-utopic-armhf/7470
        deb: http://jenkins.qa.ubuntu.com/job/generic-mediumtests-builder-utopic-armhf/7470/artifact/work/output/*zip*/output.zip
    SUCCESS: http://s-jenkins.ubuntu-ci:8080/job/touch-flash-device/15071

Click here to trigger a rebuild:
http://s-jenkins.ubuntu-ci:8080/job/ubuntu-sdk-team-ubuntu-ui-toolkit-staging-ci/1174/rebuild

<elopio> kalikiana: for now, the toolkit deb is python 2 and 3.
<elopio> so
<elopio> maybe you should also add python-autopilot-trace
<kalikiana> elopio: we run it with python3
<kalikiana> afair we don't want to install everything twice
<elopio> kalikiana: yes, but there are aa couple of projects that still use py2 and it would be useful for them.
<elopio> we are about to remove the py2 everywhere
<kalikiana> hmmmm
<elopio> we are about to remove the py2 everywhere
<elopio> so I'm not sure if it might be worth it.
<zbenjamin> mhall119: pong
<kalikiana> elopio: idea, I can try the | magic
<elopio> kalikiana: not sure how that would help
<kalikiana> elopio: we do that for qt where the packages in the latest release were renamed
<kalikiana> qml-blabla
<elopio> kalikiana: but how would you tell when you need the 2 or the 3 version?
<kalikiana> so it's like qml-module-dragon | qtdeclarative-dragon-plugin
<kalikiana> hmmmm
<kalikiana> I guess it's not quite the same as you can have both py2 and 3
<kalikiana> unlike old and new qt
<elopio> kalikiana: also installing the py2 version won't hurt a lot, as we are already installing the 2 versions for a bunch of projects. But also not installing it wouldn't be bad, as the py2 projects will be updated and anyway they have always run without trace.
<elopio> kalikiana: so do whatever feels good for you. The change looks correct.
<kalikiana> elopio: I'm pushing a rev adding the py2
<kalikiana> should be there now
<elopio> kalikiana: ok.

FAILED: Continuous integration, rev:1307
http://jenkins.qa.ubuntu.com/job/ubuntu-sdk-team-ubuntu-ui-toolkit-staging-ci/1181/
Executed test runs:
    UNSTABLE: http://jenkins.qa.ubuntu.com/job/generic-deb-autopilot-utopic-touch/6323
    SUCCESS: http://jenkins.qa.ubuntu.com/job/ubuntu-sdk-team-ubuntu-ui-toolkit-staging-utopic-amd64-ci/1014
    SUCCESS: http://jenkins.qa.ubuntu.com/job/ubuntu-sdk-team-ubuntu-ui-toolkit-staging-utopic-armhf-ci/1013
        deb: http://jenkins.qa.ubuntu.com/job/ubuntu-sdk-team-ubuntu-ui-toolkit-staging-utopic-armhf-ci/1013/artifact/work/output/*zip*/output.zip
    SUCCESS: http://jenkins.qa.ubuntu.com/job/ubuntu-sdk-team-ubuntu-ui-toolkit-staging-utopic-i386-ci/1013
    UNSTABLE: http://jenkins.qa.ubuntu.com/job/generic-deb-autopilot-runner-mako/5928
    SUCCESS: http://jenkins.qa.ubuntu.com/job/generic-mediumtests-builder-utopic-armhf/7575
        deb: http://jenkins.qa.ubuntu.com/job/generic-mediumtests-builder-utopic-armhf/7575/artifact/work/output/*zip*/output.zip
    SUCCESS: http://s-jenkins.ubuntu-ci:8080/job/touch-flash-device/15229

Click here to trigger a rebuild:
http://s-jenkins.ubuntu-ci:8080/job/ubuntu-sdk-team-ubuntu-ui-toolkit-staging-ci/1181/rebuild

according to the commit message, python3-autopilot should depend on python3-autopilot-trace, not uitk depend on the -trace package.

> according to the commit message, python3-autopilot should depend on python3
> -autopilot-trace, not uitk depend on the -trace package.

No. The "autopilot" package in this case is ubuntu-ui-toolkit-autopilot. And that's what the commit actually does, if you look at the change.

ok.

So the python3-autopilot and python-autopilot dependencies can be removed, since the -trace packages depend on it?

< kalikiana> timp: hmm. I see what you mean. not sure if that might be a bit confusing, though

right.