New issue
Advanced search Search tips
Note: Color blocks (like or ) mean that a user may not be available. Tooltip shows the reason.

Issue 643370 link

Starred by 1 user

Issue metadata

Status: Verified
Owner:
Closed: Dec 2016
Cc:
EstimatedDays: ----
NextAction: ----
OS: Chrome
Pri: 2
Type: Bug



Sign in to add a comment

Uninstall the previous chameleond pip packet

Project Member Reported by waihong@chromium.org, Sep 1 2016

Issue description

Any new chameleon install has the problem of issue 632177.

The workaround is to run:

# This uninstalls the 1st chameleond package.
$ pip uninstall chamaleond     

# This uninstalls the 2nd chameleond package.
$ pip uninstall chamaleond

# Remove the chameleond directory
$ rm -rf /usr/lib/python2.7/site-packages/chameleond

# Re-install chameleond
$ /etc/init.d/chameleon-updater start

Should auto-run these commands for the new deployment.
 
Cc: mojahsu@chromium.org
+moja who might deploy a new bundle later.

I should have a script to do this automatically.
Thank for all the help from kalin, Tom, and Jimmy. It seems that there are no PIP related problems recently. Could we close this issue now?

Comment 3 by ka...@chromium.org, Dec 6 2016

Status: Verified (was: Available)
Thanks

Sign in to add a comment