It does appear, however, that despite the above comment (which I think highlights ways we can make this foot a smaller target), this definitely began with human error:
That's a manual apt dist-upgrade which would have asked for confirmation on that removal. unattended-upgrades alone would have never gotten into this situation, as it won't remove to force an upgrade.
It does appear, however, that despite the above comment (which I think highlights ways we can make this foot a smaller target), this definitely began with human error:
Start-Date: 2018-08-14 13:37:10 4.15.0- 32-generic: amd64 (4.15.0-32.35, automatic), linux-headers- 4.15.0- 32:amd64 (4.15.0-32.35, automatic) generic: amd64 (4.15.0.31.33, 4.15.0.32.34), linux-libc- dev:amd64 (4.15.0-31.33, 4.15.0-32.35) generic: amd64 (4.15.0.31.33), linux-generic:amd64 (4.15.0.31.33)
Commandline: apt dist-upgrade
Install: linux-headers-
Upgrade: linux-headers-
Remove: linux-signed-
End-Date: 2018-08-14 13:37:16
That's a manual apt dist-upgrade which would have asked for confirmation on that removal. unattended-upgrades alone would have never gotten into this situation, as it won't remove to force an upgrade.