Where do I report bugs and fixes?

Description: OpenSS7 Frequently Asked Questions #17.

Let common sense be your guide when reporting bugs. Please see the System Requirements and read the installation instructions that come with the package before reporting what appears to be bugs.

The mailing list is a proper place to report bugs. If you have a large amount of information in a bug report (over 40k), see Large Attachments. Let common sense be your guide when reporting bugs. Please see the System Requirements and read the installation instructions that come with the package before reporting what appears to be bugs. For details on the maling lists, please see the Mailing List page.

  Note: To limit spam, you must be a member of the mailing list to post to it.

The project also has a GNU GNATS based Bug Tracking System, if you prefer a more formal approach to problem reports. For details on the bug tracking system, see the Bug Reports page.

You may also mail your software bug report to openss7-bugs@openss7.org. and it will reach the Bug Tracking System. If you provide less information than is listed above, it may be difficult to assist you. Please remember that there is NO WARRANTY on code released under a Public License. For commercial support services, see the OpenSS7 Corporation website.

The project has been meaning to provide a 'send-pr'-like script with the release packages that will automatically generate a problem report and mail it to the Bug Tracking System, but this is not yet available. For now, it is a rather manual process.

Before making a bug report, you should be prepared to provide the following information:

• The version of Linux kernel you are running (e.g., 2.4.18)
• Whether the Linux machine is a single or multi-processor machine, and whether a preemptive kernel has been enabled.
• Whether you are running an SMP kernel, regarless of whether the machin is UP or SMP. (Some distributions run an SMP kenrel by default if you have not recompiled your kernel.)
• If the problem is a configuration problem, the 'config.log' file generated by './configure'.
• If the problem is a compilation problem, the 'compile.log' file generated by 'make compile.log'.
• If the problem is an installation problem, the 'install.log' or 'uninstall.log' file generated by 'make install.log' or 'make unistall.log'.
• If the problem is installing or removing an RPM, provide the standard and error output of 'rpm -ivvv' or 'rpm -evvv'.
• If the problem is a failed test case, the 'testsuite.log' file generated by 'make installcheck'.
• Any log messages that appear on the console or in the system log files.
• Extracts or complete test programs (if you can share them) that you are running that generates the problem.