Hi, Bernard

In my opinion, "./lava-deployment-tool setup" is used to update the common libs that some of the LAVA components need. so I guess in such situation, just run the setup and then run the upgrade, then everything will be OK.

But of course, please wait for the official answer from LAVA team:)

Thanks, Yongqin Liu

On 18 March 2013 17:38, Bernard Park bernard.park@linaro.org wrote:

Thanks for your comments YongQin,

By the way, it can be happen in normal situation, let me give you an example,

1. An in-house LAVA operator setup and running revision number XXX.

2. After few months later, he wants to upgrade in- LAVA from XXX to

XXX+n for some reason.

3. However, he deleted lava-deployment-tool directory which he used to

setup so he is trying branch lava-deployment-tool again but he might have the same message what I have cause newly branched lava-deployment-tool doesn’t know about previous installation

Thanks, Bernard

*From:* YongQin Liu [mailto:yongqin.liu@linaro.org] *Sent:* Friday, March 15, 2013 12:46 PM *To:* Bernard Park *Cc:* Validation Linaro *Subject:* Re: [Linaro-validation] bzr pull before upgrade issue

On 15 March 2013 11:33, Bernard Park bernard.park@linaro.org wrote:

Hello all,

After up and running LAVA with lava-deployment-tool, I have ran wrong command to upgrade my LAVA packages

1. Move to lava-deployment-tool

*2.** *$bzr pull (this is my mistake)

3. After then I got a following message whenever I try to upgrade

“$lava-deployment-tool upgrade <reno>

A. *“Please run './lava-deployment-tool setup' first’”*

In this situation, how to resolve this issue and upgrade easily?

I think you can do as it said, *:)*

*run './lava-deployment-tool setup' first*

--

Thanks,

Yongqin Liu

---

#mailing list

linaro-android@lists.linaro.org linaro-dev@lists.linaro.org

http://lists.linaro.org/mailman/listinfo/linaro-android

linaro-validation@lists.linaro.org linaro-dev@lists.linaro.org

http://lists.linaro.org/pipermail/linaro-validation