Template:FAQ:General 11
Bug Reports
The best way to submit a bug report is via the bug database through the interface found at http://www.net-snmp.org/bugs/. Be sure to include the version of the package that you've been working with, the output of the command 'uname -a', the precise configuration or command that triggers the problem and a copy of any output produced.
Questions about using the package should be directed at the net-snmp-users@lists.sourceforge.net mailing list. Note that this mailing list is relatively busy, and the people answering these questions are doing so out of the goodness of their hearts, and in addition to their main employment. Please note the following:
- use plain text mail, rather than HTML
- don't resend questions more than once
(even if no-one answered immediately) - include full details of exact commands and error messages
("I've tried everything, and it doesn't work" isn't much use!) - do NOT send messages to -users and -coders mailing lists
(most developers read both anyway) - don't mail the developers privately - keep everything on the list
We can't promise to be able to solve all problems, but we'll certainly try and help. But remember that this is basically an unsupported package. It's Open Source, so if you need something fixing badly enough, fundamentally it's up to you to do the work.
Patches
All patches should be submitted to the patch manager at http://www.net-snmp.org/patches/. If possible, submit a bug report describing the patch as well (referencing it by its patch number) since the patch manager doesn't contain a decent description field.
The best way to submit patch (diff) information is by checking out the current code from the development SVN trunk, making your changes and then running "svn diff" after you're done.
If you're working from a source code distribution, and comparing old and new versions of a code file, use "diff -u OLDFILE NEWFILE"
