On Wed, Oct 26, 2011 at 10:01, Javi Merino <[email protected]> wrote: > On 25/10/11 00:40, Thilo-Alexander Ginkel wrote: >> Package: mercurial >> Version: 1.6.4-1 >> Severity: normal >> Tags: squeeze >> >> Mercurial as installed on a fresh Debian 6.0 installation fails to execute >> with the following error message: >> >> tg@vega ~$ hg >> abort: couldn't find mercurial libraries in [/usr/bin /usr/lib/python2.6 >> /usr/lib/python2.6/plat-linux2 /usr/lib/python2.6/lib-tk >> /usr/lib/python2.6/lib-old /usr/lib/python2.6/lib-dynload >> /usr/local/lib/python2.6/dist-packages /usr/lib/python2.6/dist-packages >> /usr/lib/pymodules/python2.6] >> (check your install and PYTHONPATH) > > Can you please run "ls /usr/lib/pymodules/python2.6/" and "debsums -c > mercurial mercurial-common" (you may need to install the debsums package)?
-- 8< -- tg@vega ~$ ls /usr/lib/pymodules/python2.6/ beaker boto-1.9b.egg-info hgext mercurial pygments reportbug Beaker-1.5.4.egg-info chardet lsb_release.py mercurial-1.6.4.egg-info Pygments-1.3.1.egg-info reportbug-4.12.6.egg-info boto chardet-2.0.1.egg-info lsb_release.pyc OpenSSL pyOpenSSL-0.10.egg-info -- 8< -- -- 8< -- tg@vega ~$ debsums -c mercurial mercurial-common -- 8< -- <no output> > Can you try to reinstall the package with "aptitude install --reinstall > mercurial mercurial-common"? It should say "Processing triggers for > python-support ..." as part of the output. My aptitude does not support --reinstall, but apt-get does: -- 8< -- tg@vega ~$ sudo apt-get install --reinstall mercurial mercurial-common Reading package lists... Done Building dependency tree Reading state information... Done 0 upgraded, 0 newly installed, 2 reinstalled, 0 to remove and 0 not upgraded. Need to get 0 B/1,414 kB of archives. After this operation, 0 B of additional disk space will be used. (Reading database ... 80369 files and directories currently installed.) Preparing to replace mercurial-common 1.6.4-1 (using .../mercurial-common_1.6.4-1_all.deb) ... Unpacking replacement mercurial-common ... Preparing to replace mercurial 1.6.4-1 (using .../mercurial_1.6.4-1_amd64.deb) ... Unpacking replacement mercurial ... Setting up mercurial-common (1.6.4-1) ... Setting up mercurial (1.6.4-1) ... -- 8< -- No triggers. > I've just installed mercurial in a fresh squeeze install and it works > for me. I also set up another virtual machine where it works correctly, but I cannot easily perform a reinstall as the system in question is provided as a VPS image, so I cannot really perform a scratch install. Based on the output I got on my VM when installing mercurial I however figured out that the triggers for python-support are not being invoked. debsums -c python-support showed no differences, but reinstalling python-support before reinstalling mercurial and mercurial-common actually solved the issue. Thanks for your help! Regards, Thilo -- To UNSUBSCRIBE, email to [email protected] with a subject of "unsubscribe". Trouble? Contact [email protected]
