On Mon, Sep 18, 2006 at 07:48:08AM -0700, tony mancill wrote: > This is up to you; I've done it both ways in the past. If the bug is > affects the usability of the package, and it could take a while to fix it, > go ahead and report the bug to the BTS. That will let other users know that > the maintainer is aware of the issue. You may even be able to describe a > workaround in the bug report. If the bug is trivial or purely aesthetic > then the bug report would be less useful. However, it doesn't hurt to file > a bug report, even if the issue is very minor, so if you're in doubt, I > would suggest filing one.
I would have to second what Tony says above. I maintain packages as a Debian developer and as upstream and yes while there is no rule about it Tony's description is a pretty good way of determining what you can do. Another way of looking at it is; would the bug report be useful to users of your package. This could be either because they know it is not just their system, because you have put in a work-around or so that they know Debian/upstream is aware of it. - Craig -- Craig Small GnuPG:1C1B D893 1418 2AF4 45EE 95CB C76C E5AC 12CA DFA5 Eye-Net Consulting http://www.enc.com.au/ MIEE Debian developer csmall at : enc.com.au ieee.org debian.org -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
