Comment 22 for bug 228693

Thanks for upgrading to the 2.4.2 version, which is much more stable than 2.4.0 and 2.4.1.

One additional consideration when producing Bacula packages. I regularly release well tested patches to bugs to the bacula-bugs section of the Source Forge release are. When you are building new packages, you might want to check what has been released there. Sometimes the fixes are trivial, but other times, they are important.

These patches are also available in the current branch Branch-2.4 and the trunk SVN (now imported to Lauchpad Bazaar) in bacula/patches and are all named 2.4.2-xxx.patch. It is possible from time to time that the patches are order dependent, so they should be applied in order of their date. In the Notes section of the Source Forge bacula-bugs release the patches are listed with the most recent one on top.

Finally, the documentation on what the patch fixes or possibly fixes, if we don't have a positive confirmation, and how to apply the patches is at the top of each patch file.

Personally, I prefer to pull the current Branch-2.4 rather than applying patches, but everyone has his own way of handling these things.

If there is anything I can do to make this all easier for you, please don't hesitate to let me know: kern at sibbald.com

Kern
Bacula upstream