[Bug 1031098] Re: Design flaw: does nothing after install? split package into {, -core} ?

Mathew Hodson mathew.hodson at gmail.com
Thu Sep 8 00:13:31 UTC 2016


I believe this is fixed in Xenial and auto-updates should be enabled by
default.

---
unattended-upgrades (0.90) unstable; urgency=medium

  [ Alexandre Detiste ]
  * tweak a bit the French translations

  [ Michael Vogt ]
  * debian/templates: set unattended-upgrades/enable_auto_updates to
    "true" (Closes: #707055)
  * debian/config: set debconf questions about origin/enable to low

 -- Michael Vogt <mvo at debian.org>  Thu, 18 Feb 2016 14:05:58 -0800

** Changed in: unattended-upgrades (Ubuntu)
   Importance: High => Wishlist

** Changed in: unattended-upgrades (Ubuntu)
       Status: In Progress => Fix Released

** Summary changed:

- Design flaw: does nothing after install? split package into {,-core} ?
+ Auto-updates should be enabled by default

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

Title:
  Auto-updates should be enabled by default

Status in unattended-upgrades package in Ubuntu:
  Fix Released
Status in unattended-upgrades package in Debian:
  Unknown

Bug description:
  situation: 
  minimal ubuntu server image, installation of this package done manually with "aptitude install unattended-upgrades".

  problem: 
  unattended-upgrades actually do not happen, because I have to edit config files before - but the system does not give me any hint about this - so I just install this package and think "great feature, can sleep now very good" - evil guys are just waiting for the first remote exploit and they know that I am sleeping well while my system gets more vulnarable with every missed security update... 

  [Additionally, the documentation about "Automatic updates" - btw, why
  the irritating change of terminology here? - is flawed, see bug filed
  there by me today.]

  I do not understand why unattended-upgrades do not just happen after I
  install this package. This looks like a design error to me and should
  be corrected - this security related feature should be as easy as
  possible to get working. This package should just start working with
  reasonable defaults without any need for the user to edit config
  files.

  And if there is a need to edit config files after installation, the
  user should be informed about this fact right after installation -
  from what I see from doing tests with 12.04 this feature does not just
  start working ootb, but needs manual config file editing after
  installation.

  It would be even better if the installation process will not end
  successfully, if it just installs this package without proper config -
  there is no sense in having an installed package named "unattended-
  upgrades" if these upgrades are actually not going to happen.

  My observations may be wrong. I hope so.

  Thank you very much for your attention!

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/unattended-upgrades/+bug/1031098/+subscriptions



More information about the foundations-bugs mailing list