On Mon, Sep 04, 2006 at 12:56:03PM -0700, [EMAIL PROTECTED] wrote: > What about cdrdao? It does not allow for setting suid through debconf. > Perhaps > I should submit a whishlist bug against cdrdao?
We can probably remove that warning entirely. I don't think it's needed at all. > There may be quite a few people who like k3bsetup, and who will want it back. Yes, it seems like it, so I'll leave it in for now I think. But I want to "debianize" the warning messages that K3b emits. > There are some other warning messages that k3b gives which are misleading. > For > example k3b diagnostics suggests installing package cdrtools, but there is no > such binary package in debian. That may lead people to download and install > cdrtools from upstream sources... I know it sounds silly, but it happens a > lot, and it usually ends up with a broken system. Should I submit separate > bug reports for these? I think that I'm going to close this bug when I apply Dirk's patch for the dpkg-statoverride calls. However, you are right, it would be a good idea to submit a new bug report (wishlist). Feel free to open a new bug that suggests making the warning messages more relevant for a Debian system. I can see the following: - removing the cdrdao warning - talking about "dpkg-reconfigure wodim" to make cdrecord SUID in case of problems, but also suggesting that the user be added to the cdrom group - any other messages that don't make sense on Debian Francois -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
