* Mathew Hodson [2015-11-03 20:09 -0000]: > ** Changed in: command-not-found (Ubuntu) > Importance: Undecided => Medium
'Medium' might be too high (if anybody cares if it is low or medium): I wrote in my initial mail: | I don't use Ubuntu, but I assume that the file bash_command_not_found | in the bzr repository is installed to /etc Looks like this assumption was wrong: <http://packages.ubuntu.com/search?searchon=contents&keywords=_command_not_found&mode=&suite=xenial&arch=any>: | You have searched for paths that end with _command_not_found in suite xenial, all sections, and all architectures. Found 1 results. | | File Packages | /etc/zsh_command_not_found command-not-found | Hence, the actual bug only affects upstream, but not the Ubuntu package, but Ubuntu would benefit from the minor zsh improvements. Shipping (a fixed) bash_command_not_found in the source package and providing it in the upstream repository is still useful, for example, a sysadmin might disable command-not-found in the system wide bash.bashrc and source /etc/bash_command_not_found if it exists in the skeleton .bashrc. Carsten -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1479805 Title: /etc/bash_command_not_found is utterly broken To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/command-not-found/+bug/1479805/+subscriptions -- ubuntu-bugs mailing list [email protected] https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
