[note: sent to d-d only] I demand that Luke Kenneth Casson Leighton may or may not have written...
> On Tue, Jan 10, 2006 at 02:04:45PM +0100, Adeodato Sim?? wrote: >> * Matthew Garrett [Tue, 10 Jan 2006 02:50:56 +0000]: [snip] >>> It's the job of either the bug submitter or (more usually) the Debian >>> maintainer to contact upstream to make sure that they're aware of the >>> bug. It is *not* the upstream maintainer's job to examine Debian's bug >>> database. > that distinction isn't made clear: it's only if people think about it that > they will realise that they are supposed to report debian-specific > packaging bugs to the debian bugs database and package-specific bugs to > whatever upstream thingy they can find. _if_ they can find it. Not necessarily. The bug could be due to a Debian-specific change in the package and, for whatever reason, $USER may be unable to determine this - in that case, the best place for the bug report is the Debian BTS. > and even if some people do think, there's lots that won't. Then there are the people who send bug reports upstream anyway, even for distribution-specific problems... [snip] >>> "If you report a bug to Debian and nobody forwards it, we know nothing >>> about it". >> All correct. Thanks, Matthew. I'll just note that the Debian KDE packages >> receive an incredible amount of bug reports, and that we're understaffed >> to forward all of them to KDE upstream. > that's why one of my recommendations was to consider putting, into certain > key very popular packages, a means to either transfer the bug to upstream > (via some mad notional XMLeey are pee cee-ey common API) or to simply put > into reportbug a list of packages for which reporting should be given > special messages: [snip] I can imagine a situation in which, due to a lot of packaging-specific bugs being sent upstream, upstream starts closing bugs, marking them with something like "report via your distribution's BTS" ;-\ > other possibilities: > 1) add into the dpkg thingy an upstream URL where bugs can be reported: > UpstreamBugs: http://bugs.kde.org/enter_bug.cgi (whatever) > if you encounter a bug in kde. > please report it here because otherwise nobody > will fix it, thank you. > . ITYM "... because otherwise your bug report will be ignored". [snip] > this would save maintainers a boat-load of time. Maybe... > 2) against the list of "UpstreamBugs", on bugs.debian.org, email > received automatically notifies the sender of the above info. That /may/ be useful, but it's also another potential black hole, whether the messages are sent to a person ("not enough time") or to a list. And, as we know, lists can easily become SEP generators: just add one 9V battery... :-) [snip] -- | Darren Salt | nr. Ashington, | linux (or ds) at | sarge, | Northumberland | youmustbejoking | RISC OS | Toon Army | demon co uk | Kill all extremists! Live within your income, even if you have to borrow to do so. -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
