Your message dated Thu, 13 Oct 2022 23:24:57 +0200
with message-id <y0ickxowl3uex...@thunder.hadrons.org>
and subject line Re: Bug#134591: dpkg: unable to lock dpkg status database: No
locks available
has caused the Debian Bug report #134591,
regarding dpkg: unable to lock dpkg status database: No locks available
to be marked as done.
This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.
(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact ow...@bugs.debian.org
immediately.)
--
134591: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=134591
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: dpkg
Version: 3.0 (woody)
dbootstrap exists with an error value 1 while installing on a root
filesystem type NFS. The mount options are standard "mount
192.168.0.3:/usr/exported /mnt" and the server is FreeBSD 4.0 with kernel
support of NFS v2/3. The installation starts fine and downloads and
extracts all packages, but I believe it is 'dpkg --configure --pending'
since typing this on the prompt reproduces the error. The alt-f4 debug
screen says: dpkg: unable to lock dpkg status database: No locks
available"
--- End Message ---
--- Begin Message ---
On Thu, 2002-10-10 at 17:56:22 +0200, Wichert Akkerman wrote:
> Previously Thomas Hood wrote:
> > W.A.: 149491 was marked wontfix. Is this because these reports
> > are unreasonable wishes, or because there is a solution
> > (for the user to use NFS locking)?
>
> The latter.
Indeed. This is a filesystem requirement to be able to use dpkg on,
documented in
<https://wiki.debian.org/Teams/Dpkg/FAQ#Q:_What_are_the_filesystem_requirements_by_dpkg.3F>.
I'm thus closing this wontfix report.
Thanks,
Guillem
--- End Message ---
