Sorry for the delayed reaction. Jakub, that worked like a charm! Thank you.
On Tue, Oct 4, 2011 at 5:30 AM, Jakub Wilk <jw...@debian.org> wrote: > (Disclaimer: I'm not the maintainer of this package and I don't really what > happened here. Perhaps it's another instance of #594814.) > > * Chris Koehnen <crkoeh...@gmail.com>, 2011-10-02, 16:42: >> >> As a work-around, I created a symlink, /usr/lib/pymodules/python2.7, > > Do you mean that /usr/lib/pymodules/python2.7 didn't exist at all? Or did > you have to remove it first? > >> pointing to /usr/lib/pymodules/python2.6. > > Please never ever do things like that. You just broke your system. These > directories are separate for a reason. > > Fortunately, there's an easy way to undo this damage: > 1) Remove /usr/lib/pymodules/python2.*/ (yes, both of them). > 2) Run "update-python-modules -a", which should reconstruct these > directories. > > -- > Jakub Wilk > -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
