Hello,
Until then I've installed extra test packages from embedded test scripts. Using the latest V2 version, I'm trying to manage this in my test jobs.
e.g.:
install: deps: - python-pytest - python-lxml - packagegroup-core-buildessential - phoronix-test-suite
At execution time, I get a Error: OPKG package manager not found in the path.
Does this mean that OPKG is the only installer supported? Or is this the default one meaning that I can select DPKG or aptitude instead?
Best regards,
Denis
On 15 May 2017 at 15:17, Denis HUMEAU denis.humeau@st.com wrote:
Hello, Until then I’ve installed extra test packages from embedded test scripts.
Using the latest V2 version, I’m trying to manage this in my test jobs.
The availability of a package manager is determined by the test files submitted as part of the test job definition, so LAVA picks up settings there to determine which package manager should be used.
At execution time, I get a Error: OPKG package manager not found in the path.
In this case, the test job will have specified:
os: oe
OpenEmbedded does not include OPKG support in every build and if you want to be able to install packages using OE, you will need to ensure that opkg is built into all OE images to be used with this test definition.
Does this mean that OPKG is the only installer supported? Or is this the default one meaning that I can select DPKG or aptitude instead?
opkg is the only package manager available if OE has been selected in the test job.
apt is the only package manager available for the test definition install: deps: if os: debian is specified.
See https://staging.validation.linaro.org/static/docs/v2/writing-tests.html#test...
If the objective is to have one test definition that works for many deployments, write a script which can check what is installed and use whatever it finds - or ensure that the images as built already contain all the relevant dependencies.
Hello Neil,
Following your advice I've added opkg to my rootfs generated with openembedded. I've prepared ipk packages and shared them on an apache server just for test purpose.
Running this configuration, I get the following error message:
###################################################### I: unsupported distro, cannot add sources: - http://lmewx80k/ipk/all ###################################################### ###################################################### I: unsupported distro, cannot add sources: - http://lmewx80k/ipk/cortexa9hf-vfp-neon ###################################################### ###################################################### I: unsupported distro, cannot add sources: - http://lmewx80k/ipk/sti-lts ###################################################### /usr/bin/opkg
Do you have any clue on the origin of this error message?
Best regards,
Denis
-----Original Message----- From: Neil Williams [mailto:neil.williams@linaro.org] Sent: lundi 15 mai 2017 16:31 To: Denis HUMEAU denis.humeau@st.com Cc: lava-users@lists.linaro.org Subject: Re: [Lava-users] Package installation
On 15 May 2017 at 15:17, Denis HUMEAU denis.humeau@st.com wrote:
Hello, Until then I’ve installed extra test packages from embedded test scripts.
Using the latest V2 version, I’m trying to manage this in my test jobs.
The availability of a package manager is determined by the test files submitted as part of the test job definition, so LAVA picks up settings there to determine which package manager should be used.
At execution time, I get a Error: OPKG package manager not found in the path.
In this case, the test job will have specified:
os: oe
OpenEmbedded does not include OPKG support in every build and if you want to be able to install packages using OE, you will need to ensure that opkg is built into all OE images to be used with this test definition.
Does this mean that OPKG is the only installer supported? Or is this the default one meaning that I can select DPKG or aptitude instead?
opkg is the only package manager available if OE has been selected in the test job.
apt is the only package manager available for the test definition install: deps: if os: debian is specified.
See https://staging.validation.linaro.org/static/docs/v2/writing-tests.html#test...
If the objective is to have one test definition that works for many deployments, write a script which can check what is installed and use whatever it finds - or ensure that the images as built already contain all the relevant dependencies.
-
Denis HUMEAU -
Neil Williams