On Sat, 24 Jun 2006 09:33:43 -0700 [EMAIL PROTECTED] (Debian Bug Tracking System) wrote:
> This bug has been closed by the upstream developer. Please comment > directly on his bug tracker if you would still like this issue > resolved: > > https://bugs.kde.org/show_bug.cgi?id=121633 Unfortunately there's no explanation for the closing at that page. I notice a URL there with a label: View Bug Activity https://bugs.kde.org/show_activity.cgi?id=121633 Which only leads to a blank page that ungrammatically advises: Log in first for seeing more details. Do you believe a Debian user should have to "log in" upstream just to read a bug history? I am not a KDE developer and have no account there, so in effect you're asking that users sign up for a private forum they might have no other reason to join. As a Debian maintainer, dealing with upstream is one of your tasks. You're never obliged to close a bug because upstream does, if you believe them to be wrong. Whereas if you believe them to be correct, your own explanation for closing should be posted on an open forum, because Debian's BTS is by design an open and public forum. Merely saying that you agree or refuse to contradict some unspecified reason from a private upstream forum is not enough. 3. We will not hide problems We will keep our entire bug report database open for public view at all times. Reports that people file online will promptly become visible to others. - Debian Social Contract, v1.1 I'm also surprised that on 2/9/2006 while writing to upstream you quoted extensively a message I wrote, introducing it with a paraphrase without clearly marking the quote -- making it seem as though you were the author of it. I've nothing against quoting of course, but it ought to be correctly attributed. In conclusion, at least one of your users would very much like to read a publicly posted reason for closing what seems like an undeniable bug. -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
