command-not-found (0.2.38-1) unstable; urgency=low
* Update to latest release
- Prints an error message if the command could not be found in the
database (Closes: #551377)
* Packaging changes:
- Use python-support instead of python-central.
- Switch to the new 3.0 (quilt) source format.
* Bugfixing:
- Create symlinks for command-not-found in /usr/lib (used by bash),
and in /usr/bin for manual invocation (Closes: #543747)
- Strip package names so they don't contain newlines (Closes: #521276)
- Fix typo in the description (Closes: #503629)
- Use mode 0644 for the database files (Closes: #522450), and set
the umask to 022 while running the update-command-not-found script.
- Set -e in the maintainer scripts, reported by lintian.
* Change update-command-not-found to only add the section to the database
filenames. Delete old cache files in postinst, so users only get the
new ones.
* Stop installing /etc/bash_command_not_found, since the standard one
included in bash works now.
-- Julian Andres Klode <email address hidden> Mon, 02 Nov 2009 20:43:12 +0100
