HowIInstalledMercurial

How I unstalled Mercurial

After I had some headache with Mercurial (I guess the reason was improper Python version), I decided to reinstall both using pkg-get and finally got rid of all problems. The below is the description of how I did this. This dos not pretend to be a complete guide, but hopefully will help somebody.

My OS is Solaris 10 on x86 machine. Most likely the below applies to such machines only.

Clean up previous versions (optional)

I personally would recommend you to first get rid of all python and mercurial instances on your machine. But this can be easily skipped, in this case you have just to make sure your PATH and LD_LIBRARY_PATH include new versions, not old ones.

To remove what is installed as packages, you can use

pkginfo | egrep "(mercurial)|(python)"
sudo pkgrm <found-packages>

To remove other just use rm command.

Install new vewrsions via pkg-get

Sometimes pkg-get works well only if you cd to its directory, so

cd /opt/csw/bin


To make sure it won't complain on incorrect access privileges:

mkdir /home/${USER}/.gnupg 
chmod -R 777 /home/${USER}/.gnupg 

If pkg-get complains about the absence of keys:

sudo wget http://www.blastwave.org/mirrors.html 
sudo ./gpg --import mirrors.html

Update the pkg-get list:

sudo ./pkg-get  -U

Try getting python and Mercurial

sudo ./pkg-get -i python
sudo ./pkg-get -i mercurial

Most likely it will fail because of not updated dependencies. The easiest way of coping with that is to use

sudo ./pkg-get update

(it will take rather long time)

Another way is removing each package it complains about via sudo pkgrm <name> and restarting pkg-get; this should be repeated until it finishes successfully.

Remove PYTHON* environment variables from your .bashrc oh whatever.

Make sure it works

Make sure that `which hg` is /opt/csw/bin/hg.

Add proxy to your environment variables:

export http_proxy=<address>:<port>

Try it. If you encounter any issues, check that your LD_LIBRARY_PATH does not contain paths with previous versions or paths that newer versions precede older ones.

And don't forger to restart bash or to invoke ". ~/.bashrc" after you edited it.

Good luck!

Not logged in. Log in, Register

By use of this website, you agree to the NetBeans Policies and Terms of Use. © 2012, Oracle Corporation and/or its affiliates. Sponsored by Oracle logo