The README file needs to be updated for this package:
$ less /usr/share/doc/command-not-found/README
...
To use it in bash, please add the following line to your .bashrc file:
. /etc/bash_command_not_found
...
--
[gutsy] command-not-found not found
https://bugs.launchpad.net/bugs/135794
You rece
Seems to be fixed according to the comments
** Changed in: command-not-found (Ubuntu)
Status: Confirmed => Fix Released
--
[gutsy] command-not-found not found
https://bugs.launchpad.net/bugs/135794
You received this bug notification because you are a member of Ubuntu
Bugs, which is the b
Yes, we can mark it as resolved. I just don't know how to do that :-)
On Nov 17, 2007 10:20 PM, RW Penney <[EMAIL PROTECTED]> wrote:
> Can this bug be marked as resolved?
>
> Package bash-3.2-0ubuntu11, as used in xubuntu7.10, appears to correctly
> reference /usr/lib/command-not-found in /etc/bas
Can this bug be marked as resolved?
Package bash-3.2-0ubuntu11, as used in xubuntu7.10, appears to correctly
reference /usr/lib/command-not-found in /etc/bash.bashrc.
--
[gutsy] command-not-found not found
https://bugs.launchpad.net/bugs/135794
You received this bug notification because you are
** Changed in: command-not-found (Ubuntu)
Sourcepackagename: bash => command-not-found
--
[gutsy] command-not-found not found
https://bugs.launchpad.net/bugs/135794
You received this bug notification because you are a member of Ubuntu
Bugs, which is the bug contact for Ubuntu.
--
ubuntu-bugs ma
Changed package to bash
** Changed in: bash (Ubuntu)
Sourcepackagename: command-not-found => bash
--
[gutsy] command-not-found not found
https://bugs.launchpad.net/bugs/135794
You received this bug notification because you are a member of Ubuntu
Bugs, which is the bug contact for Ubuntu.
--
ub
Promoting to high as it makes c-n-f not usable with current releases.
This bug can be fixed by either patching bash: /etc/bash.bashrc to point
to the new location of command-not-found OR by patching command-not-
found to include a symlink that will be deprecated with future releases.
** Changed i
topdog wrote:
> Bash expects the it to be at this location /usr/bin/command-not-found
> The new package is installing it in the wrong location /usr/lib/command-
> not-found.
It is, IMHO, not in the wrong location. AFAIK, binaries in /usr/bin/ are
meant for users and binaries in /usr/lib are for "
Bash expects the it to be at this location /usr/bin/command-not-found
The new package is installing it in the wrong location /usr/lib/command-
not-found.
[EMAIL PROTECTED]:~# dpkg -L command-not-found
/.
/usr
/usr/share
/usr/share/doc
/usr/share/doc/command-not-found
/usr/share/doc/command-not-fou
