Paul Johnson skrev:
On Wednesday 14 May 2008 12:10:59 am Ove Kaaven wrote:I'm not sure why you would file a bug on the Debian package if you already filed it upstream, but I guess I've just marked the Debian bug as forwarded there.The casual Debian user of wine may not necessarily be aware of the WineHQ bugzilla; submitting the bug both places ensures people looking for it will find it. Please let me know if this the Wrong Thing; I have one more I'm tracking that I may resub here otherwise.
I like to think that most users (especially those using sid) are clever enough to realize that Wine has an upstream, and that they should look to them for answers (unless the issue is clearly Debian-specific).
In the event some users don't, it's always possible for us to search upstream's BTS and forward reports to an existing (or new) upstream bug ourselves (though that doesn't always happen in a timely fashion, admittedly). Anyway, this only fills Debian's BTS on demand (i.e., only when proven useful), as opposed to trying to proactively replicate upstream's BTS to Debian's.
You can still submit your upstream bugs to Debian if you think it's a good idea, but if you do so, I'd appreciate it if you also marked the bugs as forwarded yourself, it'd lessen our workload somewhat.
--- System information. ---Actually, could you say which bug-reporting tool generated this? It doesn't seem to honor /usr/share/bug/wine/control (formatted as specified by reportbug docs). Doesn't make much difference in this particular case, but it'd be nice to fix for bug reports in the future...reportbug-ng
Thanks. Reviewing reportbug-ng bug #422085, I think the best course of action is to recommend users *not* use reportbug-ng unless that bug is fixed.