Your message dated Sat, 25 Aug 2007 00:47:03 +0000
with message-id <[EMAIL PROTECTED]>
and subject line Bug#161685: 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.9
Severity: minor
I think that the --retry option for lockfile-create is misleading.
lockfile-progs(1) reads:
For both of the locking commands (mail-lock and lockfile-create), the
--retry argument specifies (as an integer) the maximum number of
times to retry locking the file before giving up if attempts
are failing.
So the retry option is used to specify how many retries to use ``if
attempts are failing''. So, if I can create a lockfile without errors,
then I should be able to specify ``--retry 0'' to attempt creation
exactly once (in the spirit of lockfile-touch --oneshot)
k,
admin ~% ls -l lockfile.lock
ls: lockfile.lock: No such file or directory
admin ~% touch lockfile.lock
admin ~% ls -l lockfile.lock
-rw------- 1 mcarr mcarr 0 2002-09-20 13:48 lockfile.lock
admin ~% rm lockfile.lock
admin ~% ls -l lockfile.lock
ls: lockfile.lock: No such file or directory
admin ~% lockfile-create --retry 0 lockfile
lockfile creation failed
admin ~% lockfile-create --retry 1 lockfile
admin ~% ls -l lockfile.lock
-rw-r--r-- 1 mcarr mcarr 2 2002-09-20 13:53 lockfile.lock
I touched the file just to indicate that I can, in fact, create a file.
I'm not looking at a permissions issue or anything like that;
lockfile-create isn't making any attempt to lock the file.
I believe that this behaviour is in conflict with the manpage. Either
the behaviour should be adjusted or the manpage corrected.
-- System Information:
Debian Release: testing/unstable
Architecture: i386
Kernel: Linux commserv 2.4.18-686 #1 Sun Apr 14 11:32:47 EST 2002 i686
Locale: LANG=C, LC_CTYPE=C
Versions of packages lockfile-progs depends on:
ii libc6 2.2.5-14.2 GNU C Library: Shared libraries an
ii liblockfile1 1.03 NFS-safe locking library, includes
-- no debconf information
--- 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 ---
