On Wed, Sep 21, 2016 at 10:11:10AM +0100, Simon John wrote:
> Regarding the version info, I didn't realise it was ok/possible to put
> two versions in the tag, but I put it in the text anyway. Maybe file it
> as a bug to the reportbug maintainers?
The point is that you should not add two versions but the earliest one
you found it in. The BTS tracks the versions.
See the graph right at https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=838418.
In you rinitial report it would think it was new in 5.2.1-3, thus also making
the testing scripts refuse to update 5.2.1-1 in testing because "it has new
bugs (compared to testing)" which is untrue.
That one's said in what reportbug has shown you:
--- snip ---
Set the Version: header right. If you found a bug in a specific version,
set that as version:, even if you in the meanwhile upgraded. If you are on
an up-to-date version and tried old versions and they have the bug, too, set
the Version: header to the earliest version you found it in (of course, if
versions inbetween don't have the bug use the version in which it reappeared
and sustained to the current version)
--- snip ---
> No weird fonts or anything, using liberation* or mscorefonts* makes no
> difference, gnome is using canterell, changing that doesn't help either.