Date: Tue, 5 Aug 2014 12:44:58 +0200 From: Carlos Jacobo Puga Medina <cpm@fbsd.es> To: Baptiste Daroussin <bapt@FreeBSD.org> 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: <20140805124458.e5971ddcd52299721bc6176a@fbsd.es> In-Reply-To: <20140805062243.GJ75980@ivaldir.etoilebsd.net> References: <20140804214349.8d8d01cb01c8d7f2894adba1@fbsd.es> <CAG=rPVcPVWXB=AgqBf8R_AB9HF9SKJhw%2B6EzfBhuQaEDTb2vfw@mail.gmail.com> <20140805062243.GJ75980@ivaldir.etoilebsd.net>
next in thread | previous in thread | raw e-mail | index | archive | help
On Tue, 5 Aug 2014 08:22:45 +0200 Baptiste Daroussin <bapt@FreeBSD.org> wrote: Hello, > On Mon, Aug 04, 2014 at 07:28:26PM -0700, Craig Rodrigues wrote: > > 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? I typed 'pkg_libchk -qo > /tmp/rebuild_ports.txt` but it fails running 'pkg_libchk` as well. > > > > > > > > > > > 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. > > > This will be available in 1.3.5 Thanks to both of you. It's good to know it :) > > regards, > Bapt Best regards, -- Carlos Jacobo Puga Medina <cpm@fbsd.es>
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20140805124458.e5971ddcd52299721bc6176a>