From b6f1b480164b454661ddd4fdd3968302c6a3ebf6 Mon Sep 17 00:00:00 2001 From: David Kalnischkies Date: Wed, 10 Feb 2016 12:26:49 +0100 Subject: get dpkg lock in build-dep if cache was invalid again MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 8bit Regression introduced in a249b3e6fd798935a02b769149c9791a6fa6ef16, which in the case of an invalid cache would build the first part unlocked and later pick up the (still unlocked) cache for further processing, so the system got never locked and apt would end up complaining about being unable to release the lock at shutdown. The far more common case of having a valid cache worked as expected and hence covered up the problem – especially as tests who would have noticed it are simulations only, which do not lock. Closes: 814139 Reported-By: Balint Reczey Reported-By: Helmut Grohne on IRC --- apt-pkg/cachefile.cc | 1 + 1 file changed, 1 insertion(+) (limited to 'apt-pkg') diff --git a/apt-pkg/cachefile.cc b/apt-pkg/cachefile.cc index 6db0749d4..909da5cb4 100644 --- a/apt-pkg/cachefile.cc +++ b/apt-pkg/cachefile.cc @@ -238,6 +238,7 @@ bool pkgCacheFile::AddIndexFile(pkgIndexFile * const File) /*{{{*/ ExternOwner = false; Map = NULL; } + _system->UnLock(true); return true; } /*}}}*/ -- cgit v1.2.3