@c Permission is granted to copy, distribute and/or modify this document
@c under the terms of the GNU Free Documentation License, Version 1.3
@c or any later version published by the Free Software Foundation;
@c Permission is granted to copy, distribute and/or modify this document
@c under the terms of the GNU Free Documentation License, Version 1.3
@c or any later version published by the Free Software Foundation;
It is also valuable to try the newest version of @pspp{}, since the
problem may have already been fixed. You can always find the newest
It is also valuable to try the newest version of @pspp{}, since the
problem may have already been fixed. You can always find the newest
website}. You might have obtained PSPP from a downstream packager,
such as a GNU/Linux distribution; if your downstream package is not
up-to-date, please ask the distributor to update to the newest
website}. You might have obtained PSPP from a downstream packager,
such as a GNU/Linux distribution; if your downstream package is not
up-to-date, please ask the distributor to update to the newest
A high-quality bug report allows the developers to understand,
reproduce, and ultimately fix the problem. We recommend
including the following:
A high-quality bug report allows the developers to understand,
reproduce, and ultimately fix the problem. We recommend
including the following:
-@item The version of @pspp{} in which you encountered the problem
-That means the precise version number. ``The latest version''
-is often too ambiguous because
-releases happen quickly, and bug reports are archived indefinitely.
+@item
+The version of @pspp{} in which you encountered the problem. It also
+often helps to know some information about how @pspp{} was built.
+
+With @pspp{} command syntax, @code{SHOW SYSTEM.} will output
+everything we ordinarily need. In the PSPPIRE GUI,
+@clicksequence{Help @click{} System Info} produces the same output.
+
@item A sample of the syntax which causes the problem or, if it is a user
interface problem, the sequence of steps required to reproduce it.
Screenshots can be helpful for reporting bugs in the graphical user
interface, especially since GUI bugs can arise on some systems but
not others, but they do not usually help fixing other kinds of bugs.
@item A sample of the syntax which causes the problem or, if it is a user
interface problem, the sequence of steps required to reproduce it.
Screenshots can be helpful for reporting bugs in the graphical user
interface, especially since GUI bugs can arise on some systems but
not others, but they do not usually help fixing other kinds of bugs.
-When I run PSPP 0.8.4 on my GNU/Linux system, executing the following
-syntax:
+I'm running PSPP on a system where @code{SHOW SYSTEM.} outputs the
+following:
+
+@psppoutput{show-system}
+
+The bug I'm seeing is that executing the following syntax: