If you have problems or question with this project, there are several options at your disposal:

  • Try to troubleshoot the issue yourself
  • Chat on IRC
  • File bug reports

We of course welcome other contributions like documentation, translations and patches, see the Contribution guide guide for more information on how to contribute to the project.


The basic way to troubleshoot this program is to run the same command as you did when you had an error with the --verbose or, if that doesn’t yield satisfactory results, with the --debug output.


The debug output outputs a lot of information and may be confusing for new users.

If you suspect there is a bug specific to your environment, you can also try to see if it is reproducible within the Test suite. From there, you can either file a bug report or try to fix the issue yourself, see the Contribution guide section for more information.

Otherwise, see below for more options to get support.


We are often present in realtime in the #feed2exec channel of the Freenode network. You can join the channel using a normal IRC client or using this web interface.

Bug reports

We want you to report bugs you find in this project. It’s an important part of contributing to a project, and all bug reports will be read and replied to politely and professionally.

We are using an issue tracker to manage issues, and this is where bug reports should be sent.


A few tips on how to make good bug reports:

  • Before you report a new bug, review the existing issues in the online issue tracker to make sure the bug has not already been reported elsewhere.
  • The first aim of a bug report is to tell the developers exactly how to reproduce the failure, so try to reproduce the issue yourself and describe how you did that.
  • If that is not possible, just try to describe what went wrong in detail. Write down the error messages, especially if they have numbers.
  • Take the necessary time to write clearly and precisely. Say what you mean, and make sure it cannot be misinterpreted.
  • Include the output of --version and --debug in your bug reports. See the issue template for more details about what to include in bug reports.

If you wish to read more about issues regarding communication in bug reports, you can read How to Report Bugs Effectively which takes about 30 minutes.


The output of the --debug may show information you may want to keep private. Do review the output before sending it in bug reports.

Commercial support

The project maintainers are available for commercial support for this software. If you have a feature you want to see prioritized or have a bug you absolutely need fixed, you can sponsor this development. Special licensing requirements may also be negociated if necessary. See Contact for more information on how to reach the maintainers.