Package: libgdbm3 Version: 1.8.3-9 Severity: normal The file debian/rules adds "#undef HAVE_FLOCK" to autoconf.h, forcing the use of fcntl for locking instead of flock (the default in gdbm, if available).
IMO this is a bad idea: flock has been supported natively in Linux for 15 years and since kernel 2.6.12 it works even on NFS (but locking on NFS is a mess anyway). More importantly fcntl has really bad semantics. E.g. if different threads in the same process open the same database for reading (thus using a shared lock) at the same time, the lock will be released when the file is first closed by *any* thread, leaving the others with an open database not covered by locks. flock is much saner: in the same situation the lock is only released when *all* threads close the database. So please remove from debian/rules the two lines that modify autoconf.h. -- System Information: Debian Release: squeeze/sid APT prefers testing APT policy: (500, 'testing') Architecture: powerpc (ppc) Kernel: Linux 2.6.32-5-powerpc Locale: LANG=it_IT.utf8, LC_CTYPE=it_IT.utf8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Versions of packages libgdbm3 depends on: ii dpkg 1.15.7.2 Debian package management system ii install-info 4.13a.dfsg.1-5 Manage installed documentation in ii libc6 2.11.2-2 Embedded GNU C Library: Shared lib libgdbm3 recommends no packages. libgdbm3 suggests no packages. -- no debconf information -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
