Your message dated Mon, 16 Oct 2006 22:33:33 -0700
with message-id <[EMAIL PROTECTED]>
and subject line Bug#393574: heartbeat-2: mknod in maintainer script
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: heartbeat-2
Version: 2.0.7-1
Severity: serious
Justification: Policy 10.6
Maintainer scripts should not create device files directly. They should
call makedev instead. Refer to Policy Manual, section 10.6 for details.
-- System Information:
Debian Release: testing/unstable
APT prefers unstable
APT policy: (500, 'unstable')
Architecture: i386 (x86_64)
Shell: /bin/sh linked to /bin/bash
Kernel: Linux 2.6.15-1-amd64-k8-smp
Locale: LANG=fr_FR.UTF-8, LC_CTYPE=fr_FR.UTF-8 (charmap=UTF-8) (ignored: LC_ALL
set to fr_FR.UTF-8)
--- End Message ---
--- Begin Message ---
On Tue, Oct 17, 2006 at 10:13:36AM +0900, Horms wrote:
> On Mon, Oct 16, 2006 at 11:18:06PM +0200, Aurelien Jarno wrote:
> > Package: heartbeat-2
> > Version: 2.0.7-1
> > Severity: serious
> > Justification: Policy 10.6
> > Maintainer scripts should not create device files directly. They should
> > call makedev instead. Refer to Policy Manual, section 10.6 for details.
> The problem is that the call to mknod is not creating a device,
> it is creating a fifo, which is not an operation created by makedev.
> I'm not sure what the best fix, if any, is for this. When I asked
> around a very long time ago, I was advised to just leave the call
> to mknod inside the maintainer script.
Indeed, this is out of scope for makedev. While it may be debatable whether
these fifos should be created under /dev at all, that doesn't fall under
provision 10.6 of policy.
Cheers,
--
Steve Langasek Give me a lever long enough and a Free OS
Debian Developer to set it on, and I can move the world.
[EMAIL PROTECTED] http://www.debian.org/
--- End Message ---
