I've changed the description to more precisely characterize the
actionable problem here, namely a buggy postinst script that sends
spurious reboot notifications.
** Summary changed:
- reboot every single update in the past month on ubuntu hardy nearly.
massively decreasing my uptime.
+ Spurious reboot notifications caused by libssl upgrades.
** Description changed:
- I have been asked to reboot after every single update in the past month
- on ubuntu hardy nearly. I find this very typical of windows and
- microsoft behavior ( except they only update on tuesdays). How can you
- justify a reboot after i just updated today (see below for the
- packages).
-
- Setting up libruby1.8 (1.8.6.111-2ubuntu1.1) ...
-
- Setting up openssl (0.9.8g-4ubuntu3.3) ...
-
- Setting up ruby1.8 (1.8.6.111-2ubuntu1.1) ...
- Setting up samba-common (3.0.28a-1ubuntu4.3) ...
-
- Setting up smbclient (3.0.28a-1ubuntu4.3) ...
- Setting up samba (3.0.28a-1ubuntu4.3) ...
- * Starting Samba daemons [ OK
]
-
- Setting up samba-doc (3.0.28a-1ubuntu4.3) ...
-
- Setting up libsmbclient (3.0.28a-1ubuntu4.3) ...
-
-
- ---------------------
- Surely that openssl bug was fixed a while ago. If some one can provide a good
reason for all these reboots I will close this. I wish to remind everyone that
rebooting after each update is not a good sign.
+ The postinst script for libssl0.9.8 currently has a bug where it sends a
+ reboot notifcation whenever libssl is configured. So reconfiguring
+ libssl0.9.8 or even just installing libssl0.9.8 will result in a reboot
+ notification. Sending of the reboot notification should definitely be
+ moved inside the upgrading guard. The correct fix is likely to move it
+ inside a version comparison guard for particular important updates like
+ Colin suggests below -- this is what every other standard package using
+ notify-reboot-required does.
** Changed in: openssl (Ubuntu)
Status: New => Confirmed
--
Spurious reboot notifications caused by libssl upgrades.
https://bugs.launchpad.net/bugs/244250
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
