Dear All,
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.
If anyone has any alternative/better suggestions for how to do this, then please let me know.
Thanks,
Alex
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 ;)
Hi suv,
I think I'll have a bit of spare time tomorrow, if you'd like me to start forwarding the relevant debian reports. Would it be worth tagging them with something like "debbugs-needing-review" so we can keep track of which ones have been looked over?
AV
On 15 January 2011 13:39, ~suv <suv-sf@...58...> wrote:
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 ;)
On 19/1/11 11:58, Alex Valavanis wrote:
I think I'll have a bit of spare time tomorrow, if you'd like me to start forwarding the relevant debian reports. Would it be worth tagging them with something like "debbugs-needing-review" so we can keep track of which ones have been looked over?
Using a temporary tag in Inkscape's bug tracker for the forwarded reports seems a good idea to me.
Could you start with the most recent reports (against 0.47 or 0.48) which haven't been forwarded yet?
AFAICT there are several very old ones (reported against 0.45 or even earlier) which are likely to be no longer relevant in current versions (0.47 and 0.48). These old reports IMHO only make sense to be forwarded if they are confirmed with the current version, too.
As an example: in older Inkscape versions PS/EPS import was calling pstoedit, but since 0.47 Inkscape uses ps2pdf from Ghostscript instead. Old Debian bug reports about failing EPS import due to problems with pstoedit don't have to forwarded upstream IMHO, but could be closed in the debian tracker instead.
I start working on a list with this type of reports and will add it here (hopefully later today).
~suv
OK, I'll make a start on the bugs reported against 0.47/0.48.
On 20 January 2011 07:52, ~suv <suv-sf@...58...> wrote:
On 19/1/11 11:58, Alex Valavanis wrote:
I think I'll have a bit of spare time tomorrow, if you'd like me to start forwarding the relevant debian reports. Would it be worth tagging them with something like "debbugs-needing-review" so we can keep track of which ones have been looked over?
Using a temporary tag in Inkscape's bug tracker for the forwarded reports seems a good idea to me.
Could you start with the most recent reports (against 0.47 or 0.48) which haven't been forwarded yet?
AFAICT there are several very old ones (reported against 0.45 or even earlier) which are likely to be no longer relevant in current versions (0.47 and 0.48). These old reports IMHO only make sense to be forwarded if they are confirmed with the current version, too.
As an example: in older Inkscape versions PS/EPS import was calling pstoedit, but since 0.47 Inkscape uses ps2pdf from Ghostscript instead. Old Debian bug reports about failing EPS import due to problems with pstoedit don't have to forwarded upstream IMHO, but could be closed in the debian tracker instead.
I start working on a list with this type of reports and will add it here (hopefully later today).
~suv
participants (2)
-
Alex Valavanis -
~suv