Your message dated Tue, 17 Dec 2013 16:03:48 +0000
with message-id <[email protected]>
and subject line Bug#728020: fixed in latd 1.34
has caused the Debian Bug report #728020,
regarding latd: Replace use of lockdev with flock
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 [email protected]
immediately.)
--
728020: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=728020
Debian Bug Tracking System
Contact [email protected] with problems
--- Begin Message ---
Package: latd
Version: 1.33
Severity: normal
Dear maintainer,
I'm writing to you as the maintainer of lockdev (liblockdev1). I've
opened this bug because your package either has a build-depends on
liblockdev1-dev or is building binary packages with a dependency on
liblockdev1.
lockdev implements a library interface around the SYSV-style UUCP
device locks for TTY devices. However, this type of locking is
deprecated and unnecessary, at least on Linux; I'm not sure of the
status on kFreeBSD. The recommended alternative is direct use of
flock(2) on the corresponding device node. This will ensure that
locking will work properly with other programs also locking the device
node, and since the locks are implemented in the kernel, there's no
need for racy creation and deletion of lockfiles with the owner PID,
and no possibility of PID clashes or failure to reclaim lost locks if
the PID is reused. That is to say, the flock(2) interface is
guaranteed to be robust, while lockdev is not. For users not using
the C API (for example scripts), flock(1) from util-linux provides a
wrapper.
I'd like to remove lockdev entirely for jessie, providing that it's
possible to do so without breakage. Likewise I'd also like to convert
packages using UUCP-style locks which don't use lockdev. We currently
have at least three methods of device locking (UUCP-with-lockdev,
UUCP-without-lockdev and direct-flock), all of which have overlapping
or completely orthogonal semantics, which will result in not
respecting the other lock types if used in combination. Hence the
need to reduce this to a single robust locking strategy: just locking
the device directly.
It would be greatly appreciated if you could disable/remove lockdev
support from your package and remove it from the source build-depends
and/or package depends as appropriate, replacing this with flock(2)
calls instead of dev_lock and dev_unlock.
Many thanks,
Roger Leigh
-- System Information:
Debian Release: jessie/sid
APT prefers unstable
APT policy: (550, 'unstable'), (400, 'experimental')
Architecture: amd64 (x86_64)
Kernel: Linux 3.11-1-amd64 (SMP w/8 CPU cores)
Locale: LANG=en_GB.UTF-8, LC_CTYPE=en_GB.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Versions of packages latd depends on:
ii libc6 2.17-93
ii libgcc1 1:4.8.2-1
ii liblockdev1 1.0.3-1.5+b1
ii libstdc++6 4.8.2-1
latd recommends no packages.
latd suggests no packages.
--- End Message ---
--- Begin Message ---
Source: latd
Source-Version: 1.34
We believe that the bug you reported is fixed in the latest version of
latd, which is due to be installed in the Debian FTP archive.
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.
Chrissie Caulfield <[email protected]> (supplier of updated latd 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.8
Date: Tue, 17 Dec 2013 15:21:22 +0000
Source: latd
Binary: latd
Architecture: source i386
Version: 1.34
Distribution: unstable
Urgency: low
Maintainer: Christine Caulfield <[email protected]>
Changed-By: Chrissie Caulfield <[email protected]>
Description:
latd - LAT (Local Area Transport) Daemon
Closes: 728020
Changes:
latd (1.34) unstable; urgency=low
.
* use flock(2) instead of liblockdev
Closes: #728020
Checksums-Sha1:
d7636838bf9fb827ef46b501fd319910fc8da6b8 731 latd_1.34.dsc
412a18f3fef0ce557de007d02a6cc3ca7ee47ad5 443891 latd_1.34.tar.gz
d833c70650902f564fd25c3b72378c2a192656d1 79350 latd_1.34_i386.deb
Checksums-Sha256:
911725ea79ade497658bc129c153fd2c082b60eef3cb7d411fd71e755602a60c 731
latd_1.34.dsc
c73738fa7bd45962a9f0ada39d742809371ad71aa68ca3aac179e25ec1984908 443891
latd_1.34.tar.gz
e00abe47b36c63de6bc486bab6fec3a13eaa8573e2abd0b0c99c513557c816fc 79350
latd_1.34_i386.deb
Files:
db2a7da0a7ad7eff807079d2cd676347 731 net extra latd_1.34.dsc
d647cc943ea2d8aa47aaa1ab2edf8f2d 443891 net extra latd_1.34.tar.gz
fb26cfb1b6e202234ca7d9312e8f4eb4 79350 net extra latd_1.34_i386.deb
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v2.0.22 (GNU/Linux)
iEYEARECAAYFAlKwc7gACgkQhej7/PCycRMbxwCbBUKHY12AWO/ZXeORf+JluUY1
+NIAnj+6xDlPy2GTSJAG8qol6FjVMggX
=H+UP
-----END PGP SIGNATURE-----
--- End Message ---
