bacula-1.34.6 RPM release

"D. Scott Barninger" <[email protected]> 01 Aug 2004 16:57:22 -0400
Newsgroups gmane.comp.sysutils.backup.bacula.announce
Message-ID <1091393840.26835.65.camel__10242.4685298049$1091394147$gmane$org@scott.localdomain>
Hello All,

The rpm packages for 1.34.6 are released to sourceforge
(http://sourceforge.net/project/showfiles.php?group_id=50727) and my
SuSE apt repository (http://ftp.gwdg.de/pub/linux/misc/suser-sbarnin/).
RedHat 8.0 users please read the Platform Notes.

There was some discussion on bacula-users after the last release which
prompts me to offer the following explanation of available packages:

bacula-sqlite
bacula-mysql
bacula-postgresql
These are full server installation packages providing the director,
storage daemon and file daemon as well as the command line console for
the indicated database support backends. They are not intended for
partial installations such as a stand alone storage server.

bacula-client
This provides the file daemon and command line console for client only
installations. It does not provide the gnome console for X
installations.

bacula-gconsole
This provides the gnome-console and can be installed along side of
either of the above two installation choices.

--------
Bacula-1.34 RPM Release Notes
01 Aug 2004
D. Scott Barninger
<barninger at fairfieldcomputers dot com>

Release 1.34.6-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=256964

**************************************************************
* This rpm release contains some important changes from 1.32 *
**************************************************************

The platform designator (rh7, rh8, rh9) has been REMOVED from 
the package names since 1.32d as this was creating some 
problems. Hence, you CAN NOT upgrade existing 1.32d or lower 
installations with these packages (rpm -U).

To upgrade:
1. Backup your configuration files (/etc/bacula/*.conf)
"just to be safe."
2. Uninstall the old bacula package, ie.
	rpm -e bacula-mysql-rh9
If you are not sure what package name is installed do
	rpm -qa | grep bacula
3. Install the new package with rpm -i

In addition, the spec file has been reworked to include a
platform and database configuration section at the beginning 
of the file. To rebuild the SRPM, first install using rpm -i 
then edit /usr/src/redhat/SPECS/bacula.spec (or whatever directory
structure your platform uses) to set platform and database options.
You can also pass any of the defines on the command line as before.

Example: 
	rpmbuild -ba \
	--define "build_rh9 1" \
	--define "build_sqlite 1" \
	bacula.spec
This will build RedHat 9 packages with sqlite support.

********************************************************
* PostgreSQL support and database detection and update *
********************************************************

The 1.34 release introduces support for PostgreSQL packages. There
is now a specific define for building mysql, sqlite and postgresql 
support. Formerly there was only a define for mysql and having it
not set resulted in an sqlite build.

In addition, post-install routines have been added to detect an 
existing bacula database before attempting to create the database.
Previously this just ran and caused a harmless error message if a
bacula database already existed. As this error message may have been
alarming, though harmless, we now only create the database if none
exists.

The 1.34 release requires an update to the bacula database structure
from version 6 to version 7. A pre-install routine has been added to
check for databases older than 6. In that event the install will exit
with an error message indicating that the database must be updated to
version 6 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 6 database is detected a
post-install 
routine will update the database after creating a backup file in the 
bacula working directory.

*************************
* bacula-client changes *
*************************

The 1.34 release adds the command line console to the client package and
adds a new package for for the gnome-console, bacula-gconsole. The
bacula-gconsole package requires bacula-client or any server package as
a dependancy. The gnome-console is no longer included in the server
packages so they may now be installed on servers without X or gnome.

This release adds superuser support for executing gnome-console. RedHat
rpms now use (and require) the usermode package. SuSE rpms use the xsu
package. In either case, when starting gnome-console a dialog box will
pop up to request the root password.

To disable usermode support on RedHat:
1. delete /etc/pam.d/gnome-console
2. delete /etc/security/console.apps/gnome-console
3. edit the bacula.desktop file to point to /usr/sbin/gnome-console
instead of /usr/bin/gnome-console
4. delete the symlink /usr/bin/gnome-console

To disable xsu support in SuSE:
1. edit the bacula.desktop file to remove the gnomesu wrapper and
execute /usr/sbin/gnome-console directly.

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

The 1.34 release provides official packaging support for SuSE. Packages
built on SuSE 9.0 are provided and it is known that the srpm will
rebuild on SuSE 8.x and possibly 7.x. Feedback from anyone doing so
would be appreciated.

This 1.34.6 release is likely to 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, and this week brings the news that
FedoraLegacy has suspended support for 8.0 due to lack of community
involvement.

Dropping RedHat 8.0 support will allow me to replace it on my packaging
host with a RedHat 9 installation and move my main development host to
SuSE 9.1. SuSE is increasingly becoming my platform of choice for
workstation use with RedHat EL3 (actually Whitebox) my choice for
servers.

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

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

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




-------------------------------------------------------
This SF.Net email is sponsored by OSTG. Have you noticed the changes on
Linux.com, ITManagersJournal and NewsForge in the past few weeks? Now,
one more big change to announce. We are now OSTG- Open Source Technology
Group. Come see the changes on the new OSTG site. www.ostg.com