Thanks for pointing out the correct mailing list to use for this... I wasn't sure which one was appropriate and wanted to be as low-key as possible about this issue since I wasn't paying much attention about what was updated.
The virtual environment in question is my Ubuntu 12.04 workstation... not a local LAVA server environment. So there is no lava deployment tool in this environment AFAIK. The lava tools were installed from binary packages found in a combination of the official Ubuntu repositories plus "deb-amd64 http://ppa.launchpad.net/linaro-maintainers/toolchain/ubuntu precise main" and "deb-amd64 http://ppa.launchpad.net/linaro-maintainers/tools/ubuntuprecise main".
I normally assume that any updates which come from the 12.04 distribution-compatible repositories should be a safe and reliable upgrade, and I try to stick with binaries from the official repositories rather than locally compiled packages in order to minimize packaging compatibility and upgrade issues. Why is a package for Ubuntu 12.04 requiring pyxdg ==0.25 when the latest pyxdg version available in the 12.04 repositories is 0.19-3ubuntu2 (which was already installed)? And why didn't this requirement get listed as a dependency in the package, flagged as an unmet dependency and prevent the package upgrade from occurring?
And most importantly now that this binary update has occurred despite the unmet dependency, how do I cleanly get a working set of lava tools for accessing the production servers from command line scripts again? Is there a way to back out the update and revert to the earlier version? The new lava-scheduler-tool package version is 0.6-0ubuntu1~linaro1, but I don't know what the previous working version was nor if it is still accessible for installation.
Any help will be appreciated. Fortunately I'll be on vacation next week so I have some time to fix this before it becomes a serious handicap to my work.
Gary Robertson
On Sun, Nov 24, 2013 at 5:28 AM, Neil Williams neil.williams@linaro.orgwrote:
Please use linaro-validation for queries like this. linaro-validation@lists.linaro.org (Please do not reply directly to me or to this private team list)
The error message describes what is wrong - pyxdg has been added as a requirement but is not in the virtual environment.
lava-deployment-tool upgrade or re-running the buildout command is normally sufficient for this.
On 24 November 2013 00:13, Gary Robertson gary.robertson@linaro.org wrote:
Hello,
Today there was an update to the lava tools on my Ubuntu 12.04 x86_64 workstation. I have the PPA repository enabled to try and stay up to
date
on all my Linaro tools.
Some time after the update, I tried to submit a job from my local
machine
thusly:
lava scheduler submit-job
http://gary-robertson@validation.linaro.org/RPC2/
workspace-le/my_test.json
The json file was:
{ "actions": [ { "command": "deploy_linaro_image", "metadata": { "distribution": "openembedded", "hwpack.build": "13", "hwpack.type": "arndale" }, "parameters": { "hwpack": "
https://people.linaro.org/~gary.robertson/hwpack_linaro-arndale_20131123-231... ",
"rootfs":
"
http://snapshots.linaro.org/openembedded/images/lng-armv7a-gcc-4.8/160/linar... "
} }, { "command": "lava_test_shell", "parameters": { "testdef_repos": [ { "git-repo":
"git://git.linaro.org/qa/test-definitions.git", "testdef": "openembedded/hackbench.yaml" } ], "timeout": 18000 } }, { "command": "lava_test_shell", "parameters": { "testdef_repos": [ { "git-repo": "git://git.linaro.org/qa/test-definitions.git", "testdef": "openembedded/ltp.yaml" } ], "timeout": 7200 } }, { "command": "lava_test_shell", "parameters": { "testdef_repos": [ { "git-repo": "git://git.linaro.org/qa/test-definitions.git", "testdef": "openembedded/ltp-realtime.yaml" } ], "timeout": 18000 } }, { "command": "lava_test_shell", "parameters": { "testdef_repos": [ { "git-repo": "git://git.linaro.org/qa/test-definitions.git", "testdef": "openembedded/kvm.yaml" } ], "timeout": 18000 } }, { "command": "lava_test_shell", "parameters": { "testdef_repos": [ { "git-repo": "git://git.linaro.org/qa/test-definitions.git", "testdef": "openembedded/lmbench.yaml" } ], "timeout": 18000 } }, { "command": "submit_results", "parameters": { "server": "http://validation.linaro.org/RPC2/", "stream": "/anonymous/gary-robertson/" } } ], "device_type": "arndale", "job_name": "gary.robertson_linux-lng-preempt-rt_le_13", "timeout": 172800 }
As of yesterday I was able to submit identical jobs for different hwpacks successfully, but this evening after the update had occurred it failed
with
the following error:
Traceback (most recent call last): File "/usr/bin/lava", line 5, in <module> from pkg_resources import load_entry_point File "/usr/lib/python2.7/dist-packages/pkg_resources.py", line 2711, in
<module> parse_requirements(__requires__), Environment() File "/usr/lib/python2.7/dist-packages/pkg_resources.py", line 584, in resolve raise DistributionNotFound(req) pkg_resources.DistributionNotFound: pyxdg==0.25
I was able to submit the above json file via the web interface and so was able to schedule the test successfully that way... however I would very
much
like to restore the ability to do this from a local command line, as my kernel tree maintenance duties require frequent LAVA tests for pending patches to the LNG kernel.
I'm not sure if this is a bug or some kind of configuration error on my
part
due to mixed repository specifications or such - so I'm reporting it
here to
let the gurus get a look at it.
Any help or insight would be appreciated.
Gary Robertson
--
Neil Williams
neil.williams@linaro.org http://www.linux.codehelp.co.uk/
On Sun, Nov 24, 2013 at 05:55:59PM -0600, Gary Robertson wrote:
Thanks for pointing out the correct mailing list to use for this... I wasn't sure which one was appropriate and wanted to be as low-key as possible about this issue since I wasn't paying much attention about what was updated.
The virtual environment in question is my Ubuntu 12.04 workstation... not a local LAVA server environment. So there is no lava deployment tool in this environment AFAIK. The lava tools were installed from binary packages found in a combination of the official Ubuntu repositories plus "deb-amd64 http://ppa.launchpad.net/linaro-maintainers/toolchain/ubuntu precise main" and "deb-amd64 http://ppa.launchpad.net/linaro-maintainers/tools/ubuntuprecise main".
I normally assume that any updates which come from the 12.04 distribution-compatible repositories should be a safe and reliable upgrade, and I try to stick with binaries from the official repositories rather than locally compiled packages in order to minimize packaging compatibility and upgrade issues. Why is a package for Ubuntu 12.04 requiring pyxdg ==0.25 when the latest pyxdg version available in the 12.04 repositories is 0.19-3ubuntu2 (which was already installed)? And why didn't this requirement get listed as a dependency in the package, flagged as an unmet dependency and prevent the package upgrade from occurring?
And most importantly now that this binary update has occurred despite the unmet dependency, how do I cleanly get a working set of lava tools for accessing the production servers from command line scripts again? Is there a way to back out the update and revert to the earlier version? The new lava-scheduler-tool package version is 0.6-0ubuntu1~linaro1, but I don't know what the previous working version was nor if it is still accessible for installation.
Any help will be appreciated. Fortunately I'll be on vacation next week so I have some time to fix this before it becomes a serious handicap to my work.
That was a mistake and will be fixed ASAP, bear with me. Sorry for the inconvenience.
On Sun, Nov 24, 2013 at 05:55:59PM -0600, Gary Robertson wrote:
Thanks for pointing out the correct mailing list to use for this... I wasn't sure which one was appropriate and wanted to be as low-key as possible about this issue since I wasn't paying much attention about what was updated.
The virtual environment in question is my Ubuntu 12.04 workstation... not a local LAVA server environment. So there is no lava deployment tool in this environment AFAIK. The lava tools were installed from binary packages found in a combination of the official Ubuntu repositories plus "deb-amd64 http://ppa.launchpad.net/linaro-maintainers/toolchain/ubuntu precise main" and "deb-amd64 http://ppa.launchpad.net/linaro-maintainers/tools/ubuntuprecise main".
I normally assume that any updates which come from the 12.04 distribution-compatible repositories should be a safe and reliable upgrade, and I try to stick with binaries from the official repositories rather than locally compiled packages in order to minimize packaging compatibility and upgrade issues. Why is a package for Ubuntu 12.04 requiring pyxdg ==0.25 when the latest pyxdg version available in the 12.04 repositories is 0.19-3ubuntu2 (which was already installed)? And why didn't this requirement get listed as a dependency in the package, flagged as an unmet dependency and prevent the package upgrade from occurring?
lava-tool used a feature of pyxdg that was not available at pyxdg 0.19. It was fixed to also work with pyxdg version 0.19 so you should be good now.
The fixed packages has been uploaded to the Linaro Tools PPA. Just upgrading should fix it for you.
Just back in from vacation as of 02 DEC.
Thanks for your prompt resolution of this issue. The latest lava-tool package is once again working on my Ubuntu 12.04 installation and my scripts are once more operational.
Gary Robertson
On Mon, Nov 25, 2013 at 6:39 PM, Antonio Terceiro < antonio.terceiro@linaro.org> wrote:
On Sun, Nov 24, 2013 at 05:55:59PM -0600, Gary Robertson wrote:
Thanks for pointing out the correct mailing list to use for this... I wasn't sure which one was appropriate and wanted to be as low-key as possible about this issue since I wasn't paying much attention about what was updated.
The virtual environment in question is my Ubuntu 12.04 workstation...
not a
local LAVA server environment. So there is no lava deployment tool in
this
environment AFAIK. The lava tools were installed from binary packages found in a combination of the official Ubuntu repositories plus
"deb-amd64
http://ppa.launchpad.net/linaro-maintainers/toolchain/ubuntu precise
main"
and "deb-amd64
http://ppa.launchpad.net/linaro-maintainers/tools/ubuntuprecise
main".
I normally assume that any updates which come from the 12.04 distribution-compatible repositories should be a safe and reliable
upgrade,
and I try to stick with binaries from the official repositories rather
than
locally compiled packages in order to minimize packaging compatibility
and
upgrade issues. Why is a package for Ubuntu 12.04 requiring pyxdg ==0.25 when the latest pyxdg version available in the 12.04 repositories is 0.19-3ubuntu2 (which was already installed)? And why didn't this requirement get listed as a dependency in the package, flagged as an
unmet
dependency and prevent the package upgrade from occurring?
lava-tool used a feature of pyxdg that was not available at pyxdg 0.19. It was fixed to also work with pyxdg version 0.19 so you should be good now.
The fixed packages has been uploaded to the Linaro Tools PPA. Just upgrading should fix it for you.
-- Antonio Terceiro Software Engineer - Linaro http://www.linaro.org
linaro-validation@lists.linaro.org