Package: apt Version: 1.4~rc2 Followup-For: Bug #844453 I believe an appropriate fix for this bug would be to change apt-daily.timer so that systemd does not attempt to run APT daily background processing during boot-up, but only some time afterward. An appropriate configuration would be similar to the systemd-tmpfiles-clean.timer, which runs 15 minutes after boot and once a day thereafter.
For instance --- apt-daily.timer.orig 2017-03-27 10:07:32.697972326 -0400 +++ apt-daily.timer 2017-03-27 10:08:37.022378906 -0400 @@ -2,8 +2,9 @@ Description=Daily apt activities [Timer] -OnCalendar=*-*-* 6,18:00 -RandomizedDelaySec=12h +OnBootSec=15min +OnUnitActiveSec=1d +RandomizedDelaySec=30min AccuracySec=1h Persistent=true I have made this change in my local configuration via override file and it appears to work well; at least, apt-daily.service is no longer the long pole in 'systemd-analyze blame' output. zw