[Bug 1604936] Re: Please document command-line options with --help and when called incorrectly

[Brian Murray]

Hello Adam, or anyone else affected,

Accepted shim-signed into xenial-proposed. The package will build now
and be available at https://launchpad.net/ubuntu/+source/shim-
signed/1.19~16.04.1 in a few hours, and then in the -proposed
repository.

Please help us by testing this new package.  See
https://wiki.ubuntu.com/Testing/EnableProposed for documentation how to
enable and use -proposed.  Your feedback will aid us getting this update
out to other Ubuntu users.

If this package fixes the bug for you, please add a comment to this bug,
mentioning the version of the package you tested, and change the tag
from verification-needed to verification-done. If it does not fix the
bug for you, please add a comment stating that, and change the tag to
verification-failed.  In either case, details of your testing will help
us make a better decision.

Further information regarding the verification process can be found at
https://wiki.ubuntu.com/QATeam/PerformingSRUVerification .  Thank you in
advance!

** Changed in: shim-signed (Ubuntu Xenial)
       Status: In Progress => Fix Committed

** Tags added: verification-needed

-- 
You received this bug notification because you are a member of Ubuntu
Foundations Bugs, which is subscribed to shim-signed in Ubuntu.
https://bugs.launchpad.net/bugs/1604936

Title:
  Please document command-line options with --help and when called
  incorrectly

Status in shim-signed package in Ubuntu:
  Fix Released
Status in shim-signed source package in Precise:
  In Progress
Status in shim-signed source package in Trusty:
  In Progress
Status in shim-signed source package in Xenial:
  Fix Committed

Bug description:
  [Impact]
  update-secureboot-policy did not include any help text.

  [Test case]
  - verify 'sudo update-secureboot-policy' works as expected (prompts to disable Secure Boot if it's enabled)
  - verify 'sudo update-secureboot-policy --disable' works as expected (same as above)
  - verify 'sudo update-secureboot-policy --enable' re-enables Secure Boot after it has been disabled (ie. after a run with --disable and a reboot)
  - verify 'update-secureboot-policy --help' displays help text.

  [Regression Potential]
  None. The default behavior without a parameter remains to try to disable Secure Boot if it's not already disabled. --enable is documented behind a new parameter --help which displays usage information.

  ---

  Subject says it all.  Having to read the source to discover --enable
  was irksome.  There should probably also be an opposite explicit
  --disable.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/shim-signed/+bug/1604936/+subscriptions