I believe the plan is to eventually enable the automatic updates by default, but I don’t know of the timeline for that yet.
Here’s the simple way to enable the automatic staging of updates (assuming you haven’t touched /etc/rpm-ostreed.conf
at all):
$ sudo sed -i 's|^#AutomaticUpdatePolicy=none|AutomaticUpdatePolicy=stage|' /etc/rpm-ostreed.conf
$ sudo rpm-ostree reload
$ sudo systemctl enable rpm-ostreed-automatic.timer --now
Afterwards, you can inspect rpm-ostree
and the timer to see your changes took effect:
$ rpm-ostree status
State: idle
AutomaticUpdates: stage; rpm-ostreed-automatic.timer: no runs since boot
Deployments:
● ostree://fedora:fedora/30/x86_64/testing/silverblue
Version: 30.20190729.0 (2019-07-29T02:34:10Z)
BaseCommit: a5d1add72506ea9797b1517397b8dd4774b45766aa777cb39b0ff8a0565d65bf
GPGSignature: Valid signature by F1D8EC98F241AAF20DF69420EF3C111FCFC659B9
LayeredPackages: chromium cockpit-bridge compat-ffmpeg28 fedora-arm-installer ffmpeg-libs krb5-workstation ksmtuned libvirt libvirt-client libvirt-daemon-kvm libvirt-devel qemu-kvm tilix tmux vagrant-libvirt vim-enhanced virt-install
virt-manager
$ systemctl status rpm-ostreed-automatic.timer
● rpm-ostreed-automatic.timer - RPM-OSTree Automatic Update Trigger
Loaded: loaded (/usr/lib/systemd/system/rpm-ostreed-automatic.timer; enabled; vendor preset: disabled)
Active: active (waiting) since Tue 2019-07-30 09:48:11 EDT; 32min ago
Trigger: Tue 2019-07-30 10:47:52 EDT; 27min left
Docs: man:rpm-ostree(1)
man:rpm-ostreed.conf(5)