Date: Mon, 4 Aug 2014 19:28:26 -0700 From: Craig Rodrigues <rodrigc@freebsd.org> To: Carlos Jacobo Puga Medina <cpm@fbsd.es> Cc: freebsd-pkg@freebsd.org Subject: Re: [BUG?] pkg: Cannot get a read lock on a database, it is locked by another process Message-ID: <CAG=rPVcPVWXB=AgqBf8R_AB9HF9SKJhw%2B6EzfBhuQaEDTb2vfw@mail.gmail.com> In-Reply-To: <20140804214349.8d8d01cb01c8d7f2894adba1@fbsd.es> References: <20140804214349.8d8d01cb01c8d7f2894adba1@fbsd.es>
next in thread | previous in thread | raw e-mail | index | archive | help
On Mon, Aug 4, 2014 at 12:43 PM, Carlos Jacobo Puga Medina <cpm@fbsd.es> wrote: > Hi, > > After upgrade pkg to 1.3.4 I have the same problem with pkg_libchk which it shows while is running: > > pkg: Cannot get a read lock on a database, it is locked by another process What command did you type which caused this problem? > > > Any suggestion is welcome. If you look here: https://github.com/freebsd/pkg/commits/release-1.3 there is a fix for READ_LOCK commit 4d946cf395a51f48bcc1469e21862910dd50797c but that fix went in after pkg 1.3.4 was released. This won't be available until pkg 1.3.5. -- Craig
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?CAG=rPVcPVWXB=AgqBf8R_AB9HF9SKJhw%2B6EzfBhuQaEDTb2vfw>