CNF recommends 'snap info <command>' instead of 'snap info <snapname>'
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
command-not-found (Ubuntu) |
Fix Released
|
Critical
|
Michael Vogt |
Bug Description
The new language for CNF with snaps is much better thank you, but there is a mistake in that it recommends that you use 'snap info' with the *command* when it should in fact be 'snap info <snapname>'. As an example:
mark@mark:~$ aws
Command 'aws' not found, but can be installed as:
snap aws-cli
deb awscli ()
See 'snap info aws' for additional versions.
mark@mark:~$ snap info aws
error: no snap found for "aws"
mark@mark:~$ snap info aws-cli
name: aws-cli
summary: Universal Command Line Interface for Amazon Web Services
[...snip...]
In this case, the CNF output should be tweaked to use the snap name not the command name:
See 'snap info aws-cli' for additional versions.
In fact, I think we should tweak the output as follows, in order to line things up and make the commands cut-and-pasteable:
Command 'aws' not found, but can be installed with:
snap install aws-cli # version XXXX is latest/stable
apt install awscli # version YYYY
See 'snap info aws-cli' for additional versions.
tags: | added: bionic bitesize |
Changed in command-not-found (Ubuntu): | |
status: | New → In Progress |
importance: | Undecided → Critical |
assignee: | nobody → Michael Vogt (mvo) |
This is fixed in bionic with 18.04.0~pre6 now:
```
$ aws
Command 'aws' not found, but can be installed as:
sudo snap install aws-cli
sudo apt install awscli
See 'snap info aws-cli' for additional versions.
```