Hi all,
I have used command-not-found in the past and it used to be good.
I just installed it , ran an apt update and tried to run a command
which I knew whose binary isn't installed but command-not-found didn't
work.
I am using zsh though if it makes any difference.
% apt-cache policy command-not-found
command-not-found:
Installed: 0.2.38-4
Candidate: 0.2.38-4
Version table:
*** 0.2.38-4 900
900 http://httpredir.debian.org/debian buster/main amd64 Packages
1 http://httpredir.debian.org/debian unstable/main amd64 Packages
100 /var/lib/dpkg/status
% sudo apt update
[sudo] password for shirish:
Hit:1 http://cdn-fastly.deb.debian.org/debian buster InRelease
Hit:2 http://cdn-fastly.deb.debian.org/debian unstable InRelease
Hit:3 http://cdn-fastly.deb.debian.org/debian experimental InRelease
Reading package lists... Done
Building dependency tree
Reading state information... Done
All packages are up to date.
% cmake
zsh: command not found: cmake
As I understand or remember it from before, it should have told that I
needed to install cmake binary/package to run the command
-- System Information:
Debian Release: buster/sid
APT prefers testing
APT policy: (900, 'testing'), (1, 'experimental'), (1, 'unstable')
Architecture: amd64 (x86_64)
Kernel: Linux 4.14.0-2-amd64 (SMP w/4 CPU cores)
Locale: LANG=en_IN, LC_CTYPE=en_IN (charmap=UTF-8), LANGUAGE=en_IN:en
(charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Init: systemd (via /run/systemd/system)
LSM: AppArmor: enabled
Versions of packages command-not-found depends on:
ii apt-file 3.1.5
ii lsb-release 9.20170808
ii python 2.7.14-4
ii python-gdbm 2.7.14-1
command-not-found recommends no packages.
command-not-found suggests no packages.
-- no debconf information
Hope it helps in diagnozing the situation, please let me know if any
more info. is needed.
--
Regards,
Shirish Agarwal शिरीष अग्रवाल
My quotes in this email licensed under CC 3.0
http://creativecommons.org/licenses/by-nc/3.0/
http://flossexperiences.wordpress.com
EB80 462B 08E1 A0DE A73A 2C2F 9F3D C7A4 E1C4 D2D8
