The deployment of LAVA using Ubuntu packages is deprecated in favor of the dedicated LAVA deployment tool [1]. LAVA installation is tested and supported on Ubuntu host from version 10.10 to 11.10 (Maverick to Oneiric) [2].
From 11.12 cycle, the following conditions will be applied:
* Linaro Validation PPA [3] won't be updated with latest LAVA releases. * Bugs affecting packages won't be fixed.
We plan to provide LAVA deployment tool from Linaro Validation PPA.
[1] http://launchpad.net/lava-deployment-tool [2] Ubuntu 10.04 LTS (Lucid) isn't supported due to a bug with upstart [3] http://launchpad.net/~linaro-validation/+archive/ppa
On Tue, Dec 06, 2011 at 10:16:22AM +0200, Fathi Boudra wrote:
The deployment of LAVA using Ubuntu packages is deprecated in favor of the dedicated LAVA deployment tool [1]. LAVA installation is tested and supported on Ubuntu host from version 10.10 to 11.10 (Maverick to Oneiric) [2].
From 11.12 cycle, the following conditions will be applied:
- Linaro Validation PPA [3] won't be updated with latest LAVA releases.
- Bugs affecting packages won't be fixed.
We plan to provide LAVA deployment tool from Linaro Validation PPA.
[1] http://launchpad.net/lava-deployment-tool [2] Ubuntu 10.04 LTS (Lucid) isn't supported due to a bug with upstart [3] http://launchpad.net/~linaro-validation/+archive/ppa
Does this affect all LAVA packages (eg lava-test, lava-dashboard-tool), or just the ones pertaining to the server?
Thanks, Alexandaros
On Tue, Dec 6, 2011 at 9:46 AM, Alexandros Frantzis < alexandros.frantzis@linaro.org> wrote:
On Tue, Dec 06, 2011 at 10:16:22AM +0200, Fathi Boudra wrote:
The deployment of LAVA using Ubuntu packages is deprecated in favor of
the
dedicated LAVA deployment tool [1]. LAVA installation is tested and
supported
on Ubuntu host from version 10.10 to 11.10 (Maverick to Oneiric) [2].
From 11.12 cycle, the following conditions will be applied:
- Linaro Validation PPA [3] won't be updated with latest LAVA releases.
- Bugs affecting packages won't be fixed.
We plan to provide LAVA deployment tool from Linaro Validation PPA.
[1] http://launchpad.net/lava-deployment-tool [2] Ubuntu 10.04 LTS (Lucid) isn't supported due to a bug with upstart [3] http://launchpad.net/~linaro-validation/+archive/ppahttp://launchpad.net/%7Elinaro-validation/+archive/ppa
Does this affect all LAVA packages (eg lava-test, lava-dashboard-tool), or just the ones pertaining to the server?
I would hope that client side tools that have reached a certain degree of maturity (read: you don't need to SRU stuff to ubuntu released version regularly due to changes on server side) would be still be made available in packaging form.
This mostly affects the server side components, yes. I'm open to the idea of continuing packages for the client-side tools, if it would be useful to others.
Thanks, Paul Larson
On Tue, Dec 6, 2011 at 5:12 AM, Alexander Sack asac@linaro.org wrote:
On Tue, Dec 6, 2011 at 9:46 AM, Alexandros Frantzis < alexandros.frantzis@linaro.org> wrote:
On Tue, Dec 06, 2011 at 10:16:22AM +0200, Fathi Boudra wrote:
The deployment of LAVA using Ubuntu packages is deprecated in favor of
the
dedicated LAVA deployment tool [1]. LAVA installation is tested and
supported
on Ubuntu host from version 10.10 to 11.10 (Maverick to Oneiric) [2].
From 11.12 cycle, the following conditions will be applied:
- Linaro Validation PPA [3] won't be updated with latest LAVA releases.
- Bugs affecting packages won't be fixed.
We plan to provide LAVA deployment tool from Linaro Validation PPA.
[1] http://launchpad.net/lava-deployment-tool [2] Ubuntu 10.04 LTS (Lucid) isn't supported due to a bug with upstart [3] http://launchpad.net/~linaro-validation/+archive/ppahttp://launchpad.net/%7Elinaro-validation/+archive/ppa
Does this affect all LAVA packages (eg lava-test, lava-dashboard-tool), or just the ones pertaining to the server?
I would hope that client side tools that have reached a certain degree of maturity (read: you don't need to SRU stuff to ubuntu released version regularly due to changes on server side) would be still be made available in packaging form.
-- Alexander Sack Technical Director, Linaro Platform Teams http://www.linaro.org | Open source software for ARM SoCs http://twitter.com/#%21/linaroorg - http://www.linaro.org/linaro-blog
linaro-dev mailing list linaro-dev@lists.linaro.org http://lists.linaro.org/mailman/listinfo/linaro-dev
Hi,
I was looking at the code for this...
Is this something that should be on the Linaro GIT server?
git://github.com/zyga/pip.git
It's called as git clone git://github.com/zyga/pip.git -b develop $LAVA_PREFIX/$LAVA_INSTANCE/src/pip
On Tue, Dec 6, 2011 at 7:24 AM, Paul Larson paul.larson@linaro.org wrote:
This mostly affects the server side components, yes. I'm open to the idea of continuing packages for the client-side tools, if it would be useful to others.
Thanks, Paul Larson
On Tue, Dec 6, 2011 at 5:12 AM, Alexander Sack asac@linaro.org wrote:
On Tue, Dec 6, 2011 at 9:46 AM, Alexandros Frantzis alexandros.frantzis@linaro.org wrote:
On Tue, Dec 06, 2011 at 10:16:22AM +0200, Fathi Boudra wrote:
The deployment of LAVA using Ubuntu packages is deprecated in favor of the dedicated LAVA deployment tool [1]. LAVA installation is tested and supported on Ubuntu host from version 10.10 to 11.10 (Maverick to Oneiric) [2].
From 11.12 cycle, the following conditions will be applied: * Linaro Validation PPA [3] won't be updated with latest LAVA releases. * Bugs affecting packages won't be fixed.
We plan to provide LAVA deployment tool from Linaro Validation PPA.
[1] http://launchpad.net/lava-deployment-tool [2] Ubuntu 10.04 LTS (Lucid) isn't supported due to a bug with upstart [3] http://launchpad.net/~linaro-validation/+archive/ppa
Does this affect all LAVA packages (eg lava-test, lava-dashboard-tool), or just the ones pertaining to the server?
I would hope that client side tools that have reached a certain degree of maturity (read: you don't need to SRU stuff to ubuntu released version regularly due to changes on server side) would be still be made available in packaging form.
-- Alexander Sack Technical Director, Linaro Platform Teams http://www.linaro.org | Open source software for ARM SoCs http://twitter.com/#%21/linaroorg - http://www.linaro.org/linaro-blog
linaro-dev mailing list linaro-dev@lists.linaro.org http://lists.linaro.org/mailman/listinfo/linaro-dev
linaro-dev mailing list linaro-dev@lists.linaro.org http://lists.linaro.org/mailman/listinfo/linaro-dev
On Tue, 6 Dec 2011 08:31:12 -0700, Joey STANFORD joey@linaro.org wrote:
Hi,
I was looking at the code for this...
Is this something that should be on the Linaro GIT server?
git://github.com/zyga/pip.git
It's called as git clone git://github.com/zyga/pip.git -b develop $LAVA_PREFIX/$LAVA_INSTANCE/src/pip
It's something that will hopefully go into pip upstream at some point, and as pip upstream is on github, it seems a reasonable place for this branch until that happens.
Cheers, mwh
On Tue, Dec 6, 2011 at 3:24 PM, Paul Larson paul.larson@linaro.org wrote:
This mostly affects the server side components, yes. I'm open to the idea of continuing packages for the client-side tools, if it would be useful to others.
At best we would continue packaging for the ubuntu development releases,
but not need to do SRUs regularly to keep them working with new servers... you think that's possible to maintain at this point?
We only have things in the PPA right now, so SRUs aren't needed anyway. Are you talking about continuing packages for everything, or just for the client side tools?
On Tue, Dec 6, 2011 at 9:46 AM, Alexander Sack asac@linaro.org wrote:
On Tue, Dec 6, 2011 at 3:24 PM, Paul Larson paul.larson@linaro.orgwrote:
This mostly affects the server side components, yes. I'm open to the idea of continuing packages for the client-side tools, if it would be useful to others.
At best we would continue packaging for the ubuntu development releases,
but not need to do SRUs regularly to keep them working with new servers... you think that's possible to maintain at this point?
-- Alexander Sack Technical Director, Linaro Platform Teams http://www.linaro.org | Open source software for ARM SoCs http://twitter.com/#%21/linaroorg - http://www.linaro.org/linaro-blog
On Tue, 6 Dec 2011 08:24:40 -0600, Paul Larson paul.larson@linaro.org wrote:
This mostly affects the server side components, yes. I'm open to the idea of continuing packages for the client-side tools, if it would be useful to others.
I think continuing to package the client side tools would be good (I use the packages from the PPA <wink>). They don't change quickly, nor do they have esoteric dependencies.
Cheers, mwh
-
Alexander Sack -
Alexandros Frantzis -
Fathi Boudra -
Joey STANFORD -
Michael Hudson-Doyle -
Paul Larson