This is not a bug in command-not-found. You essentially broke the system
by removing python that came with the installation (and on which many
things depend on, including on binary modules that are not built against
python2.7) and symlinked your own custom python in its place.
Please don't do that and especially don't file bugs about command-not-
found. The error message is caused by the /usr/bin/command-not-found not
being able to find it's required components as the search path for
python2.6 and 2.7 is different. If you really want to use python2.7
install it from the maverick backports (or build it yourself) and read
about python-support and python-central on how python is installed and
managed in debian-based distributions.
** Changed in: command-not-found (Ubuntu)
Status: New => Invalid
** Summary changed:
- ln and command-not-found crash with python
+ command-not-found cannot find required modules after manually replacing
python2.6 with custom-built python2.7
--
command-not-found cannot find required modules after manually replacing
python2.6 with custom-built python2.7
https://bugs.launchpad.net/bugs/622370
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
