On Thu, Dec 2, 2010 at 14:02:27 +0100, Alexander Reichle-Schmehl wrote: > 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? > I think this error comes from running python code before the python-support trigger has a chance to run, so adding update-python-modules -p before the call to hginit might be enough for this bug. Note the other RC bug I filed yesterday while looking at this one though.
Cheers, Julien
signature.asc
Description: Digital signature
