Re: Improving imagemagick.bug-presubj
Justin B Rye wrote:
> This would make it:
Looking at this again, I'm not convinced it works as a series of
"steps" (even with item 1 moved back to the end). Two of the steps
are if-clauses; the rest of them are parts of the process of
recreating the bug under controlled conditions, but it never actually
says anything about this being the objective! Maybe you want
something more like this:
Debugging imagemagick can be difficult, so you can help by following
these guidelines.
First you should verify that the problem is in imagemagick and not the
graphicksmagick compatibility package. Run "convert -version" in a
terminal; if you see "GraphicsMagick" in the first line of output, please
make your report against the graphicsmagick package.
Otherwise, please provide a test-case that can reproduce the bug:
1. Install debugging packages. As root, run
"apt-get install --install-suggests imagemagick-dbg".
2. Repeat the command line that led to the bug. To ensure you are using
the imagemagick versions, replace convert, display, identify, or
mogrify with convert.im6, display.im6, identify.im6, or mogrify.im6 in
your test-case.
3. If imagemagick dumps core, please attach a backtrace - see
"http://wiki.debian.org/HowToGetABacktrace";.
Document the exact command line used, and attach the input files to your
bug report. If they are in SVG format, please also run the commands
"rsvg-convert yourinput.svg > rsvg.png" (from the package librsvg2-bin)
and "inkscape yourinput.svg --export-png=inkscape.png" (from the package
inkscape). Include the PNG output files in your bug report.
--
JBR with qualifications in linguistics, experience as a Debian
sysadmin, and probably no clue about this particular package
Reply to: