On 14/1/11 18:54, Alex Valavanis wrote:
The Inkscape package in Debian is used by several other major linux distributions (e.g. Ubuntu) and hence it represents bugs which potentially affect a very large number of Inkscape users in linux. Its bug tracker is available at:
http://bugs.debian.org/cgi-bin/pkgreport.cgi?package=inkscape
Unfortunately, the Debian tracker is quite out of date, and many of the reports have not been forwarded to the Inkscape tracker on Launchpad. I think it's quite important for Inkscape QA, that the Debian tracker gets back in sync with the upstream project. I have been (slowly) working through the reports, but there's a pretty large backlog and some of the bugs were probably fixed years ago.
Would any of the upstream triagers be interested in helping out with this task? If so, a possible option would be for me to forward all the Debian bugs which relate to the upstream part of the Inkscape package. We could then triage the bugs in Launchpad, and I will update the Debian reports accordingly.
As far as general Inkscape bugs are concerned, I'll try to help as best I can. Linux- or distribution-specific issues (like handling dependencies or installed mime-types) I can't test myself and often I don't know how far it also concerns upstream Inkscape or should be handled by the distribution-specific packaging process.
If anyone has any alternative/better suggestions for how to do this, then please let me know.
I could go through the list (next week), and sort out those for which I already know (or easily can find) an existing report. The rest would probably be best handled by forwarding to launchpad for further triage.
OTOH maybe it would make more sense to just forward all reports concerning upstream Inkscape to launchpad, and triage them there. [1]
~suv
[1] I have to admit that my initial reaction to any kind of announced 'mass-reporting' of bugs tends to be defensive - "oh no, please search for duplicates first" - until rational thinking takes over ;)