Bug 1155918 - update-bootloader --help : does not work
update-bootloader --help : does not work
Status: NEW
Classification: openSUSE
Product: openSUSE Distribution
Classification: openSUSE
Component: Bootloader
Leap 15.1
x86-64 Other
: P5 - None : Normal (vote)
: ---
Assigned To: Jiri Srain
Jiri Srain
Depends on:
  Show dependency treegraph
Reported: 2019-11-05 12:18 UTC by Neil Rickert
Modified: 2020-01-02 13:26 UTC (History)
2 users (show)

See Also:
Found By: ---
Services Priority:
Business Priority:
Blocker: ---
Marketing QA Status: ---
IT Deployment: ---
jsrain: needinfo? (snwint)


Note You need to log in before you can comment on or make changes to this bug.
Description Neil Rickert 2019-11-05 12:18:26 UTC
User-Agent:       Mozilla/5.0 (X11; Linux x86_64; rv:68.0) Gecko/20100101 Firefox/68.0
Build Identifier: 

According to text inside the "update-bootloader" script,
 update-bootloader --help
should output help information.

It doesn't.  It seems to silently update "grub.cfg", but no help information is provided.

Reproducible: Always
Comment 1 Jiri Srain 2019-11-08 12:41:23 UTC
/sbin/update-bootloader is a link to /sbin/pbl

The code only shows help if called as pbl, that said:

 pbl --help

works as expected.

The code is quite full of checks for the way the script is called, I don't really understand the rationale. Steffen, Josef, do you?
Comment 2 Steffen Winterfeldt 2019-11-11 09:53:45 UTC
update-bootloader and bootloader_entry are kept for compatibility (basically
for the kernel packages). Any options you might want to provide to them
are basically no-ops as there's no way to influence what grub is doing anyway.

And yes, that --help is not working for them is an oversight.
Comment 3 Josef Reidinger 2019-12-31 08:39:13 UTC
as steffen said.
Comment 4 Josef Reidinger 2019-12-31 09:13:30 UTC
It is not hard to print pbl --help for update-bootloader --help, but question is if it is what do we want? And if so, maybe mentioning in that help that backward compatible symlinks?
Comment 5 Jiri Srain 2020-01-02 13:26:51 UTC
I read Steffen's answer as something that should be fixed (as an oversight), with the fix being possibly trivial.

Would fix like this be acceptable?