UbuntuUpdates.org

Package "unattended-upgrades"


Moved to bionic:main:updates


Name: unattended-upgrades

Description:

automatic installation of security upgrades

Latest version: *DELETED*
Release: bionic (18.04)
Level: proposed
Repository: main

Links

Save this URL for the latest version of "unattended-upgrades": https://www.ubuntuupdates.org/unattended-upgrades


Download "unattended-upgrades"


Other versions of "unattended-upgrades" in Bionic

Repository Area Version
base main 1.1ubuntu1
updates main 1.1ubuntu1.18.04.8

Changelog

Version: *DELETED* 2019-01-07 09:06:30 UTC
Moved to bionic:main:updates
No changelog for deleted or moved packages.

Version: 1.1ubuntu1.18.04.8 2018-12-13 17:07:05 UTC

  unattended-upgrades (1.1ubuntu1.18.04.8) bionic; urgency=medium

  * Start service after systemd-logind.service to be able to take inhibition
    lock (LP: #1806487)
  * Handle gracefully when logind is down (LP: #1806487)

 -- Balint Reczey <email address hidden> Thu, 13 Dec 2018 14:42:44 +0100

1806487 [regression] Crashing with dbus.exceptions.DBusException when logind can't be started (yet)

Version: *DELETED* 2018-12-04 11:06:58 UTC
Moved to bionic:main:updates
No changelog for deleted or moved packages.

Version: 1.1ubuntu1.18.04.7 2018-11-26 18:07:21 UTC

  unattended-upgrades (1.1ubuntu1.18.04.7) bionic; urgency=medium

  * Trigger unattended-upgrade-shutdown actions with PrepareForShutdown()
    Performing upgrades in service's ExecStop did not work when the upgrades
    involved restarting services because systemd blocked other stop/start
    actions making maintainer scripts time out and be killed leaving a broken
    system behind.
    Running unattended-upgrades.service before shutdown.target as a oneshot
    service made it run after unmounting filesystems and scheduling services
    properly on shutdown is a complex problem and adding more services to the
    mix make it even more fragile.
    The solution of monitoring PrepareForShutdown() signal from DBus
    allows Unattended Upgrade to run _before_ the jobs related to shutdown are
    queued thus package upgrades can safely restart services without
    risking causing deadlocks or breaking part of the shutdown actions.
    Also ask running unattended-upgrades to stop when shutdown starts even in
    InstallOnShutdown mode and refactor most of unattended-upgrade-shutdown to
    UnattendedUpgradesShutdown class. (LP: #1778219)
  * Increase logind's InhibitDelayMaxSec to 30s. (LP: #1778219)
    This allows more time for unattended-upgrades to shut down gracefully
    or even install a few packages in InstallOnShutdown mode, but is still a
    big step back from the 30 minutes allowed for InstallOnShutdown previously.
    Users enabling InstallOnShutdown node are advised to increase
    InhibitDelayMaxSec even further possibly to 30 minutes.
    - Add NEWS entry about increasing InhibitDelayMaxSec and InstallOnShutdown
      changes
  * Ignore "W503 line break before binary operator"
    because it will become the best practice and breaks the build
  * Stop using ActionGroups, they interfere with apt.Cache.clear()
    causing all autoremovable packages to be handled as newly autoremovable
    ones and be removed by default. Dropping ActionGroup usage does not slow
    down the most frequent case of not having anything to upgrade and when
    there are packages to upgrade the gain is small compared to the actual
    package installation.
    Also collect autoremovable packages before adjusting candidates because that
    also changed .is_auto_removable attribute of some of them. (LP: #1803749)
    (Closes: #910874)

 -- Balint Reczey <email address hidden> Mon, 26 Nov 2018 13:37:47 +0100

1803749 apt.Cache.clear() may set apt.Package.is_auto_removable to False
910874 unattended-upgrades removes packages even if - Debian Bug report logs

Version: *DELETED* 2018-10-26 10:06:17 UTC
Moved to bionic:main:updates
No changelog for deleted or moved packages.



About   -   Send Feedback to @ubuntu_updates