Hello Developers, The platforms/redhat/bacula.spec.in file in your 3.0.3 tarball has a number of problems when built for EL5 and sqlite:
- Source file bacula-docs is now bz2 not gz - Logwatch location wrong for newer distros - Logwatch applybaculadate script not installed - Sqlite database not created with correct permissions - Passwords not set up correctly in conf files Your published bacula-3.0.3-1.src.rpm fixes the first two, but not the remainder. The attached patch will ensure the correct logwatch locations for the supported Fedora-based distros (I don't know about SuSE or Mandrake) as well as fixing the other issues. I would also vote for having a placeholder in the Name fields of the .conf files, rather than the hostname of the build host. That way the real hostname can be inserted by the %post script in the same way that the passwords are. I'm building for CentOS 5, and will be installing the rpms on several servers, so having all the resources named after my build server isn't very useful default. There's a small mistake in bacula-3.0.3/scripts/logwatch/README: it tells you to copy scripts/logwatch/bacula to applybaculaupdate. I hope you find this useful. Moray. "To err is human. To purr, feline"
bacula.spec.in.patch
Description: Binary data
------------------------------------------------------------------------------ This SF.Net email is sponsored by the Verizon Developer Community Take advantage of Verizon's best-in-class app development support A streamlined, 14 day to market process makes app distribution fast and easy Join now and get one step closer to millions of Verizon customers http://p.sf.net/sfu/verizon-dev2dev
_______________________________________________ Bacula-devel mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/bacula-devel
