On Wed, Mar 23, 2005 at 09:02:41AM +1100, [EMAIL PROTECTED] wrote: > Justin, > > I am confused. You wrote: > > >> When do you expect it to be forwarded upstream? > > Donno; that's up to the maintainer. If you like, you can do it > > yourself. You should Cc: [EMAIL PROTECTED] in your message, > > which will get your message into the bts and also mark the bug as > > "forwarded" to whoever is in the To: field. > > Looking in http://bugs.debian.org/295435 it says > > Maintainer for sylpheed is Ricardo Mones <[EMAIL PROTECTED]> ... > > which agrees with you saying that you are not the maintainer. Right:)
> You suggest I do something "funny" to ensure the maintainer gets the > message? Or, would that forward the bug upstream (all of it, or just > the message I am sending), bypassing the lazy maintainer? No; people have different interpretations about what the maintainer of a package is supposed to do, and what they are expected to do. Some maintainers dislike when users report upstream bugs to the debian BTS, because then they have to forward the bugs upstream, and fumble with a second BTS. Or they simply don't do that, and the bugs just bitrot. Other maintainers don't have so many bugs to worry about, and don't mind forwarding the bugs. Since I can confirm that the problem is the "upstream" tarball, and not the Debian packaging, I suggested that you might forward the bug yourself. (I'm assuming that Ricardo won't mind; correct me if I'm wrong. Most people aren't protective of their bugs, but conventionally only the submitter or the maintainer actually closes a bug). > If you are not the maintainer, how did you get to "tag" this bug: > could I have done so myself? Yup. http://bugs.debian.org/ tells you all about it. The BTS is opened for you to submit, view, or even manipulate bugs. Cheers, Justin -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
