Hello, I have posted the following pre-release files to www.bacula.org/downloads:
2.2.0-restore.patch 2.2.1-restore.patch 2.2.2-restore.patch bacula-2.2.3.tar.gz bacula-2.2.3.tar.gz.sig winbacula-2.2.3.exe winbacula-2.2.3.exe.sig The web site does not permit directory listings of that directory, so you must explicitly specify each filename for download. These are preliminary files and not an official release, but if you want to get an early version of the code, it is there. I do not yet have an independent confirmation that the patch fixes the bug, but it does in my tests. At this point, I consider bacula-2.2.3 more stable than 2.2.2, but I recommend to wait until we hear more from the beta testers before putting this into production, unless you are doing multiple simultaneous backups to disk. I have not yet tested the winbacula file. You do not need to use it unless you are running a Win32 Storage daemon. Please note that the bug as currently identified affects only the Storage daemon, so there is no reason to upgrade your clients. Personally, I recommend upgrading the Director at the same time just for good form. As soon as the official release is loaded on Source Forge, it will be announced here. I expect that will be much later today my time ... Best regards, Kern ------------------------------------------------------------------------- This SF.net email is sponsored by: Microsoft Defy all challenges. Microsoft(R) Visual Studio 2005. http://clk.atdmt.com/MRT/go/vse0120000070mrt/direct/01/ _______________________________________________ Bacula-users mailing list Bacula-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/bacula-users
