Sune Vuorela wrote, on 2009-04-13 20:08:
On 2009-04-13, Cassiano Leal <cassianoleal@gmail.com> wrote:I might be able to help with that, if it means what I think it does -- getting debian bugs that are not packaging bugs and filing them upstream, is that it?Basically, yes. (or locate them in bugs.kde.org) And then set them to "forwarded" in the debian bug tracking system To mark a debian bug forwarded, send a mail to the control bot with the following content: forwarded nnnnn http://bugs.kde.org/show_bug.cgi?id=mmmmm thanks with nnn being the debian bug number and mmmm being the kde bug numberIf that's the case, I would be more than happy to help, even though I don't have much spare time either.If a handful of people does this with a handful of bugs each week, it adds up quite fast.
So, the big "all of Debian" picture is that packages.debian.org / bugs.debian.org and reportbug need to give instructions on when and how to search for and if necessary report a bug upstream and how to indicate on the Debian bug tracker that the bug has been forwarded upstream?
In the Debian-KDE case, if the instructions for reporting a kde-related bug provided when using reportbug or bugs.debian.org included how to search for a bug report and if necessary report a new bug at bugs.kde.org and how to mark the Debian-KDE bug as forwarded, then it would be easier for the average non-developer Debian user to do this.
If the above suggestions should be reported as a bug (feature request or wish-list item) against bugs.debian.org, please let me know how I go about doing so using reportbug.
Also, I must have missed the e-mail with the graphs, as I have no idea what you're talking about, so if you could point me to them and also to some beginner tips, that would be great.http://users.alioth.debian.org/~pusling-guest/pkg-kde-buggraphs/ < graphs http://pkg-kde.alioth.debian.org/bugs.html /Sune
Arthur.