diff options
| author | David Kalnischkies <david@kalnischkies.de> | 2017-01-19 01:09:05 +0100 |
|---|---|---|
| committer | David Kalnischkies <david@kalnischkies.de> | 2017-01-19 01:09:05 +0100 |
| commit | 0d9081598afa051409b03dbdbe5025cd7ce59ba4 (patch) | |
| tree | 17b292aebc9e449e7c53740fd48b4319fb7ef0df /apt-pkg/acquire-worker.cc | |
| parent | 22acd327ac39ffe3bb14b3e1f2d1f21761de13ca (diff) | |
don't lock dpkg in update commands
The update command acquires a lock on lists/, but at the end it will
also require the dpkg/lock while building the binary caches. That seems
rather pointless as we are only reading those files, not causing writing
in them. This can also cause problems if a package installation is
running and a background process (like cron) starts an update: If you
are "lucky" enough the update process will pick the dpkg lock in between
apt calls causing the installation process to fail.
Diffstat (limited to 'apt-pkg/acquire-worker.cc')
0 files changed, 0 insertions, 0 deletions