Mailing lists, ticketing system and bug tracker – join the project!

Have you found a problem? Would you like to see a new feature in the software? There are several ways to get in touch. Customers with a valid support contract can use our ticketing system, and everyone can use the bug tracker.

The Bareos project has two mailing lists, for users and for developers.

bareos-users

On the mailing list bareos-users@googlegroups.com users discuss the operation of Bareos in small and large environments, ask questions and give answers.

Registration is done by email to:
bareos-users+subscribe@googlegroups.com

You can read the list in a web browser of your choice:
https://groups.google.com/forum/#!forum/bareos-users

GitHub Discussions

Are you interested in the technical details and want to contribute to the Bareos code? We have moved our developer discussions to a new platform: GitHub Discussions. This new tool offers a more modern and interactive way for the community to engage and collaborate on future developments.

To participate, simply visit: https://github.com/bareos/bareos/discussions

Please note that the bareos-devel@googlegroups.com mailing list will become read-only soon, and we encourage you to join us on GitHub to stay connected and contribute to the ongoing development of Bareos.
This change does not affect the bareos-users@googlegroups.com mailing list, which will remain active and unchanged.

How to report Bugs

If you have found a security issue in Bareos, please read this document on GitHub.

If something doesn’t work as expected or if you have suggestions for improvement (always welcome!), please check first if someone else has already reported the problem or proposed the idea. Please don’t just create feature requests or report bugs multiple times.

How to ensure that your report is not closed as duplicate or no change required:

Have a look at the Bareos manual and use the search function.
Make sure you have the latest version of the software installed.
Post your problem or idea on the bareos-user mailing list (also accessible via web browser). The list has a search function and an archive that contains older posts.
Check the bug tracker to see if there is already an entry; please use the search function.
If someone else has already reported the bug, don’t create a new entry, but comment on the existing one – for example, with additional information or confirmation that you have the same problem.
Maybe the bug is already fixed? Take a look in the latest repository.

Creating a Bug Report

If you have followed all the above tips and you are sure that you have found a bug, please note the following things:

You want the problem you describe to be fixed.
The more detailed information you provide, the better the chances that we will be able to fix the problem quickly. Therefore, please take the time to create a meaningful bug report which contains all the information needed to reproduce the problem.
Please remain objective and friendly – it’s easier and more pleasant for our support team to respond to polite requests.

What to include in the Bug Report?

We need the following information, please:

It’s really important that we can reproduce the bug – it’s almost impossible to fix it otherwise.
Make sure that you can reproduce the bug even in the latest repository.
Try to keep the steps to reproduce it to a minimum.
Be very specific about the operating system you’re using, its version number and the Bareos version.
Include the configuration file(s) so that we can reproduce the bug.
List all the steps that led to the bug on your system.
Send the log files. Please send them as attachments and do not simply copy them into the web interface of the bug tracker.
Create trace files, e.g. with setdebug. On Windows, let the daemons write the trace files.