On Wed, Jan 03, 2007 at 10:25:07AM +0100, Pierre Habouzit wrote: > so my guess, but I may be wrong, is that there is old byte compiled > things from your package before the new policy, and that when > /usr/bin/hg does `from mercurial import mdiff` it finds the mdiff.pyc > from /usr/lib/python2.4/site-packages/mercurial/mdiff.pyc FYI, I already tried purging the "mercurial" package. I checked if I could find any more lingering files, and found nothing at the time. I could do this again and check specifically for that directory, if you wish. > (3) the solution is to rm -rf /usr/lib/python*/site-packages/mercurial/ > (yes * because you presumably left python2.3 bytecode over too) > from the postinst. you will be able to drop that upgrade stanza > after the etch release. I uninstalled python2.3 and removed all bytecode a couple of days ago. I also triggered bytecode recompilation with dpkg-reconfigure python2.4 a few times.
Attachment:
signature.asc
Description: Digital signature