Hmmm. Ran -zypper dup- and I see the following, shown in the pre-form-text below
The following 2 NEW packages are going to be installed:
cnf-rs 0.5.2~0-1.1 x86_64 openSUSE-Tumbleweed-Oss openSUSE
cnf-rs-bash 0.5.2~0-1.1 noarch openSUSE-Tumbleweed-Oss openSUSE
I cancelled zypper (and marked those as ‘taboo’), cause it seems odd.
I did a google search for “tumbleweed cnf-rs” and zero results.
Also did a “cnf-rs” search and got health-related hits.
I ran Yast2 and checked , yep - they are there:
“Bash setup code for command-not-found handler cnf-rs”
Is this a decision only for openSuse folks to have code just for handling “command not found” for bash?
It seems to me that would be default behavior for bash, after all these years.
Seems odd. Why didn’t the bash authors think it’s required ?
Sorry, just seems suspicious as I never found any internet hits for it.
I prefer scout-command-not-found, cnf-rs requires more key strokes and doesn’t advise the package it’s from…
cnf-rs echo
Absolute path to 'echo' is '/usr/bin/echo'. Please check your $PATH variable to see whether it contains the mentioned path.
versus
cnf echo
Program 'echo' is present in package 'coreutils', which is installed on your system.
Absolute path to 'echo' is '/usr/bin/echo'. Please check your $PATH variable to see whether it contains the mentioned path.
zypper in scout-command-not-found
Solution 1: deinstallation of cnf-rs-bash-0.5.2~0-1.1.noarch
zypper al cnf-rs*