Home | Back
liblockfile (1.08)

  * When not writing a pid into the lockfile, write "0\n" as
    placeholder instead of "0\0" (bug reported by Rob Browning
    <rlb@defaultvalue.org>)
  * lockfile_check() did the following:
      - open lockfile
      - read from it
      - stat file and get atime as 'now'
    this gets the 'now' time from the filesystem so comparisations
    to mtime work even if the clock of the remote file server is off.
    However this doesn't work with noatime / relatime, so now we stat
    the lockfile both before and after the read and use atime only
    if it differs before and after.
  * Copy Changelog from debian/changelog now that the package
    isn't native anymore since 1.07

-- Miquel van Smoorenburg <miquels@cistron.nl>  Thu, 24 Jul 2008 22:40:34 +0200

liblockfile (1.07-1) unstable; urgency=low

  * Fixed "liblockfile1: option -u is duplicated". Closes: #416271

-- Anibal Monsalve Salazar <anibal@debian.org>  Sat, 05 Apr 2008 12:14:10 +1000

liblockfile (1.06.2) unstable; urgency=low

  * Non-maintainer upload.
  * Rename eaccess() to eaccess_write() as eaccess is now a glibc function.
    Patch by Colin Watson. Closes: #392779.

-- Aurelien Jarno <aurel32@debian.org>  Sun, 03 Jun 2007 19:28:33 +0200

liblockfile (1.06.1) unstable; urgency=low

  * Non-maintainer upload.
  * Remove postinst and prerm scripts, completing the /usr/doc tarnsition.
    Closes: #322790

-- Joey Hess <joeyh@debian.org>  Tue, 10 Jan 2006 01:21:31 -0500

