If you believe that there is a bug in ###pkgname###, we would be grateful if you take the time to report it. Only known problems can get fixed!
Here are a few tips to help you report this bug in a way that facilitates its resolution.
If you have trouble with a command, you can identify the corresponding package by running this command in a terminal:
$ dpkg -S `readlink -f $(which COMMAND)`
where COMMAND is the name of the command that fails.
If you believe there is a problem with a file installed on your system you can find the responsible package by running:
$ dpkg -S FULLPATH
where FULLPATH is the complete absolute path of the file.
That means including every single detail – not just the “important” ones. What kind of system (hardware/software) are you using? What did you do exactly when the bug hit you?
Remember: bug reports are not just input for developers, but also help other users to identify whether they are affected by the same problem, and a recommended solution applies to them as well.
A good bug report is an important service to the community!
More information on high quality bug reporting is available at: http://raphaelhertzog.com/go/bugreporting/
Please email bug reports to the neurodebian-users or neurodebian-devel mailing list – whichever is more appropriate. In rare cases where your bug report contains confidential information, please email it directly to firstname.lastname@example.org.
If you have evidence that the faulty behavior is not specific to NeuroDebian, your bug report is best directed to the developers of the respective software.