Le 20/02/05 à 21:53 Christian Kurz ([EMAIL PROTECTED]) écrivait : > Hi, Hi,
> this bug was reported in Aug 2004. Since then you've made 5 new upstream > releases. One of those releases even closes bugreports, without proper > changelog entries. May I suggest that instead of continuing to > release new upstream versions as debian package, you work on the buglist > of k3b? Most of k3b bugs in debian aren't related to the package therefore I can do nothing for them. > At least this bug fix is very easy to fix with a simple entry in > debian/control. And while you are at it, k3b claims to use crdao to > write cds: No, it isn't. Have a look to debian policy : http://www.debian.org/doc/debian-policy/ch-archive.html "Packages must not depend on packages with lower priority values (excluding build-time dependencies). In order to ensure this, the priorities of one or more packages may need to be adjusted." [EMAIL PROTECTED] ~/debian/amavis-stats] $apt-cache show k3b |grep ^Priority Priority: optional [EMAIL PROTECTED] ~/debian/amavis-stats] $apt-cache show cdrdao |grep ^Priority Priority: extra > Unable to find cdrdao executable > k3b uses cdrdao to actually write CDs. > Solution: Install the cdrdao package. I'am sorry about that. The best way would be to ask for a change of cdrdao priority. > Why is then k3b depending on cdrecord, which can also be used to write > CDs? If both are used, then this should be documented better and this > warning changed. If cdrecord isn't used then please remove the > dependency. Or if it's needed, then include some explanation why. > Thanks! $apt-cache show cdrecord |grep ^Priority Priority: optional Thanks. -- Jean-Michel Kelbert
signature.asc
Description: Digital signature