liblockfile (1.06) unstable; urgency=low

  * Fix manpage - fd = open("/var/mail/USER.lock") should be
    fd = open("/var/mail/USER");
  * Remove extraneous free() from lockfile.c (closes: #217740)
  * If the existing lockfile is not valid, the first try isn't really
    valid either - in that case, even if we want to try locking just
    once, try once more.  (closes: #217741)

-- Miquel van Smoorenburg <miquels@cistron.nl>  Fri,  4 Jun 2004 17:16:04 +0200

liblockfile (1.05) unstable; urgency=low

  * Fix "does not give a valid preprocessing token" cpp problem
    (closes: #194823)

-- Miquel van Smoorenburg <miquels@cistron.nl>  Mon,  2 Jun 2003 14:27:58 +0200

liblockfile (1.04) unstable; urgency=low

  * Dynamically allocate filename memory, do not use
    MAXPATHLEN sized static buffers (closes: #144129, #105973)
  * Make the '-c' option of dotlockfile(1) actually work (closes: #103998)
  * Dotlockfile '-r' arg error checking
  * Note in manpages that unlocking a non-existant file is not an error.
  * Note in dotlockfile manpage that the lockfile_create manpage
    is in the liblockfile-dev package.
  * Update COPYRIGHT file (closes: #178200)
  * Don't sleep for 5 seconds when we removed an invalid lockfile
    (closes: #131316)
  * This upload will force a rebuild with current binutils (closes: #176340)
  * Add symlinks for manpages (closes: #99546)
  * Add static library liblockfile.a to liblockfile-dev (closes: #183817)
  * Actually handle 'retries' as number of *re*tries everywhere,
    not the number of tries.
  * Document that the default number of retries in dotlockfile is 5.
  * Add a '-t' (touchlock) option to dotlockfile (closes: #41791)

-- Miquel van Smoorenburg <miquels@cistron.nl>  Thu, 15 May 2003 16:29:32 +0200

liblockfile (1.03) unstable; urgency=low

  * Some more manpage updates
  * Set priority for liblockfile1 to "important" (closes: #92551)

-- Miquel van Smoorenburg <miquels@cistron.nl>  Fri,  6 Apr 2001 09:53:32 +0200

liblockfile (1.02) unstable; urgency=low

  * Maintainer upload (closes: #87488, #80753, #87670, #48886, #50564, #57890, #80601)
  * Added section to manpages that explains that you need to flush
    the actual file being locked after locking (closes: #43491)

-- Miquel van Smoorenburg <miquels@cistron.nl>  Thu, 29 Mar 2001 00:55:55 +0200

liblockfile (1.01.2) unstable; urgency=low

  * Non-Maintainer Upload for Bug Squashing Party.
  * Fix typo in postrm, closes: #87670.
  * Removed *~ from sources.

-- Jordi Mallach <jordi@debian.org>  Sat, 17 Mar 2001 05:09:54 +0100

liblockfile (1.01.1) unstable; urgency=low

  * NMU for bugsquashing day.
  * Updated man pages and usr/doc dir to FHS, Closes: #80753 (serious)
  * Only run ldconfig in postinst if the package is being configured.
  * Run ldconfig in the postrm on removal.
  * Fixed shlibs file perms, Closes: #50564, #57890
  * Fixed descriptions, Closes: #80601
  * Fixed man page typo, Closes: #48886
  * Lintian clean except the warning about the setgid binary.

-- Joey Hess <joeyh@debian.org>  Sat, 24 Feb 2001 13:55:27 -0800

liblockfile (1.01) unstable; urgency=low

  * Fix "clean" target in debian/rules
  * Fixes bugs:
    #39813: Liblockfile failes to build because of missing Makefile
    #39864: liblockfile_1.0(unstable): can't clean already empty tree

-- Miquel van Smoorenburg <miquels@cistron.nl>  Mon, 21 Jun 1999 19:47:17 +0200

liblockfile (1.0) unstable; urgency=low

  * Added autoconf to the distribution so that this package might
    be used outside Debian and even outside Linux.
  * New soname for liblockfile; API change.
  * Included command-line utility "dotlockfile" (setgid mail) and manpage
  * library can call "dotlockfile" to do the actual locking - mailprograms
    do not need to be setgid mail anymore!
  * Doesn't include libnfslock anymore
  * Fixes: #29572: liblockfile0 bad packaging

-- Miquel van Smoorenburg <miquels@cistron.nl>  Sat,  5 Jun 1999 17:19:30 +0200

liblockfile (0.1-6) frozen unstable; urgency=high

  * Fixed libnfslock to work together with mutt's mutt_dotlock.
    This has high urgency because otherwise mutt won't be able
    to lock your mailbox 95% of the time.

-- Miquel van Smoorenburg <miquels@cistron.nl>  Wed,  2 Dec 1998 17:39:54 +0100

liblockfile (0.1-5) unstable; urgency=low

  * Added L_MANLOCK define for compatibility , it's not actually used.
  * Fixes bugs:
    #21925 liblockfile man page is inaccurate
    #27275 liblockfile0: wishlist "user" argument for mailunlock and touchlock.

-- Miquel van Smoorenburg <miquels@cistron.nl>  Mon,  5 Oct 1998 12:35:42 +0200

liblockfile (0.1-4) unstable; urgency=low

  * Fixes:
    #13974: liblockfile-dev: maillock(3) mentions other manpages, that are not
    #18521: liblockfile-dev should not include /usr/lib/liblockfile.so
    #19042: liblockfile-dev: Overlap with liblockfile0
    #18527: liblockfile0: liblockfile0 include .so link in liblockfile-dev
    #19041: liblockfile0: Overlap with liblockfle-dev and no conflict
    #19108: liblockfile0 has incorrect shlibs listed
    #18607: libnfslock: postinst and prerm scripts fail if ld.so.preload only
    #18913: libnfslock: package description

-- Miquel van Smoorenburg <miquels@cistron.nl>  Sun,  8 Mar 1998 22:41:49 +0100

liblockfile (0.1-3) unstable; urgency=low

  * Added version in name for nfslock.so (now nfslock.so.0.1)
  * Added shlibs file for nfslock
  * Add missing symlinks
    Fixes:
    #14413: /usr/doc/$(PACKAGE)/copyright should not be compressed
    #17693: liblockfile0 has executabnle changelog.gz
    #16489: liblockfile0 lacks dependency information
    #14155: lockfile_create could ignore some errors
    #14423: /usr/doc/$(PACKAGE)/copyright should not be compressed
    #15220: liblockfile-dev changelog is executable
    #14412: /usr/doc/$(PACKAGE)/copyright should not be compressed

-- Miquel van Smoorenburg <miquels@cistron.nl>  Thu, 19 Feb 1998 23:15:01 +0100

liblockfile (0.1-2) unstable; urgency=low

  * Compiled with libc6 and with -lc
  * Compile with -D_REENTRANT and -D_GNU_SOURCE
  * Apart from returning the L_XXX values, also set errno to something
    resonable.
  * Reckognize common NFS lockfiles from mailx

-- Miquel van Smoorenburg <miquels@cistron.nl>  Wed, 24 Sep 1997 12:52:44 +0200

liblockfile (0.1-1) unstable; urgency=low

  * First Debian release.

-- Miquel van Smoorenburg <miquels@cistron.nl>  Sun, 6 Jul 1997 16:04:55 +0200