Package: unattended-upgrades
Version: 0.79.5+steamos1+bsos1
Severity: wishlist
When the Unattended-Upgrade::InstallOnShutdown option is set, u-u
carries out two-stage upgrades:
1. from a cron job: the equivalent of apt-get update;
apt-get --download-only upgrade
2. while shutting down: the equivalent of apt-get update;
apt-get upgrade
This is good from the points of view of "don't upgrade a system that is
in active use" and "make sure that things that require a reboot are
fully applied". However, it assumes that network connectivity is still
available during shutdown, which is not necessarily true.
Some enhancements that would be useful here, which I'd like to look into
implementing:
* after stage 1, if an upgrade allowed by uu's policy is available,
notify the user interface that an upgrade has become available
somehow (perhaps via a D-Bus signal, a flag-file in /run, a tiny
daemon that holds the update state and has a D-Bus API, or something)
* stage 1 should make sure to download and cache enough state that
stage 2 can be done with no network connectivity at all;
stage 2 should work entirely from that cache, and not try to
re-download things
* if some other process invokes "apt-get update" between stage 1 and
shutdown, and gets an even newer set of packages, then the system
should cope gracefully with that, either by cancelling the UI
that recommends a reboot until the newer upgrade has all been
downloaded, or by saving enough state from stage 1 that it can apply
the upgrade during shutdown even though the remote apt lists
have changed
* if the state of the installed system changes after stage 1 has
completed (e.g. via a manual apt-get), then the system should cope
somewhat gracefully; the only way I can think of is to cancel the
UI that recommends a reboot, recompute the upgrade and try again
I'm aware that this might be scope-creep that heads towards the same
territory as PackageKit and aptdaemon - comments on alternatives would
also be welcome. The system I'm interested in already has PackageKit (to
support gnome-packagekit), but I'm aware that PK doesn't have the
apt/dpkg-specific knowledge that uu does, like apt origins and conffile
handling.
S
-- System Information:
Distributor ID: SteamOS
Description: SteamOS 1.0
Release: 1.0
Codename: alchemist
Architecture: x86_64
Kernel: Linux 3.10-3-amd64 (SMP w/4 CPU cores)
Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Versions of packages unattended-upgrades depends on:
ii apt 0.9.7.9+deb7u1+bsos1
ii apt-utils 0.9.7.9+deb7u1+bsos1
ii debconf [debconf-2.0] 1.5.49+bsos6
ii lsb-base 4.1+Debian8+deb7u1+bsos7
ii lsb-release 4.1+Debian8+deb7u1+bsos7
ii python 2.7.3-4+deb7u1+bsos6
ii python-apt 0.8.8.2+bsos7
ii ucf 3.0025+nmu3+bsos6
ii xz-utils 5.1.1alpha+20120614-2+bsos7
unattended-upgrades recommends no packages.
Versions of packages unattended-upgrades suggests:
pn bsd-mailx <none>
pn mail-transport-agent <none>
-- debconf information:
unattended-upgrades/enable_auto_updates: false
--
To UNSUBSCRIBE, email to [email protected]
with a subject of "unsubscribe". Trouble? Contact [email protected]
