Package: cdrecord Version: 4:2.01+01a01-2 Severity: normal
(It would be nice to CC this bug to k3b, I do not know how to do this) For some time I had situation like this: whenever I upgraded cdrecord to new version, k3b started complaining about permissions to cdrecord executable and insisted on starting k3bsetup to correct those permissions. I did it and ... at next upgrade needed to do it again. After last change it was even worse as k3bsetup failed to correct all the permissions in the expected manner and I had to do it manually. It would be nice if cdrecord and k3b maintainers could somehow agree to some common denominator and arrange the way both packages work so that the user can configure it correctly and keep configured between upgrades. I imagine best solution so: - cdrecord has some config question about setting permissions in the k3b-compatible manner (exact details to be discussed with k3b maintainer) - k3b package no longer contains k3bsetup program, instead of spawning it it shows dialogbox telling that one needs to install or reconfigure cdrecord and set such-and-such config option in such-and-such way (of course finding common solution for all CD-writing applications utilizing cdrecord would be even better) -- System Information: Debian Release: 3.1 APT prefers testing APT policy: (500, 'testing') Architecture: i386 (i686) Kernel: Linux 2.4.20-ck2 Locale: LANG=pl_PL, LC_CTYPE=pl_PL (charmap=ISO-8859-2) Versions of packages cdrecord depends on: ii debconf 1.4.30.11 Debian configuration management sy ii libc6 2.3.2.ds1-20 GNU C Library: Shared libraries an ii makedev 2.3.1-75 Creates device files in /dev -- debconf information: cdrecord/MAKEDEVNEW: true cdrecord/do_it_yourself: * cdrecord/SUID_bit: true -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
