Bacula-users

[Bacula-users] Bacula 2.4.4 Released

2009-01-05 08:07:28
Subject: [Bacula-users] Bacula 2.4.4 Released
From: Kern Sibbald <kern AT sibbald DOT com>
To: "bacula-devel" <bacula-devel AT lists.sourceforge DOT net>
Date: Mon, 5 Jan 2009 12:48:17 +0100
Hello,

This is to let you know that the source tar files and the Win32 binaries for 
Bacula version 2.4.4 have been released to the Bacula Source Forge download 
area.

Release 2.4.4
This is an important bug fix to version 2.4.3.  All daemones are
compatible with prior 2.4.x version.

Bugs Fixed:
1192, 1110, 1175, 1188, 1171, 1206, and 1208.

Change Summary:
- Apply fix suggested by Bruno Friedmann to configure.in to
  find python2.5
Beta Release Version 2.4.4-b2
- Fix bug #1208. Inappropriate Volume purging.
- Modify sql_update.c to edit zeros rather than NULL in unset
  fields. This should fix bug #1206, where apparently the user
  has modified the Bacula schema.
- Backport most recent changes to compat.h and compat.cpp
  attempt to fix restore problem with accents in path. This
  works in version 2.5.x but is not tested in 2.4.4.
- Create and apply 2.4.3-migrate2.patch, which fixes two bugs
  - Bug #1206 -- sql error when there are no files to migrate.
  - Bug #1171 -- Job catalog log is not migrated during migration.
Beta Release 2.4.4-b1
- Apply 2.4.3-sd-deadlock.patch that should fix bug #1192.
- Remove extra db_lock() in get_prune_list_for_volume()
- Apply 2.4.3-prune-deadlock.patch that fixes a problem when
  using Catalog as message backend.
- Apply 2.4.3-win32-runscript-unicode-path.patch for #1110
  about a problem when executing a program with Unicode path.
- Apply 2.4.3-unique-inchanger.patch fix for #1175 about bad slot
  number if the volume is not in autochanger.
- Fix for bug #1188 where Volume is purged while writing
  on it.
- Get message enhancement to avoid job name lookup.
- Fix bug with job name duplication if more than 60 jobs created
  during a minute.
- Correct some bugs of cleanup in SD if the FD connection fails.
- Fix orphaned jobs (possible deadlock) while pruning.
- Backport of the btraceback script that keeps trace file on working dir
- Migrate DB Log records too. This fixes last part of bug #1171.
- Modify SQL so that jobs that failed will not be migrated.
- Correct bug where long retention periods caused immediate
  pruning.


Best regards,

Kern

------------------------------------------------------------------------------
_______________________________________________
Bacula-users mailing list
Bacula-users AT lists.sourceforge DOT net
https://lists.sourceforge.net/lists/listinfo/bacula-users

<Prev in Thread] Current Thread [Next in Thread>