needrestart: better document Ubuntu-specific behaviours

[Simon Chopin]

[Impact]
As evidenced in https://lists.ubuntu.com/archives/ubuntu-devel-discuss/2024-June/019706.html the Ubuntu customizations to needrestart behaviour need to be much better documented, at least in the default configuration file and the CLI manpage/--help blurb, to try and minimize the amount of user surprise and uproar.

[Test plan]
# Check the contents of /etc/needrestart/needrestart.conf for 'UBUNTU' strings
man needrestart # that should also mention Ubuntu
needrestart --help # likewise
cat /usr/share/doc/needrestart/README.Ubuntu

[ Where problems could occur ]
This is pretty safe, unless someone actually parses out the needrestart --help somewhere?

[Launchpad Janitor (janitor)]

This bug was fixed in the package needrestart - 3.6-8ubuntu3

---------------
needrestart (3.6-8ubuntu3) oracular; urgency=medium

  * d/p/ubuntu-mode.patch: Don't touch /run/reboot-required on kernel updates
    (LP: #2065863)
  * Ubuntu mode: disable it if restart mode has been explicitly set
    (LP: #2068543)
  * Add some inline documentation for the Ubuntu mode (LP: #2068573)
  * Don't restart the google-guest-agent service (LP: #2063442)
  * Don't restart the GH runner provisioner (LP: #2067800)
  * tests: guard against looping when failing.

 -- Simon Chopin <email address hidden> Fri, 14 Jun 2024 11:57:11 +0200

[Łukasz Zemczak (sil2100)]

Hello Simon, or anyone else affected,

Accepted needrestart into noble-proposed. The package will build now and be available at https://launchpad.net/ubuntu/+source/needrestart/3.6-7ubuntu4.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 on 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, what testing has been performed on the package and change the tag from verification-needed-noble to verification-done-noble. If it does not fix the bug for you, please add a comment stating that, and change the tag to verification-failed-noble. In either case, without details of your testing we will not be able to proceed.

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

N.B. The updated package will be released to -updates after the bug(s) fixed by this package have been verified and the package has been in -proposed for a minimum of 7 days.

[Simon Chopin (schopin)]

Verified in a fresh container:

root@needrestart-nrconf:~# dpkg -l needrestart | tail -n 1
ii needrestart 3.6-7ubuntu4.1 all check which daemons need to be restarted after library upgrades
root@needrestart-nrconf:~# man needrestart
root@needrestart-nrconf:~# man needrestart | grep -i ubuntu
          u (u)buntu mode, used to customized the behaviour in the APT hook. See /usr/share/doc/README.Ubuntu.
root@needrestart-nrconf:~# needrestart --help | grep -i ubuntu
 u (u)buntu mode for the APT hook, see /usr/share/doc/needrestart/README.Ubuntu
root@needrestart-nrconf:~# cat /usr/share/doc/needrestart/README.Ubuntu
Starting from Ubuntu 24.04, needrestart in the default configuration will by
default not show the Debconf prompt, and restart automatically the affected
services. This includes when run as part of `unattended-upgrades` to ensure
that the security updates it brings are actually applied to running services
rather than leaving the system vulnerable.

For more details, see the following Discourse post:

https://discourse.ubuntu.com/t/needrestart-changes-in-ubuntu-24-04-service-restarts/44671
root@needrestart-nrconf:~#