Chris Cheney ([EMAIL PROTECTED]) wrote on 03:51:51PM 08/03/04: > You filed this bug yourself and don't realize it is an upstream issue? > I assume no one ended up actually forwarding it to upstream yet since it > still appears in KDE 3.2.1, but it definitely is not a packaging issue.
There have been many other packages with this same kind of bug, and in almost all cases it was agreed that is is a packaging issue -- and subsequently fixed in the Debian packaging. What makes you say it is different in this case? Marking it as an upstream bug would imply that you want upstream to fix Debian policy violations, which doesn't seem right to me. Also, *I* did not tag it as upstream, and I don't really agree that it is an upstream issue. Since you tagged it as upstream yourself I assumed you had filed an appropriate bug report on bugs.kde.org, but apparently that is not the case.