Classic snaps 'not found' if --classic argument is missing

Bug #1659744 reported by Stuart Bishop on 2017-01-27
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
Snappy
High
John Lenton

Bug Description

If the user forgets the '--classic' argument to 'snap install', then they get a confusing error message. I think the correct thing to do is inform the user that they need to give consent and use the --classic option to perform the install.

$ sudo snap install juju-act
error: cannot install "juju-act": snap not found

$ sudo snap install juju-act --classic
juju-act 1.0.0 from 'stub' installed

John Lenton (chipaca) wrote :
Changed in snappy:
status: New → Fix Committed
assignee: nobody → John Lenton (chipaca)
importance: Undecided → High
John Lenton (chipaca) wrote :

That branch isn't the end of the work in this space, but it addresses this immediate issue. The error message still needs picking up by the client and presented to the user better, and some other operations that take --classic need similar work.

To post a comment you must log in.
This report contains Public information  Edit
Everyone can see this information.

Other bug subscribers