Your message dated Thu, 13 Oct 2022 23:24:57 +0200 with message-id <[email protected]> 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 depends hard on working F_SETLK fcntl 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 [email protected] immediately.) -- 134591: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=134591 Debian Bug Tracking System Contact [email protected] with problems
--- Begin Message ---Package: dpkg Version: 1.9.21 dpkg refuses to operate ("unable to lock dpkg status database"), if the F_SETLK fcntl doesn't work on the filesystem where /var/lib/dpkg/lock is located. That's bad because it's not easy to get F_SETLK to work on NFS. That's especially hard if you're trying to do a Debian installation in a tight environment, where you'd rather have no locking at all than having dpkg just say "No!". I ran into this when trying to install Debian from woody_netinst-20020416-powerpc.iso. The installer said "Failure trying to run: chroot /target dpkg --force-depends --install /var/cache/apt/archives/base-files_3.0.2_powerpc.deb /var/cache/apt/archives/base-passwd_3.4.1_powerpc.deb" and on that other console it showed "dpkg: unable to lock dpkg status database: No locks available". It would be nice if the user could at least work around this problem from within the shell provided on the installation CD. I don't currently see such a workaround, but any one of the following changes to dpkg would make it possible: o Use /var/lib/dpkg/lock-dir/lock instead of /var/lib/dpkg/lock as the lock file. (workaround uses ramdisk) o Use /dpkg-lock-dir/lock as the lock file if /dpkg-lock-dir exists. (workaround uses ramdisk) o Don't care about locking if /dpkg-dont-lock exists. (My favorite!) o Fall back to some other locking mechanism (?) if F_SETLK is unavailable. (Would be best, but needs some work.)
--- 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 ---
