Reporting Problems
what to include
It is important when reporting problems or when asking help to include all relevant information. Below are some guidelines that help you to find out what to include in bug reports or help messages. Sending message like 'I did this and it didnt work' doesnt help at all ; clearly state veejay's response or error messages.
- the exact command you entered on the commandline
- the operating system used
$ uname -r -o -m 2.6.10 i686 GNU/Linux
- what version of veejay you are using
- what goes wrong
- when using VIMS or OSC messages, include offending lines in bugreport.
- tried building veejay yourself ?
./configure 2>&1 | tee configure-output.txt
- compile error during make
make 2> | tee make-output.txt
Where to Report
- veejay-users@lists.sourceforge.net This list is for general discussion, getting help on usage about veejay. Also, write to the list if you have downloaded a release and have compilation problems. When using source from subversion, use the Trac ticket system. More information about this mailinglist can be found here: http://lists.sourceforge.net/lists/listinfo/veejay-users
- veejay-vevo@lists.sourceforge.net
This list is for general discussion about vevo, Veejay's video object library More information about this mailinglist can be found here: http://lists.sourceforge.net/lists/listinfo/veejay-vevo
