automake: Reporting Bugs
1
1 27.12 Reporting Bugs
1 ====================
1
1 Most nontrivial software has bugs. Automake is no exception. Although
1 we cannot promise we can or will fix a bug, and we might not even agree
1 that it is a bug, we want to hear about problems you encounter. Often
1 we agree they are bugs and want to fix them.
1
1 To make it possible for us to fix a bug, please report it. In order
1 to do so effectively, it helps to know when and how to do it.
1
1 Before reporting a bug, it is a good idea to see if it is already
1 known. You can look at the GNU Bug Tracker (https://debbugs.gnu.org/)
1 and the bug-automake mailing list archives
1 (https://lists.gnu.org/archive/html/bug-automake/) for previous bug
1 reports. We previously used a Gnats database
1 (http://sourceware.org/cgi-bin/gnatsweb.pl?database=automake) for bug
1 tracking, so some bugs might have been reported there already. Please
1 do not use it for new bug reports, however.
1
1 If the bug is not already known, it should be reported. It is very
1 important to report bugs in a way that is useful and efficient. For
1 this, please familiarize yourself with How to Report Bugs Effectively
1 (http://www.chiark.greenend.org.uk/~sgtatham/bugs.html) and How to Ask
1 Questions the Smart Way
1 (http://catb.org/~esr/faqs/smart-questions.html). This helps you and
1 developers to save time which can then be spent on fixing more bugs and
1 implementing more features.
1
1 For a bug report, a feature request or other suggestions, please send
1 email to <bug-automake@gnu.org>. This will then open a new bug in the
1 bug tracker (https://debbugs.gnu.org/automake). Be sure to include the
1 versions of Autoconf and Automake that you use. Ideally, post a minimal
1 ‘Makefile.am’ and ‘configure.ac’ that reproduces the problem you
1 encounter. If you have encountered test suite failures, please attach
1 the ‘test-suite.log’ file.
1