Hello, Now that we have just released version 2.2.1, as Murphy's law dictates, we have a couple of more important bugs that seem to affect only older systems.
One is a problem building with older PostgreSQL versions The other is a Director critical crash caused by new code that supports certain older "brain damaged" OSes (including Win32). Note: the above problems only affect a small number of systems. Any recent version of Linux, Solaris, FreeBSD should have no problems. Normally, I would just release a couple of patches, but the problem affects the current Win32 Bacula servers, so we *must* release a new Win32 binary. Bottom line: I'm very likely going to make a release of version 2.2.2 at least for Win32, and either a patch or a full release for the source code. IMO, there is no reason to make new releases of the rpms unless one of the released rpms fails, which I think is unlikely. Question: does anyone feel that the 2.2.2 release should have anything other than Eric's PostgreSQL configure fix, my Director crash fix, and Scott's new .spec files (already committed)? Regards, Kern ------------------------------------------------------------------------- This SF.net email is sponsored by: Splunk Inc. Still grepping through log files to find problems? Stop. Now Search log events and configuration files using AJAX and a browser. Download your FREE copy of Splunk now >> http://get.splunk.com/ _______________________________________________ Bacula-devel mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/bacula-devel
