unattended-upgrade email should inform if reboot is required

Bug #415202 reported by Nick Barcet
This bug affects 4 people
Affects Status Importance Assigned to Milestone
unattended-upgrades (Ubuntu)
Fix Released
Nominated for Lucid by tuttle

Bug Description

Binary package hint: unattended-upgrades

unattended-upgrade sends an email informing of an upgrade if 'Unattended-Upgrade::Mail' is set in /etc/apt/apt.conf.d/50unattended-upgrades, but this email does not clearly indicate to the admin wether a reboot is required or not.

I think it would be useful to add this, with maybe even a hint such as a [reboot] tag in the title, in the mail that is sent.

Nick Barcet (nijaba)
Changed in unattended-upgrades (Ubuntu):
importance: Undecided → Wishlist
Revision history for this message
Paul Elliott (omahn) wrote :

This is a first pass at adding such support, feedback welcome.

Revision history for this message
Paul Elliott (omahn) wrote :

I've removed the debdiff while I make a couple of improvements. I'll upload again tomorrow.

Revision history for this message
Paul Elliott (omahn) wrote :

Debdiff to add suggested support. Working locally here on a couple of test of machines. Too late for Karmic but might be worth looking at for Lucid. Feedback welcome.

Revision history for this message
tuttle (sven-launchpad-anderson) wrote :

This is useful, please add it!

Michael Vogt (mvo)
Changed in unattended-upgrades (Ubuntu):
status: New → In Progress
Revision history for this message
Launchpad Janitor (janitor) wrote :

This bug was fixed in the package unattended-upgrades - 0.60ubuntu1

unattended-upgrades (0.60ubuntu1) maverick; urgency=low

  * Include reboot required notification in sent emails (LP: #415202)
    and add test for it (thanks to Paul Elliott for the initial patch)
  * allow ${distro_id} and ${distro_codename} in
    Unattended-Upgrade::Allowed-Origins and update conffile to it
 -- Michael Vogt <email address hidden> Mon, 17 May 2010 15:19:21 +0200

Changed in unattended-upgrades (Ubuntu):
status: In Progress → Fix Released
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers