bacula-1.36.1 rpm release

"D. Scott Barninger" <[email protected]> 26 Nov 2004 13:27:59 -0500
Newsgroups gmane.comp.sysutils.backup.bacula.announce,gmane.comp.bacula.user
Message-ID <[email protected]>
Bacula-1.36 RPM Release Notes
25 Nov 2004
D. Scott Barninger
<barninger at fairfieldcomputers dot com>

Release 1.36.1-1

This release incorporates a number of significant changes.

These release notes refer to the rpm packaging only.
Please refer to the release notes and changelog in the
tarball for complete information on all changes or at
http://sourceforge.net/project/shownotes.php?release_id=285598

*******************
* Database update *
*******************

The 1.36 release requires an update to the bacula database structure
from version 7 to version 8. A pre-install routine has been added to
check for databases older than 7. In that event the install will exit
with an error message indicating that the database must be updated to
version 7 before installing this upgrade. Scripts for updating older
database formats are available for download in the bacula-updatedb
rpm package. In the event a version 7 database is detected a
post-install 
routine will update the database after creating a backup file in the 
bacula working directory.

*************************
* Rescue package change *
*************************

The rescue package now includes both the floppy and cdrom sets. Check 
/etc/bacula/rescue/floppy and /etc/bacula/rescue/cdrom. Due to this 
addition, cdrecord, mkisofs and make are now package dependancies. If
you 
do not intend to make CDRom disks it is safe to install the package with
the --nodeps option. Likewise you can do the same if you don't intend to
use the floppy tools in order to ignore the libc5 dependancy for
tomsrtbt. 
The rescue package remains a single package for all platforms. See the
manual 
for instructions on creating a rescue CDRom disk.

*************************
* Bacula client changes *
*************************

The bacula-gconsole package includes the new tray notification program
to monitor 
the system. This program is not included in Red Hat 7 or 8 packges. You
can start 
it from the menu entry to run it in the notification area of your panel.
Note that 
the permissions on /etc/bacula/tray-monitor.conf have been set to 644 in
order that 
an ordinary user may start the program. Users upgrading from an earlier
version of 
bacula should note that there are required changes to the other bacula
config files 
to accomodate communiction with the tray-monitor. Examine the contents
of the files 
bacula-dir.conf.rpmnew, bacula-sd.conf.rpmnew and bacula-fd.conf.rpmnew
and make the 
necessary changes to your config files when you edit the
tray-monitor.conf file.

************************
* Bacula group support *
************************

This release configures the daemons to run as user/group root.bacula and
adds the 
group bacula to the system group file. This is an empty group with no
added users. 
Administrators may add any users to the group they wish to have access
to files 
created by any of the daemons, eg. backup files written to disk for CDR
or DVD media, 
bacula logs, etc. See the manual chapter Running Bacula for details.

***********************************
* Bacula CD Image Manager package *
***********************************

Rpm packages for the bimagemgr CD Image Manager program are provided.
These packages 
are really noarch rpms but separate packages are provided due to
differences in file 
locations and dependancy package names on different distributions.
bimagemgr requires 
the addition of the web server user to be added to the group bacula. Add
the user apache 
to the group bacula for Red Hat or Mandrake systems. For SuSE systems
add the user 
wwwrun to the bacula group. Also change ownership of any pre-existing
Volume files to 
root.bacula so that the web server can access the files. See the file 
/etc/bacula/README.bimagemgr for more details.

******************
* Platform Notes *
******************

The 1.36 release provides official packaging support for Mandrake.
Packages built
on Mandrake 10.0 are provided. Mandrake users should note that the
packaging 
structure of these rpms is VERY different from the older packages
available in the 
Mandrake contrib section. Do NOT attempt to upgrade to these packages,
rather you 
should uninstall them and install these packages after making backup
copies of your 
catalog and configuration files. Also note that these packages, as all
of our rpms, 
contain a static build of sqlite, so they will conflict with the
sqlite-tools rpm 
which was required by the contrib packages.

This release will be the last to provide packages for RedHat 8.0. The
number of 
downloads has dropped to very small numbers, below those for the 7.x
packages.

Build support for RedHat 8.0 will of course remain in the source rpm so
anyone
choosing not to move off that platform can still rebuild the package on
a system
with the necessary development packages installed:

BuildRequires: readline-devel, atk-devel, ncurses-devel, pango-devel
BuildRequires: libstdc++-devel, libxml2-devel, zlib-devel, pkgconfig
BuildRequires: libtermcap-devel
BuildRequires: gtk2-devel >= 2.0
BuildRequires: libgnomeui-devel >= 2.0
BuildRequires: glibc-devel >= 2.3
BuildRequires: ORBit2-devel
BuildRequires: libart_lgpl-devel >= 2.0
BuildRequires: libbonobo-devel >= 2.0
BuildRequires: libbonoboui-devel >= 2.0
BuildRequires: bonobo-activation-devel
BuildRequires: GConf2-devel
BuildRequires: linc-devel
BuildRequires: freetype-devel

For MySQL support -
BuildRequires: mysql-devel >= 3.23

For Postgresql support -
BuildRequires: postgresql-devel >= 7




-------------------------------------------------------
SF email is sponsored by - The IT Product Guide
Read honest & candid reviews on hundreds of IT Products from real users.
Discover which products truly live up to the hype. Start reading now. 
http://productguide.itmanagersjournal.com/