Rather than depending on or recommending libfile-fcntllock-perl, I think dpkg-dev can now just unconditionally use flock. According to "man 2 flock": > In Linux kernels up to 2.6.11, flock() does not lock files over NFS (i.e., the > scope of locks was limited to the local system). Instead, one could use > fcntl(2) byte-range locking, which does work over NFS, given a sufficiently > recent version of Linux and a server which supports locking. Since Linux > 2.6.12, NFS clients support flock() locks by emulating them as byte-range > locks > on the entire file. This means that fcntl(2) and flock() locks do interact > with > one another over NFS.
So, on 2.6.12 and newer, flock on NFS will transparently uses fcntl locks. No supported version of Debian runs on a kernel older than 2.6.12. Given that, I would suggest dropping the Recommends and the optional use of File::FcntlLock entirely. - Josh Triplett
