| | 1 | OPIE Software Distribution, Release 2.4 Bug Reporting Form |
| | 2 | ======================================= ================== |
| | 3 | |
| | 4 | Before submitting a bug report, please check the README file and make |
| | 5 | sure that your "bug" is not a known problem. |
| | 6 | |
| | 7 | Please make a copy of this file and then edit it with your favorite |
| | 8 | text editor (NOT a word processor; the end result needs to be reasonable ASCII |
| | 9 | text) to include the answers to the following questions: |
| | 10 | |
| | 11 | 1. Your name and electronic mail address, in case we need more information. |
| | 12 | If you can provide multiple addresses, please do so in case we |
| | 13 | are unable to reply to the first one. |
| | 14 | |
| | 15 | 2. Your exact operating system vendor, name, and version number. If available, |
| | 16 | please provide the output of "uname -a" and/or the version of your C |
| | 17 | runtime library. Please be more specific than "UNIX". |
| | 18 | |
| | 19 | 3. The exact hardware the system was installed upon. |
| | 20 | |
| | 21 | 4. Which compiler and C runtime you used and its version number. |
| | 22 | For instance, some systems have been known to have the GNU libc |
| | 23 | installed as well as its native one, or to have a "BSD |
| | 24 | compatibility" environment. |
| | 25 | |
| | 26 | 5. What version of OPIE you are using (the output of opiepasswd -v) and, |
| | 27 | if you used the Autoconf install, a copy of the config.h, config.log, |
| | 28 | and Makefile that Autoconf created. |
| | 29 | |
| | 30 | 6. A clear description of what you did and what bug then appeared. |
| | 31 | If your system has the script(1) command, please run a session |
| | 32 | under that to demonstrate the bug. Window-system cut-and-paste |
| | 33 | also works well. Sometimes, the exact output is critical to |
| | 34 | finding the bug. |
| | 35 | |
| | 36 | If you can provide any of the following things, it will greatly assist |
| | 37 | us in fixing the problem and improve the chances that we'll get back to you: |
| | 38 | |
| | 39 | 7. A diagnosis of what is causing the problem. |
| | 40 | |
| | 41 | 8. A test case that can repeatably demonstrate the problem. |
| | 42 | |
| | 43 | 9. A fix for the problem. |
| | 44 | |
| | 45 | Bug reports should be sent by Internet electronic mail to |
| | 46 | <opie-bugs@inner.net>. This mail is run through an automated sorter that helps |
| | 47 | get the bug report into the hands of someone who can help you. In order to |
| | 48 | make that program work, we ask that you: |
| | 49 | |
| | 50 | * Send this is normal RFC822 plain text or MIME text/plain. |
| | 51 | |
| | 52 | * DO NOT send this or any other file as an "attachment" from |
| | 53 | your mailer. |
| | 54 | |
| | 55 | * DO NOT send a copy of your bug report to ANYONE other than |
| | 56 | <opie-bugs@inner.net>. This includes listing more than one recipient |
| | 57 | or sending it as a carbon-copy ("Cc:") to someone else. |
| | 58 | |
| | 59 | * DO NOT send a copy of your bug report directly to the |
| | 60 | authors or to any mailing lists. This really makes the |
| | 61 | authors angry, and will be interpreted as a request to not |
| | 62 | provide you with any help. |
| | 63 | |
| | 64 | * DO NOT re-send bug reports because you didn't receive a |
| | 65 | response. We attempt to respond to ALL properly submitted |
| | 66 | bug reports. If we can't send mail back to you or you |
| | 67 | didn't bother to follow the directions for submitting a |
| | 68 | bug report, you won't receive a response. |
| | 69 | |
| | 70 | While OPIE is NOT a supported program, we generally try to respond |
| | 71 | to all properly submitted bug reports as soon as we can. If your bug report |
| | 72 | is properly submitted so our machine sorter can process it, this usually |
| | 73 | takes one working day. If our machine sorter can't process your bug report, |
| | 74 | it usually takes a week or two. |
| | 75 | |
| | 76 | Copyright |
| | 77 | ========= |
| | 78 | |
| | 79 | %%% portions-copyright-cmetz-96 |
| | 80 | Portions of this software are Copyright 1996-1999 by Craig Metz, All Rights |
| | 81 | Reserved. The Inner Net License Version 2 applies to these portions of |
| | 82 | the software. |
| | 83 | You should have received a copy of the license with this software. If |
| | 84 | you didn't get a copy, you may request one from <license@inner.net>. |
| | 85 | |
tuxillo's projects / dragonfly.git / blame_incremental