Bug#410653: kqemu-common: Creates /dev/kqemu

2007-02-12 Thread Sam Morris
Package: kqemu-common Version: 1.3.0~pre11-1 Severity: serious Justification: Policy 10.6 -BEGIN PGP SIGNED MESSAGE- Hash: SHA1 The package creates /dev/kqemu in its postinst. According to policy it must instead create the device via the MAKEDEV script. Also, on udev-using systems, the

Bug#410653: kqemu-common: Creates /dev/kqemu

2007-02-12 Thread Steve Langasek
severity 410653 important thanks On Mon, Feb 12, 2007 at 11:19:34AM +, Sam Morris wrote: The package creates /dev/kqemu in its postinst. According to policy it must instead create the device via the MAKEDEV script. This isn't RC in the case of device nodes that MAKEDEV doesn't know about.

Bug#410653: kqemu-common: Creates /dev/kqemu

2007-02-12 Thread Daniel Baumann
severity 410653 normal forcemerge 410653 410294 thanks Sam Morris wrote: The package creates /dev/kqemu in its postinst. According to policy it must instead create the device via the MAKEDEV script. again, policy sais *iff* MAKEDEV knows about the device, MAKEDEV must be used. otherwise it's

Bug#410653: kqemu-common: Creates /dev/kqemu

2007-02-12 Thread Sam Morris
again, policy sais *iff* MAKEDEV knows about the device, MAKEDEV must be used. otherwise it's fine to not use it in the meanwhile it's beeing requested for inclusion. Ok, but policy 3.7.2.2 does not say that. It says only that If a package needs any special device files that are not included

Bug#410653: kqemu-common: Creates /dev/kqemu

2007-02-12 Thread Daniel Baumann
Sam Morris wrote: Ok, but policy 3.7.2.2 does not say that. It says only that If a package needs any special device files that are not included in the base system, it must call MAKEDEV in the postinst script, after notifying the user[60] that is, according to vorlon, how it is interpreted