Hi Neil,
I followed the steps you have shared. First I installed 2016.12 version from stretch and then tried to install 2017.7 from jessie-backports.
It is showing* lava-server will upgrade to 2017.7* in up-gradable list but when I am going to upgrade its only updating lava-server-doc package.
Please see the below snapshot in which the list before upgrade and the LAVA packages list after upgrade.
Thanks, Ankit
On Tue, Jul 25, 2017 at 12:41 AM, Neil Williams neil.williams@linaro.org wrote:
There are delays getting packages into stretch-backports, as expected.
In the meantime, this is a reminder of how to use backports: first start with stable.
So when installing LAVA on Stretch, even if what you want is the latest release from production-repo or staging-repo (currently 2017.7), then your first step is to install 2016.12 from Stretch.
# apt -y install lava-server # apt -y install vim # wget http://images.validation.linaro.org/production-repo/ production-repo.key.asc # apt-key add production-repo.key.asc
# vim /etc/apt/sources.list.d/lava.list
# # edit the file to specify: deb http://images.validation.linaro.org/production-repo jessie-backports main
Yes, that is jessie-backports - we don't have packages in stretch-backports at this time.
# apt update # apt upgrade
If you specify backports too early, you'll get a range of other packages from backports - you don't actually need jessie-backports or stretch-backports from Debian at this time.
Packages for jessie-backports are built on jessie. Packages for stretch-backports are built on stretch. It's the same source code in each case. Right now, there aren't any problems with installing from jessie-backports on stretch - particularly if you install lava-server from stretch in the first place so that the majority of your packages come from stretch.
--
Neil Williams
neil.williams@linaro.org http://www.linux.codehelp.co.uk/ _______________________________________________ Lava-users mailing list Lava-users@lists.linaro.org https://lists.linaro.org/mailman/listinfo/lava-users