Hi! * Lucas Nussbaum <lu...@lucas-nussbaum.net> [101121 11:07]:
> While testing the installation of all packages in unstable, I ran > into the following problem: > > Setting up mercurial-common (1.6.4-1) ... > > Setting up mercurial (1.6.4-1) ... [..] > > Setting up mercurial-server (1.0.1-1.1) ... > > 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) > > dpkg: error processing mercurial-server (--configure): I fail to reproduce this bug. I tried current sid and current squeeze (which actually means: The very same versions you tried), using apt-get as well als aptitude. It always got installed and set up without any errors. I tried my pbuilder chroots as well as installation with on the fly chroots created by piuparts. Looking at the postrm script, I guess the following line must have caused the error (as everything else doesn't involve python): su -c "/usr/share/mercurial-server/init/hginit /usr/share/mercurial-server" hg And my first thought was, that this line might need some tighter dependency mercurial / mercurial-common, but looking at your installation log, it shows that mercurial-common and mercurial itself are already installed and configured at that point. Can you reproduce this error? Best Regards, Alexander -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
