dpkg lockf during dist-upgrade, not nice

[wdoekes]

root      1269  0.0  2.3 427356 93296 pts/4    S+   15:51   0:00                                  \_ /usr/bin/python3 /tmp/ubuntu-release-upgrader-8fr77y46/xenial --mode=server --frontend=DistUpgradeViewT
root      1361  0.0  0.0   4508   792 pts/4    S+   15:51   0:00                                      \_ sh -c service gocollect status >/dev/null && if ! service gocollect restart; then echo '(suppressin
root      1372  0.0  0.0   4508  1708 pts/4    S+   15:51   0:00                                          \_ /bin/sh /etc/init.d/gocollect restart
root      1401  0.2  0.2  14928 11380 pts/4    Sl+  15:51   0:00                                              \_ /usr/sbin/gocollect
root      1647  0.0  0.0   8648   784 pts/4    S    15:51   0:00                                                  \_ timeout 180s /usr/share/gocollect/collectors/os.pkg
root      1648  0.0  0.0   4508   696 pts/4    S    15:51   0:00                                                      \_ /bin/sh /usr/share/gocollect/collectors/os.pkg
root      1649  0.0  0.1  30148  6524 pts/4    S    15:51   0:00                                                          \_ python /usr/share/gocollect/collectors/util/lockf.py 120 /var/lib/dpkg/lock /va
root      1650  0.0  0.0   4508   104 pts/4    S    15:51   0:00                                                          \_ /bin/sh /usr/share/gocollect/collectors/os.pkg

[wdoekes]

That wasn't enough. Apparently the gocollect was run in the foreground too (for some reason).

Had to kill it. Had to do it. It's true.

[wdoekes]

Can't we just fix this by using a sleep? It shouldn't be in the foreground when it's doing os.pkg...
Why was this never backgrounded?

[wdoekes]

Or. We can fix this by not doing a restart after post-install? We already have a post-apt-run-restart hook anyway....