works again.
Conflict with older versions of the client.
Make mtx-changer.conf @sample-able so we don't overwrite on update.
ok & help from sthen and aja
packages which depend on each other:
- only create the _bacula user in -main (client parts)
- only create the _bacula-sd user in -server
Change _bacula's home dir from /var/bacula to /nonexistent.
/var/bacula needs to be writable by the _bacula group and since
/usr/libexec/security actually checks that user home dirs are
group-writable, whereas /etc/security just checked if the user
home dir was a writable *file*(!), it whines every day for
every machine with bacula client installed. (This will only
affect new installations so if you're annoyed by these mails
too, just vipw and change it by hand).
ok ajacoutot@ merdely@
- don't use ports libtool, it passes invalid flags to the linker
- since libbaccats-${BACKEND} must have the same .so version as
libbaccats, use a variable to make sure they are kept in-sync
- mark as being SHARED_ONLY and sync/merge plists
As usual with major version bump, do not forget to run the upgrade
script corresponding to your DB.
A new README is provided in the package.
Tested by sthen@ and myself.
"Don't wait on me" merdely@ (maintainer)
ok sthen@
Fixes the weird install issues with the bat binary
New features can be found here:
http://www.bacula.org/5.0.x-manuals/en/main/main/New_Features_in_5_0_0.html
Thanks to sthen for help with the new wantlib/lib_depends stuff,
removing the sqlite flavor, ...
Thanks to giovanni for pointing out a ${TRUEPREFIX} -> /usr/local that
crept into one of my patch files.
ok sthen@
section so the libraries weren't accessible by a normal user. These libs
were split off from the individual binaries in the last major update of
bacula (between openbsd 4.6 and 4.7) meaning that users not in group
_bacula would be unable to use the admin applications.
ok jasper@ merdely@
* Shared objects
* Virtual backups
* Duplicate Job Control
* TLS Authentication
* Exclude Dir Containing = <filename-string>
* Plugins including Exchange 2003/2007 Plugin
* libdbi backend abstraction
* Bat enhancements
Upgrading from 2.4.4 to 3.0.2 requires updating the database using
/usr/local/libexec/bacula/update_bacula_database. Database upgrades
from older databases can be done with other scripts in
/usr/local/libexec/bacula/updatedb. You can determine your database
version in mysql and postgresql with 'select * from version'.
As sthen@ reminded me and the documentation points out, when upgrading
between major versions (2.x.x -> 3.x.x), you should upgrade all of your
components at the same time due to protocol changes.
a *lot* of help from and ok sthen@
Add no_server PSEUDO_FLAVOR
Reorganize the Makefile some.
Remove dependency on qwt.
Set FULLPKGPATH for -main and -bat to remove backend dependencies
(found by and solution from naddy@)
Use SUBST_CMD.
ok jdixon@, okan@
Bacula changelog:
http://bacula.svn.sourceforge.net/viewvc/bacula/branches/Branch-2.2/bacula/ChangeLog?revision=6309&view=markup
Major port change in this version:
-main subpackage is now bacula-client
-server subpackage remains bacula-server
-bat subpackage is new bacula admin tool
-client subpackage goes away.
If the old -main subpackage was installed, the upgrade path is to
install both bacula-client and bacula-server.
Lots of input and assistance from sthen and okan.
ok okan; "if it works for you, go for it" sthen
Bacula is a set of computer programs that permit you (or the system
administrator) to manage backup, recovery, and verification of
computer data across a network of computers of different kinds.
In technical terms, it is a network Client/Server based backup program.
Bacula is relatively easy to use and efficient, while offering many
advanced storage management features that make it easy to find and
recover lost or damaged files. Due to its modular design, Bacula is
scalable from small single computer systems to systems consisting of
hundreds of computers located over a large network.
from Mike Erdely <mike@erdelynet.com>
