Your message dated Sun, 25 Sep 2011 15:47:49 +0000
with message-id <e1r7qvl-000626...@franck.debian.org>
and subject line Bug#626752: fixed in lockfile-progs 0.1.16
has caused the Debian Bug report #626752,
regarding lockfile-progs: lockfile-create --use-pid uses wrong pid
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 this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact ow...@bugs.debian.org
immediately.)
--
626752: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=626752
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Subject: lockfile-progs: lockfile-create --use-pid uses wrong pid
Package: lockfile-progs
Version: 0.1.15
Severity: grave
*** Please type your report below this line ***
From
https://bugs.launchpad.net/ubuntu/+source/lockfile-progs/+bug/676723
It uses L_PID which puts the PID of the lockfile-create process in the
lock.
It needs to use the L_PPID (2 places) to put the process id of the process
executing lockfile-create.
Without this change lockfile-create is useless, as it succeeds every time.
Spectrum of latent problems and consequences is indeed massive,
therefore severity grave.
-- System Information:
Debian Release: 6.0.1
APT prefers stable
APT policy: (500, 'stable')
Architecture: amd64 (x86_64)
Kernel: Linux 2.6.32-5-amd64 (SMP w/4 CPU cores)
Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Versions of packages lockfile-progs depends on:
ii libc6 2.11.2-10 Embedded GNU C Library:
Shared lib
ii liblockfile1 1.08-4 NFS-safe locking library,
includes
lockfile-progs recommends no packages.
lockfile-progs suggests no packages.
-- no debconf information
--- End Message ---
--- Begin Message ---
Source: lockfile-progs
Source-Version: 0.1.16
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.16.dsc
to main/l/lockfile-progs/lockfile-progs_0.1.16.dsc
lockfile-progs_0.1.16.tar.gz
to main/l/lockfile-progs/lockfile-progs_0.1.16.tar.gz
lockfile-progs_0.1.16_amd64.deb
to main/l/lockfile-progs/lockfile-progs_0.1.16_amd64.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 626...@bugs.debian.org,
and the maintainer will reopen the bug report if appropriate.
Debian distribution maintenance software
pp.
Rob Browning <r...@defaultvalue.org> (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 ftpmas...@debian.org)
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
Format: 1.8
Date: Sun, 21 Aug 2011 18:54:27 -0500
Source: lockfile-progs
Binary: lockfile-progs
Architecture: source amd64
Version: 0.1.16
Distribution: unstable
Urgency: low
Maintainer: Rob Browning <r...@defaultvalue.org>
Changed-By: Rob Browning <r...@defaultvalue.org>
Description:
lockfile-progs - Programs for locking and unlocking files and mailboxes
Closes: 625384 626752
Changes:
lockfile-progs (0.1.16) unstable; urgency=low
.
* Remove unused rc variable in chk() to silence gcc warning.
Thanks to Matthias Klose <d...@debian.org> for the report, and thanks
to Aurelien Jarno <aurel...@aurel32.net> for the 0.1.15.1 NMU.
(Closes: #625384)
* Use L_PID rather than L_PPID when appropriate. In cases where
lockfile_create() and lockfile_check() were being called with L_PID,
use L_PPID to capture the parent's PID. Capturing the PID of the
lockfile-create or lockfile-check process made no sense. Thanks to
Zrin Žiborski <zrin+launch...@ziborski.net> for the report, Larry
Diegel for the patch, and Sebastian Siewior <sebast...@breakpoint.cc>
for the suggestion to update the documentation. (Closes: #626752)
Checksums-Sha1:
6d8f36ebb84500b32b168c3a114ea8ad8c395b74 754 lockfile-progs_0.1.16.dsc
5624cefcf7ef5bca87544b7d7571fa33d8596bdc 155901 lockfile-progs_0.1.16.tar.gz
422ae1f69afdcbc7ea3ca1ed9c6879e750adfe4b 10752 lockfile-progs_0.1.16_amd64.deb
Checksums-Sha256:
02694672320d62ffdaad2e065848f09425eb2588071fd82446204a9095910f49 754
lockfile-progs_0.1.16.dsc
f95132d632687af971da830497f06257fa86aedbc4b76874456652f06a0a8a69 155901
lockfile-progs_0.1.16.tar.gz
cd178970a8c0f19f9d50c2c4cf9b7e865c3238abfbb6c51fe679678adaf40090 10752
lockfile-progs_0.1.16_amd64.deb
Files:
7dd8ccb954ee1ad2b75cb936b9523aa9 754 misc optional lockfile-progs_0.1.16.dsc
a7f11bb91e0aad09a7b1f37ee99357be 155901 misc optional
lockfile-progs_0.1.16.tar.gz
d7f3daa309f79010db9fb4650e23010e 10752 misc optional
lockfile-progs_0.1.16_amd64.deb
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.11 (GNU/Linux)
iEYEARECAAYFAk5/SZgACgkQJcjTd4x+c6Q+aACgqsOsB/vaSobpJXwqD7wijaui
a0AAoKctvr+SqvZ+lgAmRvWEt3Vj4LtC
=1/3a
-----END PGP SIGNATURE-----
--- End Message ---
