Your message dated Sat, 25 Aug 2007 00:47:03 +0000 with message-id <[EMAIL PROTECTED]> and subject line Bug#416355: fixed in lockfile-progs 0.1.11 has caused the attached Bug report 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 I am talking about this indicates a serious mail system misconfiguration somewhere. Please contact me immediately.) Debian bug tracking system administrator (administrator, Debian Bugs database)
--- Begin Message ---Package: lockfile-progs Version: 0.1.10 the program lockfile-create automatically adds the .lock extension to the supplied filename. but it does not talk about that in its manpage. the C function lockfile_create does NOT add a .lock extension. (the program dotlockfile does NOT add .lock extension and even explicitly sais this in its manpage.) I had bad experiences which made me find this bug: i wrote a C program which locks a directory using a lockfile. in order to be consistent i wanted to use some library and found liblockfile. then i wrote a shellscript which should interact with the C-program. it must also lock the directory with the same lockfile of course. so i found lockfile-progs and expected it to have the same behaviour as the c function it uses. and bang there was the problem: lockfile_create("foobar",10,0); -> creates "foobar" lockfile-create foobar -> creates "foobar.lock"
--- End Message ---
--- Begin Message ---Source: lockfile-progs Source-Version: 0.1.11 We believe that the bug you reported is fixed in the latest version of lockfile-progs, which is due to be installed in the Debian FTP archive: lockfile-progs_0.1.11.dsc to pool/main/l/lockfile-progs/lockfile-progs_0.1.11.dsc lockfile-progs_0.1.11.tar.gz to pool/main/l/lockfile-progs/lockfile-progs_0.1.11.tar.gz lockfile-progs_0.1.11_i386.deb to pool/main/l/lockfile-progs/lockfile-progs_0.1.11_i386.deb A summary of the changes between this version and the previous one is attached. Thank you for reporting the bug, which will now be closed. If you have further comments please address them to [EMAIL PROTECTED], and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Rob Browning <[EMAIL PROTECTED]> (supplier of updated lockfile-progs package) (This message was generated automatically at their request; if you believe that there is a problem with it please contact the archive administrators by mailing [EMAIL PROTECTED]) -----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Format: 1.7 Date: Fri, 24 Aug 2007 17:35:23 -0700 Source: lockfile-progs Binary: lockfile-progs Architecture: source i386 Version: 0.1.11 Distribution: unstable Urgency: low Maintainer: Rob Browning <[EMAIL PROTECTED]> Changed-By: Rob Browning <[EMAIL PROTECTED]> Description: lockfile-progs - Programs for locking and unlocking files and mailboxes Closes: 161685 244314 272539 360474 382730 416355 437491 Changes: lockfile-progs (0.1.11) unstable; urgency=low . * Add --quiet and --verbose options. (closes: #272539) * Use hard links for duplicate binaries. (closes: #382730) * Respect DEB_BUILD_OPTIONS nostrip. (closes: #437491) * Fix manpage to reflect changes to liblockfile --retry. (closes: #161685, #244314, #360474) * Add support for --lock-name (-l). (closes: #416355) Files: bf75f415f4063a924121e4d0901a6973 510 misc optional lockfile-progs_0.1.11.dsc 763da639a5644754728b5e27ef4f76f7 61736 misc optional lockfile-progs_0.1.11.tar.gz 97f682c08ec9ad69bba7d34bf2682776 7764 misc optional lockfile-progs_0.1.11_i386.deb -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.6 (GNU/Linux) iD8DBQFGz3p8JcjTd4x+c6QRAhKCAJ4pMSy9uOGHBXmRV4mlnVwI7vw+egCfTJyB PpBzF4CIG39YIgJq1DM+2qI= =5C8n -----END PGP SIGNATURE-----
--- End Message ---
