Traceback when attempting to uninstall a package that isn't installed

[Timothy R. Chavez]

Attempting to uninstall a snappy package that isn't presently installed results in a traceback rather than a friendly error statement.

ubuntu@localhost:~$ snappy versions
Part Tag Installed Available Fingerprint Active
ubuntu-core edge 141 - 7f068cb4fa876c *
ubuntu@localhost:~$ snappy uninstall docker
Traceback (most recent call last):
  File "/usr/bin/click", line 86, in <module>
    sys.exit(main())
  File "/usr/bin/click", line 82, in main
    return mod.run(args)
  File "/usr/lib/python3/dist-packages/click/commands/unregister.py", line 55, in run
    old_version = registry.get_version(package)
GLib.Error: click_user_error-quark: docker does not exist in any database for user @all (7)
ubuntu@localhost:~$

[Alexander Sack (asac)]

mvo: I think we should fold this in a more general "error cases should report cleanly for users what is going on" task...

[Alexander Sack (asac)]

tagged this as snappy-xp-console to ensure we feed this into our planning for next iteration console experience.

[Michael Vogt (mvo)]

$ sudo snappy remove foo
Removing foo
snappy package not found