command-not-found
Introduction[edit]
Quote Debian package command-not-found
:
Suggest installation of packages in interactive bash sessions This package will install a handler for command_not_found that looks up programs not currently installed but available from the repositories.
Installation[edit]
The order in which these commands are run matter, [1] but the process is idempotent. This means it is possible to re-apply all of the following steps.
1. Delete /etc/apt/apt.conf.d/30usability-misc
because it contains settings that speed up APT
but break
command-not-found
. [2]
2. Install command-not-found
.
Install command-not-found
. To accomplish that, the following steps A. to D. need to be done.
A. Update the package lists.
B. Upgrade the system.
C. Install the command-not-found
package.
Using apt
command line parameter --no-install-recommends
is in most cases optional.
D. Done.
The procedure of installing command-not-found
is complete.
3. Run update-command-not-found
with root rights.
4. Done.
Setup of update-command-not-found
has been completed.
Issues[edit]
local variable 'cnf' referenced before assignment[edit]
- https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=917455
- https://salsa.debian.org/jak/command-not-found/-/merge_requests/1
See Also[edit]
apt-file
- command-not-found - WARNING:root:could not open file '/etc/apt/sources.list'
- Speeding up "apt update" with Acquire::Languages=none and Contents-deb::DefaultEnabled=false - It's so much faster!
Footnotes[edit]
- ↑
Also
apt update
cannot be skipped since package contents files need to be downloaded. - ↑
Acquire::IndexTargets::deb::Contents-deb::DefaultEnabled false;
breaks
command-not-found
because it requires/var/lib/apt/lists/*Contents*
to exist.See: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=857090
Unfinished: This wiki is a work in progress. Please do not report broken links until this notice is removed, use Search Engines First and contribute improving this wiki.