Re: [Bacula-users] [bacula 0001642]: rpm-installed bat gets lockmgr failure on startup
Hello, bacula-bat-5.0.3-2.src.rpm is being uploaded to sourceforge now to address this bug. Binaries to follow. On Tuesday 28 September 2010 10:25:07 am you wrote: The following issue has been SUBMITTED. == http://bugs.bacula.org/view.php?id=1642 == Reported By:martin Assigned To:barninger == Project:bacula Issue ID: 1642 Category: rpms Reproducibility:always Severity: crash Priority: normal Status: assigned == Date Submitted: 2010-09-28 15:25 BST Last Modified: 2010-09-28 15:25 BST == Summary:rpm-installed bat gets lockmgr failure on startup Description: The version of bat in the 5.0.3 rpm/srpm files on the bacula site fail with this error on startup 100% of the time: bat: lockmgr.c:911 ASSERT failed at lockmgr.c:911: lmgr_is_active() == Issue History Date ModifiedUsername FieldChange == 2010-09-28 15:25 martin New Issue 2010-09-28 15:25 martin Status new = assigned 2010-09-28 15:25 martin Assigned To = barninger == -- Start uncovering the many advantages of virtual appliances and start using them to simplify application deployment and accelerate your shift to cloud computing. http://p.sf.net/sfu/novell-sfdev2dev ___ Bacula-users mailing list Bacula-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/bacula-users
[Bacula-users] bacula-5.0.3 rpm release to sourceforge
Bacula-5.0 RPM Release Notes 06 Sep 2010 D. Scott Barninger barninger at fairfieldcomputers dot com Release 5.0.3-1 This release incorporates a number of significant changes since 3.0. These release notes refer to the rpm packaging only. Please refer to the release notes and changelog in the tarball or on sourceforge for complete information on all changes. * * RPM packaging * * The docs, bat and mtx packages have been split out into separate spec files and srpm packages and the contrib build script adapted. Mtx packages are no longer provided as all current distributions should have one available. The bat srpm includes qt4 and should be able to be built on older systems without QT4. Rebuilding any of these srpm packages is simply: rpmbuild --rebuild bacula-bat-5.0.0-1.srpm * * Miscellaneous * * License changed to AGPL v3 Fixed bug with libbacsql files Applied patch for openssl version 1.x to build Fedora 12 Added build targets for su112, fc10, fc11 and fc12 Building rescue files is now removed as it doesn't work. Added support to build with tcpwrappers. Removed deprecated build_mysql4 and build_mysql5 defines. Consoles are now built with readline support in place of conio. ** * Postgresql Changes * ** Support for postgresql versions earlier than 8 is now deprecated. There are new defines for specifying postgresql version and package names which may optionally be passed at build time (defaults should work for most platform builds). --define postgresql_version 8 --define postgresql_package postgresql --define postgresql_server_package postgresql-server --define postgresql_devel_package postgresql-devel * * Buffer Overflow Error and Crash in fd * * Fedora 8/9 now set -D_FORTIFY_SOURCE=2 as default compiler option. This will probably be true on other platforms as they move to glibc = 2.7. This causes a false buffer overflow detected error and crash in bacula-fd and other executables. To avoid this problem a workaround for Redhat platforms is to set the CFLAGS in your ~/.rpmmacros file as follows: # uncomment for bacula #%__global_cflags -O2 -g -pipe -Wall -Wp,-D_FORTIFY_SOURCE=0 -fno-exceptions -fno-strict-aliasing -fno-rtti For SuSE platforms set as follows in your ~/.rpmrc file: optflags: i586 -O2 -g -m32 -march=i586 -mtune=i686 -fmessage-length=0 -D_FORTIFY_SOURCE=0 optflags: x86_64 -O2 -g -fmessage-length=0 -D_FORTIFY_SOURCE=0 See the discussion thread on bacula-devel for more information: http://sourceforge.net/search/?ml_name=bacula-develtype_of_search=mlistsgroup_id=50727words=%22buffer+overflow+detected%22 This problem should now be fixed in source but the project still recommends -D_FORTIFY_SOURCE=0. *** * bat (Bacula Admin Tool) * *** The bat subpackage now has QT4 included in the new separate SRPM and can be built on systems without QT4 available. As of 3.0.0 Gnome console and WX console are deprecated in favor of bat. As of 5.0.0 support for building Gnome console, WX console and tray monitor have been removed from the spec. *** * Database update * *** The 3.x and up releases require an update to the bacula database structure from version 11 to version 12. A pre-install routine will check for databases older than 11. In that event the install will exit with an error message indicating that the database must be updated to version 11 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 11 database is detected a post-install routine will update the database after creating a backup file in the bacula working directory. ** * SQLite Changes * ** SQLite is no longer supported by the project. *** * New bacula-libs package * *** The bacula shared libraries are now packaged separately in the bacula-libs rpm package. This package is required by other packages now. ** * Platform Notes * ** The spec file currently supports building on the following platforms: # RedHat builds --define build_rh7 1 --define build_rh8 1 --define build_rh9 1 # Fedora Core build --define build_fc1 1 --define build_fc3 1 --define build_fc4 1 --define build_fc5 1 --define build_fc6 1 --define build_fc7 1 --define build_fc8 1 --define build_fc9 1 --define build_fc10 1 --define build_fc11 1 --define build_fc12 1 # Whitebox Enterprise build --define build_wb3 1 # RedHat Enterprise builds --define build_rhel3 1 --define build_rhel4 1 --define build_rhel5 1 # CentOS build --define build_centos3 1 --define build_centos4 1 --define build_centos5 1 # Scientific Linux build --define build_sl3 1 --define
[Bacula-users] bacula-5.0.2 rpm release to sourceforge
Bacula-5.0 RPM Release Notes 02 May 2010 D. Scott Barninger barninger at fairfieldcomputers dot com Release 5.0.2-1 This release incorporates a number of significant changes since 3.0. These release notes refer to the rpm packaging only. Please refer to the release notes and changelog in the tarball or on sourceforge for complete information on all changes. * * RPM packaging * * The docs, bat and mtx packages have been split out into separate spec files and srpm packages and the contrib build script adapted. Mtx packages are no longer provided as all current distributions should have one available. The bat srpm includes qt4 and should be able to be built on older systems without QT4. Rebuilding any of these srpm packages is simply: rpmbuild --rebuild bacula-bat-5.0.0-1.srpm * * Miscellaneous * * Applied patch for openssl version 1.x to build Fedora 12 Added build targets for su112, fc10, fc11 and fc12 Building rescue files is now removed as it doesn't work. Added support to build with tcpwrappers. Removed deprecated build_mysql4 and build_mysql5 defines. Consoles are now built with readline support in place of conio. * * Buffer Overflow Error and Crash in fd * * Fedora 8/9 now set -D_FORTIFY_SOURCE=2 as default compiler option. This will probably be true on other platforms as they move to glibc = 2.7. This causes a false buffer overflow detected error and crash in bacula-fd and other executables. To avoid this problem a workaround for Redhat platforms is to set the CFLAGS in your ~/.rpmmacros file as follows: # uncomment for bacula #%__global_cflags -O2 -g -pipe -Wall -Wp,-D_FORTIFY_SOURCE=0 -fno-exceptions -fno-strict-aliasing -fno-rtti For SuSE platforms set as follows in your ~/.rpmrc file: optflags: i586 -O2 -g -m32 -march=i586 -mtune=i686 -fmessage-length=0 -D_FORTIFY_SOURCE=0 optflags: x86_64 -O2 -g -fmessage-length=0 -D_FORTIFY_SOURCE=0 See the discussion thread on bacula-devel for more information: http://sourceforge.net/search/?ml_name=bacula-develtype_of_search=mlistsgroup_id=50727words=%22buffer+overflow+detected%22 This problem should now be fixed in source but the project still recommends -D_FORTIFY_SOURCE=0. *** * bat (Bacula Admin Tool) * *** The bat subpackage now has QT4 included in the new separate SRPM and can be built on systems without QT4 available. As of 3.0.0 Gnome console and WX console are deprecated in favor of bat. As of 5.0.0 support for building Gnome console, WX console and tray monitor have been removed from the spec. *** * Database update * *** The 3.x and up releases require an update to the bacula database structure from version 11 to version 12. A pre-install routine will check for databases older than 11. In that event the install will exit with an error message indicating that the database must be updated to version 11 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 11 database is detected a post-install routine will update the database after creating a backup file in the bacula working directory. ** * SQLite Upgrade * ** For users of the sqlite package, from 2.2.7 onward sqlite3 replaces sqlite2. Your sqlite2 database file (/var/lib/bacula/bacula.db) is not compatible with sqlite3. During an upgrade the pre-install script will check for this situation. If found it will dump your catalog data to the file /var/lib/bacula/bacula_backup.sql, rename your old catalog file to /var/lib/bacula/bacula.db.old, and exit. You should then re-run the rpm upgrade. After the upgrade is complete restore your catalog data with the following commands (as root): /etc/bacula/drop_sqlite3_tables cd /var/lib/bacula /usr/lib/bacula/sqlite/sqlite3 $* bacula.db bacula_backup.sql chown bacula.bacula bacula.db *** * New bacula-libs package * *** The bacula shared libraries are now packaged separately in the bacula-libs rpm package. This package is required by other packages now. ** * Platform Notes * ** The spec file currently supports building on the following platforms: # RedHat builds --define build_rh7 1 --define build_rh8 1 --define build_rh9 1 # Fedora Core build --define build_fc1 1 --define build_fc3 1 --define build_fc4 1 --define build_fc5 1 --define build_fc6 1 --define build_fc7 1 --define build_fc8 1 --define build_fc9 1 --define build_fc10 1 --define build_fc11 1 --define build_fc12 1 # Whitebox Enterprise build --define build_wb3 1 # RedHat Enterprise builds --define build_rhel3 1 --define build_rhel4 1 --define build_rhel5 1 # CentOS build --define build_centos3 1 --define
[Bacula-users] Fedora 12 and OpenSSLv1 - bacula 5.0.1-2 rpm release
Good Afternoon, Kern has developed a patch to address the problems compiling bacula with openssl version 1.x. I have successfully applied this patch to the released 5.0.1 code and created rpms for Fedora 12 (server and client packages only). Unfortunately I'm still unable to build bat on Fedora 12 in what seems to be an unrelated problem. I have posted bacula-5.0.1-2.src.rpm to sourceforge along with the fc12 binaries. I have also posted the patch to the bacula-patches section for anyone trying to build from source. Apply the patch from within the main bacula directory using 'patch -p2' Regards, Scott -- Download Intel#174; Parallel Studio Eval Try the new software tools for yourself. Speed compiling, find bugs proactively, and fine-tune applications for parallel performance. See why Intel Parallel Studio got high marks during beta. http://p.sf.net/sfu/intel-sw-dev ___ Bacula-users mailing list Bacula-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/bacula-users
[Bacula-users] Fwd: [bacula 0001523]: Wrong freetype2 reference
Hello all, This is a minor bug in the 5.0.0 and 5.0.1 bat rpm packages which will be fixed in the next release. It is safe to install using --nodeps until fixed. ---BeginMessage--- The following issue has been ASSIGNED. == http://bugs.bacula.org/view.php?id=1523 == Reported By:neteler Assigned To:barninger == Project:bacula Issue ID: 1523 Category: bat Reproducibility:always Severity: minor Priority: normal Status: assigned == Date Submitted: 2010-03-05 08:50 UTC Last Modified: 2010-03-05 16:32 UTC == Summary:Wrong freetype2 reference Description: Using self-compiled RPM from SRPM taken from bacula.org Web site. It compiles successfully but refuses to install: [r...@fep x86_64]# rpm -Uhv bacula-bat-5.0.1-1.x86_64.rpm bacula-mysql-5.0.1-1.x86_64.rpm bacula-updatedb-5.0.1-1.x86_64.rpm bacula-mtx-5.0.1-1.x86_64.rpm error: Failed dependencies: freetype2 is needed by bacula-bat-5.0.1-1.x86_64 Indeed, the package is installed but has a different name scheme: rpm -qa | grep freetype freetype-2.2.1-21.el5_3.i386 freetype-2.2.1-21.el5_3.x86_64 freetype-devel-2.2.1-21.el5_3.x86_64 freetype-devel-2.2.1-21.el5_3.i386 I assume that a SPEC file tweak is needed. == Issue History Date ModifiedUsername FieldChange == 2010-03-05 08:50 netelerNew Issue 2010-03-05 16:32 kern Status new = assigned 2010-03-05 16:32 kern Assigned To = barninger == ---End Message--- -- Download Intel#174; Parallel Studio Eval Try the new software tools for yourself. Speed compiling, find bugs proactively, and fine-tune applications for parallel performance. See why Intel Parallel Studio got high marks during beta. http://p.sf.net/sfu/intel-sw-dev___ Bacula-users mailing list Bacula-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/bacula-users
[Bacula-users] Bacula version 5.0.1 compile error on Fedora 12
Hello all, I installed Fedora 12 recently and tried to build for this release. This was the result: Compiling guid_to_name.c crypto.c: In function 'ASN1_OCTET_STRING* openssl_cert_keyid(X509*)': crypto.c:333: error: invalid conversion from 'const X509V3_EXT_METHOD*' to 'X509V3_EXT_METHOD*' crypto.c: In function 'CRYPTO_SESSION* crypto_session_new(crypto_cipher_t, alist*)': crypto.c:1102: error: cannot convert 'unsigned char*' to 'EVP_PKEY_CTX*' for argument '1' to 'int EVP_PKEY_encrypt(EVP_PKEY_CTX*, unsigned char*, size_t*, const unsigned char*, size_t)' crypto.c: In function 'crypto_error_t crypto_session_decode(const u_int8_t*, u_int32_t, alist*, CRYPTO_SESSION**)': crypto.c:1226: error: cannot convert 'unsigned char*' to 'EVP_PKEY_CTX*' for argument '1' to 'int EVP_PKEY_decrypt(EVP_PKEY_CTX*, unsigned char*, size_t*, const unsigned char*, size_t)' make[1]: *** [crypto.lo] Error 1 make[1]: *** Waiting for unfinished jobs ^CExecuting(%install): /bin/sh -e /var/tmp/rpm-tmp.v78FUL make[1]: *** [fnmatch.lo] Error 1 make[1]: *** [guid_to_name.lo] Error 1 make: *** [all] Interrupt There have been some other posts to the list on this subject so I wanted to share what we know at this point. Fedora 12 is using openssh-1.0 beta which unfortunately incorporates some incompatible changes to the library which are breaking the build. Kern has been in touch with the openssl team and we will be working on a patch to try to address this as soon as possible. In the meantime we are recommending that you build without openssl support if you want to upgrade. I will publish binary rpms this weekend without openssl support for Fedora 12. You may also edit the spec file in the currently published SRPM to remove openssl support by deleting the line --with-openssl from the configure statement. Regards, Scott -- Download Intel#174; Parallel Studio Eval Try the new software tools for yourself. Speed compiling, find bugs proactively, and fine-tune applications for parallel performance. See why Intel Parallel Studio got high marks during beta. http://p.sf.net/sfu/intel-sw-dev ___ Bacula-users mailing list Bacula-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/bacula-users
[Bacula-users] bacula client rpms
Hello, Please note there was a bug in the client rpm packages I released the other day. I've withdrawn them and will repost them shortly to sourceforge. Scott -- Download Intel#174; Parallel Studio Eval Try the new software tools for yourself. Speed compiling, find bugs proactively, and fine-tune applications for parallel performance. See why Intel Parallel Studio got high marks during beta. http://p.sf.net/sfu/intel-sw-dev ___ Bacula-users mailing list Bacula-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/bacula-users
Re: [Bacula-users] [Bacula-devel] Bacula version 5.0.1 released to Source Forge - RPM release
Thanks. Fixed in git repo. There was a naming convention change that caused
that. How odd that the published packages did not break and SL did.
On Friday 26 February 2010 09:38:58 am Richard Frewin wrote:
On Thu 25 Feb 2010 at 18:04, Scott Barninger
(barnin...@fairfieldcomputers.com) wrote:
Bacula-5.0 RPM Release Notes
25 February 2010
D. Scott Barninger
Thanks for your hard work on this.
Unfortunately on Scientific Linux 5.2 (x86_64) the following ...
rpmbuild --rebuild --define build_sl5 1 --define build_client_only 1
bacula-5.0.1-1.src.rpm
fails with errors...
Installed (but unpackaged) file(s) found:
/usr/lib64/libbac-5.0.1.so
/usr/lib64/libbaccfg-5.0.1.so
/usr/lib64/libbacfind-5.0.1.so
/usr/lib64/libbacpy-5.0.1.so
The following patch that simply removes a ',' from four lines in the
spec file fixes this for me.
==8=8==
--- SPECS/bacula.spec 2010-02-25 18:54:30.0 +
+++ ./bacula.spec 2010-02-26 14:24:55.0 +
@@ -1368,10 +1368,10 @@
%{_mandir}/man8/bconsole.8.%{manpage_ext}
%{_mandir}/man8/btraceback.8.%{manpage_ext}
%{_mandir}/man1/bat.1.%{manpage_ext}
-%{_libdir}/libbac.*
-%{_libdir}/libbaccfg.*
-%{_libdir}/libbacfind.*
-%{_libdir}/libbacpy.*
+%{_libdir}/libbac*
+%{_libdir}/libbaccfg*
+%{_libdir}/libbacfind*
+%{_libdir}/libbacpy*
%_prefix/share/doc/*
%pre client
==8=8==
Cheers ...
--
--
Richard A Frewin | Email: richard.fre...@astro.cf.ac.uk
__
When the straw breaks the camel's back,
blood stains the sand.. - Roaring Jelly
--
Download Intel#174; Parallel Studio Eval
Try the new software tools for yourself. Speed compiling, find bugs
proactively, and fine-tune applications for parallel performance.
See why Intel Parallel Studio got high marks during beta.
http://p.sf.net/sfu/intel-sw-dev
___
Bacula-users mailing list
Bacula-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/bacula-users
Re: [Bacula-users] Fwd: Some issues on 5.0.0 srpm
On Sunday 07 February 2010 02:13:29 pm Timo Neuvonen wrote: Output of the above attached. What came into my mind... is the test in line 100 in the attachment (similar to the one I highlighted above with ***) wrong way: elif [ $DB_VER -lt 11 ]; then echo This release requires an upgrade to your bacula database. Does this skip the update, if the old level was 11? A long time since I had shell scripts for breakfast, but I read that if database version is less than 11 then run the update... I think it should run when equal to 11? My bad. When I was making the updates I got sqlite and postgresql but somehow missed mysql in the post. You are correct but it should be: elif [ $DB_VER -lt 12 ]; then Thanks for your help. It will be fixed for the next release. For all users upgrading with the 5.0.0 be warned that the mysql database update is broken and you must do it manually. Regards, Scott -- The Planet: dedicated and managed hosting, cloud storage, colocation Stay online with enterprise data centers and the best network in the business Choose flexible plans and management services without long-term contracts Personal 24x7 support from experience hosting pros just a phone call away. http://p.sf.net/sfu/theplanet-com ___ Bacula-users mailing list Bacula-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/bacula-users
Re: [Bacula-users] Bacula spec changes
Hello Kern, Well, someone certainly needs to buy you a beer or two, that is an amazing amount of work for the time invested. Jack - are you listening? I will certainly give this a complete look and integrate it into the project builds. You have always been the team leader here and I am happy to work with your example. See below for my preliminary comments. Please note that I am writing now preliminarily without looking at anything. On Sunday 02 August 2009 04:13:19 pm Kern Sibbald wrote: Hello Scott, I'd like to outline a bit of what I have done to the spec files, but first, I would like to say that I believe that I have taken into consideration all the points that you have raised to this point: the file is now simply bacula.spec and I have split bat, mtx, and the docs out into separate specs, which mean that the build for the main rpms is *much* faster. We agree on the splits to be sure and if this means you have abandoned the idea of using the configure script to rewrite paths I can only say thank you for considering my opinion. I agree that we can dispense with the mtx sub-package as all major distros now package it. I'm also intrigued by your idea to simply incorporate bat rather than make it a separate package but I suspect we would be hounded by the folks who want to install a server without X. For those who read this: I am making this changes after discussing it with Scott not because there is anything wrong with the current spec, there are just some changes that are necessitated to accomodate for differences with way Bacula Systems will be packaging the Enterprise rpms. Well, that's a nice way of saying that Kern took the time to eliminate a LOT of cruft that has accumulated in the spec file as time wore on and I never found the time to do. In addition to creating four spec files: bacula.spec bacula-docs.spec bacula-mtx.spec bacula-bat.spec I have made the following changes: - the gconsole, wxconsole, and tray-monitor code are now gone If we need one of those we can always create another spec file - the bacula.spec file is considerably simpler because: - gconsole, mtx, bat, docs, wxconsole, and the tray monitor are removed good riddance. - I have remove almost all the library version dependences. The idea is that we should rely on the OS packagers to ensure that the correct libraries are loaded. Here I would suggest some discussion. I have long thought about deleting the bloat of Requires: in the spec. RPM automatically inserts requires for specific library files and versions. If you are installing the package with a package manager (ie. yum or yast2) it will automatically solve and pull in dependencies. But if you download the package from us and attempt to 'rpm -ivh bacula-blah' then without the specific package requires it will give the user cryptic error messages that they will have difficulty solving. Thus I have long maintained the bloat of distro-specific package requires. - I have made a few shortcut defines that reduce the length of some of the %if statements. - I have corrected a few of the places where passwords were edited in. They were misedited in at least one place causing password failures. - I added new post processing code that uses the name of the machine on which the package is installed. This is used to make the daemon names correspond to the installed machine name rather than the build machine name. Nice ;-) - The bat build now builds with Qt 4.3.2 rather than what is installed on the build machine. This should result in a much stabler bat. - I install all the man pages with the base package, which is what I think is the correct thing to do, even though the user may not install all the components -- at least he can know what exists. - I have certainly screwed up some of the older builds by the changes in the %ifs. Therefore we should maintain the current spec file in some archive form perhaps. I'm not really worried about maintaining the older builds but I ocassionally get the odd email from the user who just can't stand to give up RH-7.3 and this would at least give them something to work from if it really mattered. Example from the changelog: * Sat May 16 2009 D. Scott Barninger barnin...@fairfieldcomputers.com - fix libxml dependency for rh7 per Pasi Kärkkäinen pa...@iki.fi - I haven't yet had time to actually test the binaries to see if they install and run correctly. - There are a number of additional changes that I need to integrate from the Enterprise .spec, which corrects a good number of permission problems when running the Dir and SD as bacula rather than root. - I seems to me that there was a version of bconsole in /usr/bin. I deleted that code. It is now installed into /usr/sbin. If someone also wants it in /usr/bin, we can add a hardlink. I think you may have altered the code which used RH consolehelper to escalate to root which involved
Re: [Bacula-users] [Bacula-devel] Bacula version 3.0.2 released to Source Forge
Rpm packages released today. Bacula-3.0 RPM Release Notes 26 July 2009 D. Scott Barninger barninger at fairfieldcomputers dot com Release 3.0.2-1 This release incorporates a number of significant changes since 2.0. These release notes refer to the rpm packaging only. Please refer to the release notes and changelog in the tarball or on sourceforge for complete information on all changes. * * Miscellaneous * * Added build switch to pass Distribution tag: --define DISTNAME Distribution Name Building rescue files is now off by default as it doesn't work and as of this release the static fd won't build for me. Thus the nobuild_rescue switch is replaced by build_rescue. Added build target for su111 Added nobuild_rescue switch to supress building the rescue package Removed libtermcap dependency for fc9 Added build target for su110 Added build target for fc9 File location changes for compatibility with FHS. Force stripping of binaries for SuSE packages. Fixed bug 1037. Added nobuild_mtx switch to supress build of mtx package. Added missing files now required by the rescue configure script. Corrected dist target for rhel5. Corrected QT dependency name for RedHat flavors. Added fix for RHEL5 64 bit QT paths. Added build target for su103. Added build targets for rhel5 and clones. Build target added for Scientific Linux (RHEL clone) thanks to Jon Peatfield. Merged Otto Mueller's patch changing some directory locations for FHS compatibility but retaining the script directory as /etc/bacula. gnome-console and wxconsole have been renamed to bgnome-console and bwx-console respectively. *** * New Build Option to Install in Single Directory * *** A new build define has been added which will build packages that install most of the files to /opt/bacula. Only the man pages, init scripts, logwatch and menu entries are installed to the root filesystem. --define single_dir_install 1 * * Buffer Overflow Error and Crash in fd * * Fedora 8/9 now set -D_FORTIFY_SOURCE=2 as default compiler option. This will probably be true on other platforms as they move to glibc = 2.7. This causes a false buffer overflow detected error and crash in bacula-fd and other executables. To avoid this problem a workaround for Redhat platforms is to set the CFLAGS in your ~/.rpmmacros file as follows: # uncomment for bacula #%__global_cflags -O2 -g -pipe -Wall -Wp,-D_FORTIFY_SOURCE=0 -fno-exceptions -fno-strict-aliasing -fno-rtti For SuSE platforms set as follows in your ~/.rpmrc file: optflags: i586 -O2 -g -m32 -march=i586 -mtune=i686 -fmessage-length=0 -D_FORTIFY_SOURCE=0 optflags: x86_64 -O2 -g -fmessage-length=0 -D_FORTIFY_SOURCE=0 See the discussion thread on bacula-devel for more information: http://sourceforge.net/search/?ml_name=bacula-develtype_of_search=mlistsgroup_id=50727words=%22buffer+overflow+detected%22 This problem should now be fixed in source but the project still recommends -D_FORTIFY_SOURCE=0. *** * bat (Bacula Admin Tool) * *** A new subpackage has been added for the new bat QT-based GUI administration tool. This requires QT = 4.2 --define build_bat 1 If you encounter problems building the bat package on platforms where you do have the proper QT4 support (QT = 4.2) it may be necessary to adjust your $QTDIR and $PATH variables. On Fedora 8/9 it was necessary to: export QTDIR=/usr/lib/qt4;export PATH=/usr/lib/qt4/bin:$PATH;rpmbuild blah... As of 2.4.4 this should no longer be necessary as we sniff the paths with pkgconfig. As of 3.0.0 Gnome console and WX console are deprecated in favor of bat. *** * Gnome console dropped on some platforms * *** The gconsole package has been dropped on older gnome platforms (gtk+ 2.4). Changes in the gnome api and code produced by Glade no longer build. In addition, the tray monitor now fails to build on 2.10 platforms. gconsole is now not built on the following platforms: rh7, rh8, rh9, rhel3 (and clones), fc1, fc3, fc4, mdk, su9, su10 *** * Database update * *** The 3.x release requires an update to the bacula database structure from version 10 to version 11. A pre-install routine will check for databases older than 10. In that event the install will exit with an error message indicating that the database must be updated to version 10 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 10 database is detected a post-install routine will update the database after creating a backup file in the bacula working directory. ** * SQLite Upgrade
Re: [Bacula-users] bacula 3.0.1 rpm release
I'm not sure why Felix didn't upload them, however I've just become aware that the packages we did release do not work. There was a structural change in the source code that has caused a packaging problem which I will have fixed by the next release. In the meantime you can continue to use bat-2.4.4. On Saturday 13 June 2009 11:57:41 pm Devin Reade wrote: Thank you very much for doing the work of making this release (in particular, the el5 release which I am using on CentOS 5). It doesn't appear that the bacula-bat RPMs are up on sourceforge in the fschwarz directory as they were with previous releases. I'm assuming that this is related to the qt problems described in April and May on this list. Is there a plan to release an el5 RPM for bacula-bat 3.0.1? Or are you foregoing it for this release? Devin -- Crystal Reports - New Free Runtime and 30 Day Trial Check out the new simplified licensing option that enables unlimited royalty-free distribution of the report engine for externally facing server and web deployment. http://p.sf.net/sfu/businessobjects ___ Bacula-users mailing list Bacula-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/bacula-users
[Bacula-users] bacula 3.0.1 rpm release
Bacula-3.0 RPM Release Notes 02 May 2009 D. Scott Barninger barninger at fairfieldcomputers dot com Release 3.0.1-1 This release incorporates a number of significant changes since 2.0. These release notes refer to the rpm packaging only. Please refer to the release notes and changelog in the tarball or on sourceforge for complete information on all changes. * * Miscellaneous * * Added build switch to pass Distribution tag: --define DISTNAME Distribution Name Building rescue files is now off by default as it doesn't work and as of this release the static fd won't build for me. Thus the nobuild_rescue switch is replaced by build_rescue. Added build target for su111 Added nobuild_rescue switch to supress building the rescue package Removed libtermcap dependency for fc9 Added build target for su110 Added build target for fc9 File location changes for compatibility with FHS. Force stripping of binaries for SuSE packages. Fixed bug 1037. Added nobuild_mtx switch to supress build of mtx package. Added missing files now required by the rescue configure script. Corrected dist target for rhel5. Corrected QT dependency name for RedHat flavors. Added fix for RHEL5 64 bit QT paths. Added build target for su103. Added build targets for rhel5 and clones. Build target added for Scientific Linux (RHEL clone) thanks to Jon Peatfield. Merged Otto Mueller's patch changing some directory locations for FHS compatibility but retaining the script directory as /etc/bacula. gnome-console and wxconsole have been renamed to bgnome-console and bwx-console respectively. *** * New Build Option to Install in Single Directory * *** A new build define has been added which will build packages that install most of the files to /opt/bacula. Only the man pages, init scripts, logwatch and menu entries are installed to the root filesystem. --define single_dir_install 1 * * Buffer Overflow Error and Crash in fd * * Fedora 8/9 now set -D_FORTIFY_SOURCE=2 as default compiler option. This will probably be true on other platforms as they move to glibc = 2.7. This causes a false buffer overflow detected error and crash in bacula-fd and other executables. To avoid this problem a workaround for Redhat platforms is to set the CFLAGS in your ~/.rpmmacros file as follows: # uncomment for bacula #%__global_cflags -O2 -g -pipe -Wall -Wp,-D_FORTIFY_SOURCE=0 -fno-exceptions -fno-strict-aliasing -fno-rtti For SuSE platforms set as follows in your ~/.rpmrc file: optflags: i586 -O2 -g -m32 -march=i586 -mtune=i686 -fmessage-length=0 -D_FORTIFY_SOURCE=0 optflags: x86_64 -O2 -g -fmessage-length=0 -D_FORTIFY_SOURCE=0 See the discussion thread on bacula-devel for more information: http://sourceforge.net/search/?ml_name=bacula-develtype_of_search=mlistsgroup_id=50727words=%22buffer+overflow+detected%22 This problem should now be fixed in source but the project still recommends -D_FORTIFY_SOURCE=0. *** * bat (Bacula Admin Tool) * *** A new subpackage has been added for the new bat QT-based GUI administration tool. This requires QT = 4.2 --define build_bat 1 If you encounter problems building the bat package on platforms where you do have the proper QT4 support (QT = 4.2) it may be necessary to adjust your $QTDIR and $PATH variables. On Fedora 8/9 it was necessary to: export QTDIR=/usr/lib/qt4;export PATH=/usr/lib/qt4/bin:$PATH;rpmbuild blah... As of 2.4.4 this should no longer be necessary as we sniff the paths with pkgconfig. As of 3.0.0 Gnome console and WX console are deprecated in favor of bat. *** * Gnome console dropped on some platforms * *** The gconsole package has been dropped on older gnome platforms (gtk+ 2.4). Changes in the gnome api and code produced by Glade no longer build. In addition, the tray monitor now fails to build on 2.10 platforms. gconsole is now not built on the following platforms: rh7, rh8, rh9, rhel3 (and clones), fc1, fc3, fc4, mdk, su9, su10 *** * Database update * *** The 3.x release requires an update to the bacula database structure from version 10 to version 11. A pre-install routine will check for databases older than 10. In that event the install will exit with an error message indicating that the database must be updated to version 10 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 10 database is detected a post-install routine will update the database after creating a backup file in the bacula working directory. ** * SQLite Upgrade * ** For users
Re: [Bacula-users] [Bacula-devel] Bacula 2.4.4 Released
Bacula-2.4 RPM Release Notes 10 January 2009 D. Scott Barninger barninger at fairfieldcomputers dot com Release 2.4.4-1 This release incorporates a number of significant changes since 1.38. These release notes refer to the rpm packaging only. Please refer to the release notes and changelog in the tarball or on sourceforge for complete information on all changes. * * Miscellaneous * * Added build target for su111 Added nobuild_rescue switch to supress building the rescue package Removed libtermcap dependency for fc9 Added build target for su110 Added build target for fc9 File location changes for compatibility with FHS. Force stripping of binaries for SuSE packages. Fixed bug 1037. Added nobuild_mtx switch to supress build of mtx package. Added missing files now required by the rescue configure script. Corrected dist target for rhel5. Corrected QT dependency name for RedHat flavors. Added fix for RHEL5 64 bit QT paths. Added build target for su103. Added build targets for rhel5 and clones. Build target added for Scientific Linux (RHEL clone) thanks to Jon Peatfield. Merged Otto Mueller's patch changing some directory locations for FHS compatibility but retaining the script directory as /etc/bacula. gnome-console and wxconsole have been renamed to bgnome-console and bwx-console respectively. *** * New Build Option to Install in Single Directory * *** A new build define has been added which will build packages that install most of the files to /opt/bacula. Only the man pages, init scripts, logwatch and menu entries are installed to the root filesystem. --define single_dir_install 1 * * Buffer Overflow Error and Crash in fd * * Fedora 8/9 now set -D_FORTIFY_SOURCE=2 as default compiler option. This will probably be true on other platforms as they move to glibc = 2.7. This causes a false buffer overflow detected error and crash in bacula-fd and other executables. To avoid this problem a workaround for Redhat platforms is to set the CFLAGS in your ~/.rpmmacros file as follows: # uncomment for bacula #%__global_cflags -O2 -g -pipe -Wall -Wp,-D_FORTIFY_SOURCE=0 -fno-exceptions -fno-strict-aliasing -fno-rtti For SuSE platforms set as follows in your ~/.rpmrc file: optflags: i586 -O2 -g -m32 -march=i586 -mtune=i686 -fmessage-length=0 -D_FORTIFY_SOURCE=0 optflags: x86_64 -O2 -g -fmessage-length=0 -D_FORTIFY_SOURCE=0 See the discussion thread on bacula-devel for more information: http://sourceforge.net/search/?ml_name=bacula-develtype_of_search=mlistsgroup_id=50727words=%22buffer+overflow+detected%22 *** * bat (Bacula Admin Tool) * *** A new subpackage has been added for the new bat QT-based GUI administration tool. This requires QT = 4.2 --define build_bat 1 If you encounter problems building the bat package on platforms where you do have the proper QT4 support (QT = 4.2) it may be necessary to adjust your $QTDIR and $PATH variables. On Fedora 8/9 it was necessary to: export QTDIR=/usr/lib/qt4;export PATH=/usr/lib/qt4/bin:$PATH;rpmbuild blah... As of 2.4.4 this should no longer be necessary as we sniff the paths with pkgconfig. *** * Gnome console dropped on some platforms * *** The gconsole package has been dropped on older gnome platforms (gtk+ 2.4). Changes in the gnome api and code produced by Glade no longer build. In addition, the tray monitor now fails to build on 2.10 platforms. gconsole is now not built on the following platforms: rh7, rh8, rh9, rhel3 (and clones), fc1, fc3, fc4, mdk, su9, su10 * Third party packager support * A new build tag added to support third party packagers to replace the information in the Packager: tag in the rpm. Invoking --define contrib_packager Your Name your-emm...@site.org will substitute your packager identification. Users interested in building packages for platforms not normally published should examine the platforms/contrib-rpm directory in the source code. *** * Option to build client only * *** A build define to build the client rpm package only added. This turns off all database builds, gnome console and wxconsole. --define build_client_only 1 * Python support added * Support for compiling with python scripting support added. This is off by default but can be enabled with: --define build_python 1 Released binary packages are built with python support. *** * Database update * *** The 2.x release requires an update to the bacula database structure from version 9 to version 10
[Bacula-users] bacula-2.4.3 rpm release
Bacula-2.4 RPM Release Notes 11 Octover 2008 D. Scott Barninger barninger at fairfieldcomputers dot com Release 2.4.3-1 This release incorporates a number of significant changes since 1.38. These release notes refer to the rpm packaging only. Please refer to the release notes and changelog in the tarball or on sourceforge for complete information on all changes. This release is to correct a dependency in the bat package for FC8/9 only. * * Miscellaneous * * Added nobuild_rescue switch to supress building the rescue package Removed libtermcap dependency for fc9 Added build target for su110 Added build target for fc9 File location changes for compatibility with FHS. Force stripping of binaries for SuSE packages. Fixed bug 1037. Added nobuild_mtx switch to supress build of mtx package. Added missing files now required by the rescue configure script. Corrected dist target for rhel5. Corrected QT dependency name for RedHat flavors. Added fix for RHEL5 64 bit QT paths. Added build target for su103. Added build targets for rhel5 and clones. Build target added for Scientific Linux (RHEL clone) thanks to Jon Peatfield. Merged Otto Mueller's patch changing some directory locations for FHS compatibility but retaining the script directory as /etc/bacula. gnome-console and wxconsole have been renamed to bgnome-console and bwx-console respectively. *** * New Build Option to Install in Single Directory * *** A new build define has been added which will build packages that install most of the files to /opt/bacula. Only the man pages, init scripts, logwatch and menu entries are installed to the root filesystem. --define single_dir_install 1 * * Buffer Overflow Error and Crash in fd * * Fedora 8/9 now set -D_FORTIFY_SOURCE=2 as default compiler option. This will probably be true on other platforms as they move to glibc = 2.7. This causes a false buffer overflow detected error and crash in bacula-fd and other executables. To avoid this problem a workaround for Redhat platforms is to set the CFLAGS in your ~/.rpmmacros file as follows: # uncomment for bacula #%__global_cflags -O2 -g -pipe -Wall -Wp,-D_FORTIFY_SOURCE=0 -fno-exceptions -fno-strict-aliasing -fno-rtti For SuSE platforms set as follows in your ~/.rpmrc file: optflags: i586 -O2 -g -m32 -march=i586 -mtune=i686 -fmessage-length=0 -D_FORTIFY_SOURCE=0 optflags: x86_64 -O2 -g -fmessage-length=0 -D_FORTIFY_SOURCE=0 See the discussion thread on bacula-devel for more information: http://sourceforge.net/search/?ml_name=bacula-develtype_of_search=mlistsgroup_id=50727words=%22buffer+overflow+detected%22 *** * bat (Bacula Admin Tool) * *** A new subpackage has been added for the new bat QT-based GUI administration tool. This requires QT = 4.2 --define build_bat 1 If you encounter problems building the bat package on platforms where you do have the proper QT4 support (QT = 4.2) it may be necessary to adjust your $QTDIR and $PATH variables. On Fedora 8/9 it was necessary to: export QTDIR=/usr/lib/qt4;export PATH=/usr/lib/qt4/bin:$PATH;rpmbuild blah... *** * Gnome console dropped on some platforms * *** The gconsole package has been dropped on older gnome platforms (gtk+ 2.4). Changes in the gnome api and code produced by Glade no longer build. In addition, the tray monitor now fails to build on 2.10 platforms. gconsole is now not built on the following platforms: rh7, rh8, rh9, rhel3 (and clones), fc1, fc3, fc4, mdk, su9, su10 * Third party packager support * A new build tag added to support third party packagers to replace the information in the Packager: tag in the rpm. Invoking --define contrib_packager Your Name [EMAIL PROTECTED] will substitute your packager identification. Users interested in building packages for platforms not normally published should examine the platforms/contrib-rpm directory in the source code. *** * Option to build client only * *** A build define to build the client rpm package only added. This turns off all database builds, gnome console and wxconsole. --define build_client_only 1 * Python support added * Support for compiling with python scripting support added. This is off by default but can be enabled with: --define build_python 1 Released binary packages are built with python support. *** * Database update * *** The 2.x release requires an update to the bacula database structure from version 9 to version 10. A pre-install routine has been added
Re: [Bacula-users] [Bacula-devel] [Fwd: Re: bacula : about the bacula.spec formrpms]
On Mon, 2008-03-03 at 09:35 -0500, David Boyes wrote: There are standards such as FHS, and these are good and useful for most programs, but they really do a big disservice to Bacula users when we are dealing with recovery. If you spread the Bacula installation all around your computer filesystem as most packages do and as the standards specify, and your system is a server and the server goes down (loses the harddisk), you will find it next to impossible to restore that server -- very few people think about this. What I am saying here applies to a Bacula server (Director, SD) and not clients. Adherence to the filesystem standards is important in that many enterprises require their use where such standards exist, and the key point here is to preserve the various configuration files and information, not the location of the binaries. I don't really care where the binaries are as long as the configuration and database is completely captured; in fact, if I'm restoring at a DR site, I may not have the same release or version that I have at home, but if I have the configuration, I have the necessary -- perhaps not optimal, but *necessary* -- pieces to put my environment back together. If Bacula is going to play in the big leagues, there isn't any excuse for dodging the standards, period. It may not be perfect, but it's the Way Things Are Done, and deviants are excluded from playing; in fact, the current setup requires some justification as it deviates from the FHS in minor ways, which has delayed getting Bacula available to other parts of the organization with more stringent requirements. So this deviation would be eliminated by: 1. changing %script_dir to %_libdir/bacula 2. changing the installed location of the rescue files from %sysconf_dir to %script_dir? FHS is the right way to do this on Linux, and there are similar recommended setups for AIX, Solaris, etc. Don't invent something different -- in enterprises, different == bad. -- db - This SF.net email is sponsored by: Microsoft Defy all challenges. Microsoft(R) Visual Studio 2008. http://clk.atdmt.com/MRT/go/vse012070mrt/direct/01/ ___ Bacula-users mailing list Bacula-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/bacula-users
Re: [Bacula-users] [Bacula-devel] [Fwd: Re: bacula : about the bacula.spec formrpms]
OK, so what would you all like me to do? Yes there are standards for things like /usr/local/... but that would I think introduce some path problems? Personally I think the official rpms should be FHS compliant for reasons that David Boyes articulated. He is quite correct about large enterprise IT departments. I could have you buy me beers for an entire evening and regale you with stupid IT stories from US Airways. Rigidity doesn't even come close to describing it. Anyone who wishes to do differently can either modify my spec file or build from source. Thoughts? On Mon, 2008-03-03 at 22:13 +0100, Kern Sibbald wrote: Everyone is perfectly free to put files where they want and regardless of what I recommend, they are going to continue to be installed on Linux as is the current habit. I was just reminding users that installing Bacula they way most Linux programs are packaged is not ideal when it comes to recovering a server. You can take or leave my advice, but many sys admins do it my way. Most Unix systems tend to put programs into their own directory (there *are* standards for the directory locations) rather than spreading the parts all over your filesystem. The extreme of spraying files all over the place is Windows, Linux is somewhere in the middle, and Unix for add-on packages is much better (IMO). - This SF.net email is sponsored by: Microsoft Defy all challenges. Microsoft(R) Visual Studio 2008. http://clk.atdmt.com/MRT/go/vse012070mrt/direct/01/ ___ Bacula-users mailing list Bacula-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/bacula-users
Re: [Bacula-users] [Bacula-devel] buffer overflow detected error on fedora distributions.
Hello, For those of you following this discussion, or who may have had problems building 2.2.8 on systems with glibc 2.7+, I have released bacula-2.2.8-2 rpm packages. This release includes a new source rpm as well as Fedora 8 binaries which tested OK for me. This fix should work for any platform which experienced this problem. Bacula-2.2 RPM Release Notes 09 February 2008 D. Scott Barninger barninger at fairfieldcomputers dot com Release 2.2.8-2 These release notes refer to the rpm packaging only. Please refer to the release notes and changelog in the tarball or on sourceforge for complete information on all changes. * * Miscellaneous * * Correction for FORTIFY_SOURCE flag default setting that causes false buffer overflow detection with glibc = 2.7 (Fedora 8). - This SF.net email is sponsored by: Microsoft Defy all challenges. Microsoft(R) Visual Studio 2008. http://clk.atdmt.com/MRT/go/vse012070mrt/direct/01/ ___ Bacula-users mailing list Bacula-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/bacula-users
[Bacula-users] bacula-2.2.8 rpm release
Bacula-2.2 RPM Release Notes 27 January 2008 D. Scott Barninger barninger at fairfieldcomputers dot com Release 2.2.8-1 This release incorporates a number of significant changes since 1.38. These release notes refer to the rpm packaging only. Please refer to the release notes and changelog in the tarball or on sourceforge for complete information on all changes. * * Miscellaneous * * Force stripping of binaries for SuSE packages. Fixed bug 1037. Added nobuild_mtx switch to surpress build of mtx package. Added missing files now required by the rescue configure script. Corrected dist target for rhel5. Corrected QT dependency name for RedHat flavors. Added fix for RHEL5 64 bit QT paths. Added build target for su103. Added build targets for rhel5 and clones. Build target added for Scientific Linux (RHEL clone) thanks to Jon Peatfield. Merged Otto Mueller's patch changing some directory locations for FHS compatibility but retaining the script directory as /etc/bacula. gnome-console and wxconsole have been renamed to bgnome-console and bwx-console respectively. *** * bat (Bacula Admin Tool) * *** A new subpackage has been added for the new bat QT-based GUI administration tool. This requires QT = 4.2 --define build_bat 1 If you encounter problems building the bat package on platforms where you do have the proper QT4 support (QT = 4.2) it may be necessary to adjust your $QTDIR and $PATH variables. On Fedora 8 it was necessary to: export QTDIR=/usr/lib/qt4;export PATH=/usr/lib/qt4/bin:$PATH;rpmbuild blah... *** * Gnome console dropped on some platforms * *** The gconsole package has been dropped on older gnome platforms (gtk+ 2.4). Changes in the gnome api and code produced by Glade no longer build. In addition, the tray monitor now fails to build on 2.10 platforms. gconsole is now not built on the following platforms: rh7, rh8, rh9, rhel3 (and clones), fc1, fc3, fc4, mdk, su9, su10 * Third party packager support * A new build tag added to support third party packagers to replace the information in the Packager: tag in the rpm. Invoking --define contrib_packager Your Name [EMAIL PROTECTED] will substitute your packager identification. Users interested in building packages for platforms not normally published should examine the platforms/contrib-rpm directory in the source code. *** * Option to build client only * *** A build define to build the client rpm package only added. This turns off all database builds, gnome console and wxconsole. --define build_client_only 1 * Python support added * Support for compiling with python scripting support added. This is off by default but can be enabled with: --define build_python 1 Released binary packages are built with python support. *** * Database update * *** The 2.x release requires an update to the bacula database structure from version 9 to version 10. A pre-install routine has been added to check for databases older than 9. In that event the install will exit with an error message indicating that the database must be updated to version 9 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 9 database is detected a post-install routine will update the database after creating a backup file in the bacula working directory. ** * SQLite Upgrade * ** For users of the sqlite package, from 2.2.7 onward sqlite3 replaces sqlite2. Your sqlite2 database file (/var/lib/bacula/bacula.db) is not compatible with sqlite3. During an upgrade the pre-install script will check for this situation. If found it will dump your catalog data to the file /var/lib/bacula/bacula_backup.sql, rename your old catalog file to /var/lib/bacula/bacula.db.old, and exit. You should then re-run the rpm upgrade. After the upgrade is complete restore your catalog data with the following commands (as root): /etc/bacula/drop_sqlite3_tables cd /var/lib/bacula /usr/lib/bacula/sqlite/sqlite3 $* bacula.db bacula_backup.sql chown bacula.bacula bacula.db ** * Platform Notes * ** The spec file currently supports building on the following platforms: # RedHat builds --define build_rh7 1 --define build_rh8 1 --define build_rh9 1 # Fedora Core build --define build_fc1 1 --define build_fc3 1 --define build_fc4 1 --define build_fc5 1 --define build_fc6 1 --define build_fc7 1 --define build_fc8 1 # Whitebox Enterprise build --define build_wb3 1 # RedHat Enterprise builds --define build_rhel3 1 --define build_rhel4 1 --define build_rhel5
[Bacula-users] Attn: sqlite users 2.2.7 upgrade
Hello, Please note that I committed a typographical error in the release notes published previously. When restoring your catalog database I indicated the command: /usr/lib/bacula/sqlite3 $* bacula.db bacula_backup.sql which should have been: /usr/lib/bacula/sqlite/sqlite3 $* bacula.db bacula_backup.sql Sorry about that. - This SF.net email is sponsored by: Microsoft Defy all challenges. Microsoft(R) Visual Studio 2005. http://clk.atdmt.com/MRT/go/vse012070mrt/direct/01/ ___ Bacula-users mailing list Bacula-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/bacula-users
Re: [Bacula-users] [Bacula-devel] Fwd: Broken 2.2.6 source rpm in Sourceforge
This sounds like the same issue I had today building 2.2.7 on Fedora 8. I had to do the following: export QTDIR=/usr/lib/qt4;export PATH=/usr/lib/qt4/bin:$PATH;rpmbuild blah... On Tue, 2007-11-20 at 16:46 -0500, Jeff Dickens wrote: Was a build with Bat enabled on CentOS 5 expected to work ? I couldn't get it to work. I had various problems around finding qt4 and/or qwt.Even building without rpmbuild it couldn't find qmake until I tweaked the path and then it didn't install the bat binary. If you want I can clean up and try it again and send you a log. Scott Barninger wrote: Hello All, I see from SF stats that there have been 92 downloads since I re-posted the SRPM last Friday. Can I assume all of the issues noted have been addressed? I ask because later this week I intend to post a special 2.2.6 to the beta-rpm section for upgrade from sqlite to sqlite3 for testing. Regards, Scott - This SF.net email is sponsored by: Microsoft Defy all challenges. Microsoft(R) Visual Studio 2005. http://clk.atdmt.com/MRT/go/vse012070mrt/direct/01/ ___ Bacula-users mailing list Bacula-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/bacula-users - This SF.net email is sponsored by: Microsoft Defy all challenges. Microsoft(R) Visual Studio 2005. http://clk.atdmt.com/MRT/go/vse012070mrt/direct/01/ ___ Bacula-users mailing list Bacula-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/bacula-users
[Bacula-users] bacula-2.2.7 rpm release
Hello, 2.2.7 rpm release is up on sourceforge. Four items of note, see below for details. 1. Build of bat may present problems on some platforms that do have qt = 4.2, particularly redhat in my experience. 2. Older postgresql versions fail to build after changes committed for postgresql-8.3. I have included a patch. 3. Per Alan Brown's request, I have added a switch to suppress build of mtx package. 4. For SQLite users please note the upgrade to sqlite3. --- Bacula-2.2 RPM Release Notes 28 December 2007 D. Scott Barninger barninger at fairfieldcomputers dot com Release 2.2.7-1 This release incorporates a number of significant changes since 1.38. These release notes refer to the rpm packaging only. Please refer to the release notes and changelog in the tarball or on sourceforge for complete information on all changes. * * Miscellaneous * * The 2.2.7 postgresql package failed to compile on EL3. This may also occur on older postgresql versions in other platforms. A patch has been added to fix the problem. It is triggered by all el3 platforms. You can trigger it if necessary on other platforms with: --define build_old_pgsql 1 Added nobuild_mtx switch to surpress build of mtx package. Added missing files now required by the rescue configure script. Corrected dist target for rhel5. Corrected QT dependency name for RedHat flavors. Added fix for RHEL5 64 bit QT paths. Added build target for su103. Added build targets for rhel5 and clones. Build target added for Scientific Linux (RHEL clone) thanks to Jon Peatfield. Merged Otto Mueller's patch changing some directory locations for FHS compatibility but retaining the script directory as /etc/bacula. gnome-console and wxconsole have been renamed to bgnome-console and bwx-console respectively. *** * bat (Bacula Admin Tool) * *** A new subpackage has been added for the new bat QT-based GUI administration tool. This requires QT = 4.2 --define build_bat 1 If you encounter problems building the bat package on platforms where you do have the proper QT4 support (QT = 4.2) it may be necessary to adjust your $QTDIR and $PATH variables. On Fedora 8 it was necessary to: export QTDIR=/usr/lib/qt4;export PATH=/usr/lib/qt4/bin:$PATH;rpmbuild blah... *** * Gnome console dropped on some platforms * *** The gconsole package has been dropped on older gnome platforms (gtk+ 2.4). Changes in the gnome api and code produced by Glade no longer build. In addition, the tray monitor now fails to build on 2.10 platforms. gconsole is now not built on the following platforms: rh7, rh8, rh9, rhel3 (and clones), fc1, fc3, fc4, mdk, su9, su10 * Third party packager support * A new build tag added to support third party packagers to replace the information in the Packager: tag in the rpm. Invoking --define contrib_packager Your Name [EMAIL PROTECTED] will substitute your packager identification. Users interested in building packages for platforms not normally published should examine the platforms/contrib-rpm directory in the source code. *** * Option to build client only * *** A build define to build the client rpm package only added. This turns off all database builds, gnome console and wxconsole. --define build_client_only 1 * Python support added * Support for compiling with python scripting support added. This is off by default but can be enabled with: --define build_python 1 Released binary packages are built with python support. *** * Database update * *** The 2.x release requires an update to the bacula database structure from version 9 to version 10. A pre-install routine has been added to check for databases older than 9. In that event the install will exit with an error message indicating that the database must be updated to version 9 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 9 database is detected a post-install routine will update the database after creating a backup file in the bacula working directory. ** * SQLite Upgrade * ** For users of the sqlite package, from 2.2.7 onward sqlite3 replaces sqlite2. Your sqlite2 database file (/var/lib/bacula/bacula.db) is not compatible with sqlite3. During an upgrade the pre-install script will check for this situation. If found it will dump your catalog data to the file /var/lib/bacula/bacula_backup.sql, rename your old catalog file to /var/lib/bacula/bacula.db.old, and exit. You should then re-run the rpm
Re: [Bacula-users] [Bacula-devel] Fwd: Broken 2.2.6 source rpm in Sourceforge
Hello All, I see from SF stats that there have been 92 downloads since I re-posted the SRPM last Friday. Can I assume all of the issues noted have been addressed? I ask because later this week I intend to post a special 2.2.6 to the beta-rpm section for upgrade from sqlite to sqlite3 for testing. Regards, Scott - This SF.net email is sponsored by: Microsoft Defy all challenges. Microsoft(R) Visual Studio 2005. http://clk.atdmt.com/MRT/go/vse012070mrt/direct/01/ ___ Bacula-users mailing list Bacula-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/bacula-users
Re: [Bacula-users] [Bacula-devel] Fwd: Broken 2.2.6 source rpm in Sourceforge
What command string are you using to build? On Fri, 2007-11-16 at 07:35 +0200, Timo Neuvonen wrote: Scott Barninger [EMAIL PROTECTED] kirjoitti viestissä news:[EMAIL PROTECTED] Sorry for the delay but I have been out of town until this evening. Not sure what went wrong with the release but I have re-uploaded the srpm now. It should be available now and the file size looks correct. Yes, the size looks correct now... but this time I keep getting this message when trying to build binaries on FC6 and CentOS5: error: syntax error in expression error: /usr/src/redhat/SPECS/bacula.spec:298: parseExpressionBoolean returns -1 error: Package has no %description: bacula Regards, Timo - This SF.net email is sponsored by: Microsoft Defy all challenges. Microsoft(R) Visual Studio 2005. http://clk.atdmt.com/MRT/go/vse012070mrt/direct/01/ ___ Bacula-devel mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/bacula-devel - This SF.net email is sponsored by: Microsoft Defy all challenges. Microsoft(R) Visual Studio 2005. http://clk.atdmt.com/MRT/go/vse012070mrt/direct/01/ ___ Bacula-users mailing list Bacula-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/bacula-users
Re: [Bacula-users] [Bacula-devel] Fwd: Broken 2.2.6 source rpm in Sourceforge
On Fri, 2007-11-16 at 07:35 +0200, Timo Neuvonen wrote: Scott Barninger [EMAIL PROTECTED] kirjoitti viestissä news:[EMAIL PROTECTED] Sorry for the delay but I have been out of town until this evening. Not sure what went wrong with the release but I have re-uploaded the srpm now. It should be available now and the file size looks correct. Yes, the size looks correct now... but this time I keep getting this message when trying to build binaries on FC6 and CentOS5: error: syntax error in expression error: /usr/src/redhat/SPECS/bacula.spec:298: parseExpressionBoolean returns -1 error: Package has no %description: bacula I have replaced the file on sourceforge. Regards, Timo - This SF.net email is sponsored by: Microsoft Defy all challenges. Microsoft(R) Visual Studio 2005. http://clk.atdmt.com/MRT/go/vse012070mrt/direct/01/ ___ Bacula-devel mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/bacula-devel - This SF.net email is sponsored by: Microsoft Defy all challenges. Microsoft(R) Visual Studio 2005. http://clk.atdmt.com/MRT/go/vse012070mrt/direct/01/ ___ Bacula-users mailing list Bacula-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/bacula-users
Re: [Bacula-users] Fwd: [Bacula-devel] Broken 2.2.6 source rpm in Sourceforge
Hello, Sorry for the delay but I have been out of town until this evening. Not sure what went wrong with the release but I have re-uploaded the srpm now. It should be available now and the file size looks correct. On Tue, 2007-11-13 at 14:10 +0100, Kern Sibbald wrote: Hello Scott, Just to let you know, I downloaded the 2.2.6-1.src.rpm package, and it does look like it is truncated since it is less than half the size of the 2.2.5 release, and the signature is NOT OK. As a consequence, I have deleted the package from Source Forge to avoid more users from having problems. I have a copy of the broken package here, if by any chance you should need it. Best regards, Kern -- Forwarded Message -- Subject: [Bacula-devel] Broken 2.2.6 source rpm in Sourceforge Date: Tuesday 13 November 2007 13:51 From: Timo Neuvonen [EMAIL PROTECTED] To: [EMAIL PROTECTED] bacula-2.2.6 has been released to sourceforge. This release should address the RedHat (and clone) issues discussed recently as well as introducing support for SuSE 10.3. Could someone pls. check if the bacula-2.2.6-1.src.rpm is ok? Size shown by Sourceforge is less than 8 megs, which is less than one half of 2.2.5 src rpm package... For me, the package in Sourceforge definetely seems to be broken. I've tried to download it several times, every time I get only the appr. 8 megs, which does not build to binaries... someone else mentioned this in the user list too. Regards, Timo - This SF.net email is sponsored by: Splunk Inc. Still grepping through log files to find problems? Stop. Now Search log events and configuration files using AJAX and a browser. Download your FREE copy of Splunk now http://get.splunk.com/ ___ Bacula-devel mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/bacula-devel --- - This SF.net email is sponsored by: Microsoft Defy all challenges. Microsoft(R) Visual Studio 2005. http://clk.atdmt.com/MRT/go/vse012070mrt/direct/01/ ___ Bacula-users mailing list Bacula-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/bacula-users
Re: [Bacula-users] Fwd: [Bacula-devel] Broken 2.2.6 source rpm in Sourceforge
No problem. Good thing I don't delete that trusty srpm until I build the next release :-) I hope all is well now. Coming Event Highlights: Per me, will be switching the sqlite package to sqlite3. Per Alan Brown, will be adding a build switch for the mtx package (default off). Hopefully this will be done with the next major release. On Thu, 2007-11-15 at 17:24 -0500, Jeff Dickens wrote: Thanks. Scott Barninger wrote: Hello, Sorry for the delay but I have been out of town until this evening. Not sure what went wrong with the release but I have re-uploaded the srpm now. It should be available now and the file size looks correct. On Tue, 2007-11-13 at 14:10 +0100, Kern Sibbald wrote: Hello Scott, Just to let you know, I downloaded the 2.2.6-1.src.rpm package, and it does look like it is truncated since it is less than half the size of the 2.2.5 release, and the signature is NOT OK. As a consequence, I have deleted the package from Source Forge to avoid more users from having problems. I have a copy of the broken package here, if by any chance you should need it. Best regards, Kern -- Forwarded Message -- Subject: [Bacula-devel] Broken 2.2.6 source rpm in Sourceforge Date: Tuesday 13 November 2007 13:51 From: Timo Neuvonen [EMAIL PROTECTED] To: [EMAIL PROTECTED] bacula-2.2.6 has been released to sourceforge. This release should address the RedHat (and clone) issues discussed recently as well as introducing support for SuSE 10.3. Could someone pls. check if the bacula-2.2.6-1.src.rpm is ok? Size shown by Sourceforge is less than 8 megs, which is less than one half of 2.2.5 src rpm package... For me, the package in Sourceforge definetely seems to be broken. I've tried to download it several times, every time I get only the appr. 8 megs, which does not build to binaries... someone else mentioned this in the user list too. Regards, Timo - This SF.net email is sponsored by: Splunk Inc. Still grepping through log files to find problems? Stop. Now Search log events and configuration files using AJAX and a browser. Download your FREE copy of Splunk now http://get.splunk.com/ ___ Bacula-devel mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/bacula-devel --- - This SF.net email is sponsored by: Microsoft Defy all challenges. Microsoft(R) Visual Studio 2005. http://clk.atdmt.com/MRT/go/vse012070mrt/direct/01/ ___ Bacula-users mailing list Bacula-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/bacula-users
[Bacula-users] 2.2.6 rpm release
Hello, bacula-2.2.6 has been released to sourceforge. This release should address the RedHat (and clone) issues discussed recently as well as introducing support for SuSE 10.3. The following issues have been corrected: * Sun Nov 11 2007 - add new files required by rescue makefile * Sat Nov 10 2007 - add su103 build target * Sun Nov 04 2007 - fix dist defines for rhel5 and clones - fix rhel broken 64 bit QT4 paths - rh qt4 packages don't provide qt so fix that too * Mon Oct 29 2007 - correct ownership when creating sqlite db file in post script The full release notes follow. Bacula-2.2 RPM Release Notes 11 November 2007 D. Scott Barninger barninger at fairfieldcomputers dot com Release 2.2.6-1 This release incorporates a number of significant changes since 1.38. These release notes refer to the rpm packaging only. Please refer to the release notes and changelog in the tarball or on sourceforge for complete information on all changes. * * Miscellaneous * * Added missing files now required by the rescue configure script. Corrected dist target for rhel5. Corrected QT dependency name for RedHat flavors. Added fix for RHEL5 64 bit QT paths. Added build target for su103. Added build targets for rhel5 and clones. Build target added for Scientific Linux (RHEL clone) thanks to Jon Peatfield. Merged Otto Mueller's patch changing some directory locations for FHS compatibility but retaining the script directory as /etc/bacula. gnome-console and wxconsole have been renamed to bgnome-console and bwx-console respectively. *** * bat (Bacula Admin Tool) * *** A new subpackage has been added for the new bat QT-based GUI administration tool. This requires QT = 4.2 --define build_bat 1 *** * Gnome console dropped on some platforms * *** The gconsole package has been dropped on older gnome platforms (gtk+ 2.4). Changes in the gnome api and code produced by Glade no longer build. In addition, the tray monitor now fails to build on 2.10 platforms. gconsole is now not built on the following platforms: rh7, rh8, rh9, rhel3 (and clones), fc1, fc3, fc4, mdk, su9, su10 * Third party packager support * A new build tag added to support third party packagers to replace the information in the Packager: tag in the rpm. Invoking --define contrib_packager Your Name [EMAIL PROTECTED] will substitute your packager identification. Users interested in building packages for platforms not normally published should examine the platforms/contrib-rpm directory in the source code. *** * Option to build client only * *** A build define to build the client rpm package only added. This turns off all database builds, gnome console and wxconsole. --define build_client_only 1 * Python support added * Support for compiling with python scripting support added. This is off by default but can be enabled with: --define build_python 1 Released binary packages are built with python support. *** * Database update * *** The 2.x release requires an update to the bacula database structure from version 9 to version 10. A pre-install routine has been added to check for databases older than 9. In that event the install will exit with an error message indicating that the database must be updated to version 9 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 9 database is detected a post-install routine will update the database after creating a backup file in the bacula working directory. ** * Platform Notes * ** The spec file currently supports building on the following platforms: # RedHat builds --define build_rh7 1 --define build_rh8 1 --define build_rh9 1 # Fedora Core build --define build_fc1 1 --define build_fc3 1 --define build_fc4 1 --define build_fc5 1 --define build_fc6 1 # Whitebox Enterprise build --define build_wb3 1 # RedHat Enterprise builds --define build_rhel3 1 --define build_rhel4 1 --define build_rhel5 1 # CentOS build --define build_centos3 1 --define build_centos4 1 --define build_centos5 1 # Scientific Linux build --define build_sl3 1 --define build_sl4 1 --define build_sl5 1 # SuSE build --define build_su9 1 --define build_su10 1 --define build_su102 1 --define build_su103 1 # Mandrake 10.x build --define build_mdk 1 # Mandriva build --define build_mdv 1 ** * Database build options * ** Database support (must select one or build client only) MySQL support: --define build_mysql 1 # OR if using mysql 4.x define this # currently: Mandrake 10.x
[Bacula-users] bacula-2.2.4 rpm release
I have released the rpm package for 2.2.4 to sourceforge. One item of note is that I did not release a bacula-mysql package for rhel3 due to a problem with the current code and mysql-3.23.x. Bacula-2.2 RPM Release Notes 15 September 2007 D. Scott Barninger barninger at fairfieldcomputers dot com Release 2.2.4-1 This release incorporates a number of significant changes since 1.38. These release notes refer to the rpm packaging only. Please refer to the release notes and changelog in the tarball or on sourceforge for complete information on all changes. * * Miscellaneous * * Added build targets for rhel5 and clones. Build target added for Scientific Linux (RHEL clone) thanks to Jon Peatfield. Merged Otto Mueller's patch changing some directory locations for FHS compatibility but retaining the script directory as /etc/bacula. gnome-console and wxconsole have been renamed to bgnome-console and bwx-console respectively. *** * bat (Bacula Admin Tool) * *** A new subpackage has been added for the new bat QT-based GUI administration tool. This requires QT = 4.2 --define build_bat 1 *** * Gnome console dropped on some platforms * *** The gconsole package has been dropped on older gnome platforms (gtk+ 2.4). Changes in the gnome api and code produced by Glade no longer build. In addition, the tray monitor now fails to build on 2.10 platforms. gconsole is now not built on the following platforms: rh7, rh8, rh9, rhel3 (and clones), fc1, fc3, fc4, mdk, su9, su10 * Third party packager support * A new build tag added to support third party packagers to replace the information in the Packager: tag in the rpm. Invoking --define contrib_packager Your Name [EMAIL PROTECTED] will substitute your packager identification. Users interested in building packages for platforms not normally published should examine the platforms/contrib-rpm directory in the source code. *** * Option to build client only * *** A build define to build the client rpm package only added. This turns off all database builds, gnome console and wxconsole. --define build_client_only 1 * Python support added * Support for compiling with python scripting support added. This is off by default but can be enabled with: --define build_python 1 Released binary packages are built with python support. *** * Database update * *** The 2.x release requires an update to the bacula database structure from version 9 to version 10. A pre-install routine has been added to check for databases older than 9. In that event the install will exit with an error message indicating that the database must be updated to version 9 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 9 database is detected a post-install routine will update the database after creating a backup file in the bacula working directory. ** * Platform Notes * ** The spec file currently supports building on the following platforms: # RedHat builds --define build_rh7 1 --define build_rh8 1 --define build_rh9 1 # Fedora Core build --define build_fc1 1 --define build_fc3 1 --define build_fc4 1 --define build_fc5 1 --define build_fc6 1 # Whitebox Enterprise build --define build_wb3 1 # RedHat Enterprise builds --define build_rhel3 1 --define build_rhel4 1 --define build_rhel5 1 # CentOS build --define build_centos3 1 --define build_centos4 1 --define build_centos5 1 # Scientific Linux build --define build_sl3 1 --define build_sl4 1 --define build_sl5 1 # SuSE build --define build_su9 1 --define build_su10 1 --define build_su102 1 # Mandrake 10.x build --define build_mdk 1 # Mandriva build --define build_mdv 1 ** * Database build options * ** Database support (must select one or build client only) MySQL support: --define build_mysql 1 # OR if using mysql 4.x define this # currently: Mandrake 10.x, SuSE 9.x 10.0, RHEL4, fc4 --define build_mysql4 1 # OR if using mysql 5.x define this # currently: SuSE 10.1, fc5 --define build_mysql5 1 PostgreSQL support: --define build_postgresql 1 Sqlite support: --define build_sqlite 1 *** * Other build options * *** Supress build of Gnome Console: --define nobuild_gconsole 1 Enable X86-64 support --define build_x86_64 1 This build switch remains but should no longer be necessary. The configure script was adjusted in the 1.39 development series to correctly detect the location of 64 bit libraries. Enable wxconsole: --define build_wxconsole 1
[Bacula-users] bacula-2.2.1 rpm release
Bacula 2.2.1 rpm has been released to sourceforge. Notable issues: The tray monitor no longer builds on EL3 or FC4, thus the gconsole package is now deprecated on those platforms. The postgresql server package fails to build on EL3. This may be fixed in future releases. Bacula-2.2 RPM Release Notes 03 September 2007 D. Scott Barninger barninger at fairfieldcomputers dot com Release 2.2.1-1 This release incorporates a number of significant changes since 1.38. These release notes refer to the rpm packaging only. Please refer to the release notes and changelog in the tarball or on sourceforge for complete information on all changes. * * Miscellaneous * * Build target added for Scientific Linux (RHEL clone) thanks to Jon Peatfield. Merged Otto Mueller's patch changing some directory locations for FHS compatibility but retaining the script directory as /etc/bacula. gnome-console and wxconsole have been renamed to bgnome-console and bwx-console respectively. * First release of bat (Bacula Admin Tool) * A new subpackage has been added for the new bat QT-based GUI administration tool. This requires QT = 4.2 --define build_bat 1 *** * Gnome console dropped on some platforms * *** The gconsole package has been dropped on older gnome platforms (gtk+ 2.4). Changes in the gnome api and code produced by Glade no longer build. In addition, the tray monitor now fails to build on some 2.4 platforms. gconsole is now not built on the following platforms: rh7, rh8, rh9, rhel3 (and clones), fc1, fc4, mdk, su9, su10 * Third party packager support * A new build tag added to support third party packagers to replace the information in the Packager: tag in the rpm. Invoking --define contrib_packager Your Name [EMAIL PROTECTED] will substitute your packager identification. Users interested in building packages for platforms not normally published should examine the platforms/contrib-rpm directory in the source code. *** * Option to build client only * *** A build define to build the client rpm package only added. This turns off all database builds, gnome console and wxconsole. --define build_client_only 1 * Python support added * Support for compiling with python scripting support added. This is off by default but can be enabled with: --define build_python 1 Released binary packages are built with python support. *** * Database update * *** The 2.x release requires an update to the bacula database structure from version 9 to version 10. A pre-install routine has been added to check for databases older than 9. In that event the install will exit with an error message indicating that the database must be updated to version 9 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 9 database is detected a post-install routine will update the database after creating a backup file in the bacula working directory. ** * Platform Notes * ** The spec file currently supports building on the following platforms: # RedHat builds --define build_rh7 1 --define build_rh8 1 --define build_rh9 1 # Fedora Core build --define build_fc1 1 --define build_fc3 1 --define build_fc4 1 --define build_fc5 1 --define build_fc6 1 # Whitebox Enterprise build --define build_wb3 1 # RedHat Enterprise builds --define build_rhel3 1 --define build_rhel4 1 # CentOS build --define build_centos3 1 --define build_centos4 1 # Scientific Linux build --define build_sl3 1 --define build_sl4 1 # SuSE build --define build_su9 1 --define build_su10 1 --define build_su102 1 # Mandrake 10.x build --define build_mdk 1 # Mandriva build --define build_mdv 1 ** * Database build options * ** Database support (must select one or build client only) MySQL support: --define build_mysql 1 # OR if using mysql 4.x define this # currently: Mandrake 10.x, SuSE 9.x 10.0, RHEL4, fc4 --define build_mysql4 1 # OR if using mysql 5.x define this # currently: SuSE 10.1, fc5 --define build_mysql5 1 PostgreSQL support: --define build_postgresql 1 Sqlite support: --define build_sqlite 1 *** * Other build options * *** Supress build of Gnome Console: --define nobuild_gconsole 1 Enable X86-64 support --define build_x86_64 1 This build switch remains but should no longer be necessary. The configure script was adjusted in the 1.39 development series to correctly detect the location of 64 bit libraries. Enable wxconsole
Re: [Bacula-users] [Bacula-devel] bacula-2.2.1 rpm release
On Tue, 2007-09-04 at 12:28 +0300, Timo Neuvonen wrote: Bacula-2.2 RPM Release Notes 03 September 2007 The spec file currently supports building on the following platforms: # Whitebox Enterprise build --define build_wb3 1 # RedHat Enterprise builds --define build_rhel3 1 --define build_rhel4 1 # CentOS build --define build_centos3 1 --define build_centos4 1 # Scientific Linux build --define build_sl3 1 --define build_sl4 1 Seems to build (haven't tested yet how it runs) on CentOS5 too, when asked to build for CentOS4. But does not, if asking for RHEL4 This leads to question, if it is really necessary to have separate build options for all the clones of one upstream distribution? AFAIK, there should be no functional differencies between RHELx and CentOSx... just minor changes to cope with trademark issues etc. Scientific Linux was something I had never heard before. Now, I'm just wondering wouldn't it be more simple to add just one more_tolerant option that effectively would bypass the platform test, instead of having options of their own for each of the clones? The platform tests exist primarily to get the correct package names and versions in the dependencies, and secondarily to pull the distribution string from the release file to absolutely label the package with the platform it was built on. I plan to add the rhel5 and clone tags in the near future. Sooner or later, someone will again release one more exact copy of another distribution, but just due to a different name it won't be possible to build on that system then. Or is there really a need to check the platform so strictly? Regards, Timo - This SF.net email is sponsored by: Splunk Inc. Still grepping through log files to find problems? Stop. Now Search log events and configuration files using AJAX and a browser. Download your FREE copy of Splunk now http://get.splunk.com/ ___ Bacula-devel mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/bacula-devel - This SF.net email is sponsored by: Microsoft Defy all challenges. Microsoft(R) Visual Studio 2005. http://clk.atdmt.com/MRT/go/vse012070mrt/direct/01/ ___ Bacula-users mailing list Bacula-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/bacula-users
Re: [Bacula-users] [Bacula-devel] Bacula version 2.2.3 released to Source Forge
Hello All, I have released the source RPM as well as the binaries for SuSE-10.2-i586 on sourceforge. I apologize but will be unable to release the other binaries I usually publish until this weekend due to time constraints. Other platforms should build from the SRPM if you are in need of immediate action. Of note is that we fixed the bug preventing postgresql from building on rhel3 and similar old platforms and I added build targets for rhel5 and clones. My release notes below. ps. the spec file currently in svn for trunk and Branch-2.2 has been updated to correct a typo at line 199. Bacula-2.2 RPM Release Notes 10 September 2007 D. Scott Barninger barninger at fairfieldcomputers dot com Release 2.2.3-1 This release incorporates a number of significant changes since 1.38. These release notes refer to the rpm packaging only. Please refer to the release notes and changelog in the tarball or on sourceforge for complete information on all changes. * * Miscellaneous * * Added build targets for rhel5 and clones. Build target added for Scientific Linux (RHEL clone) thanks to Jon Peatfield. Merged Otto Mueller's patch changing some directory locations for FHS compatibility but retaining the script directory as /etc/bacula. gnome-console and wxconsole have been renamed to bgnome-console and bwx-console respectively. *** * bat (Bacula Admin Tool) * *** A new subpackage has been added for the new bat QT-based GUI administration tool. This requires QT = 4.2 --define build_bat 1 *** * Gnome console dropped on some platforms * *** The gconsole package has been dropped on older gnome platforms (gtk+ 2.4). Changes in the gnome api and code produced by Glade no longer build. In addition, the tray monitor now fails to build on some 2.4 platforms. gconsole is now not built on the following platforms: rh7, rh8, rh9, rhel3 (and clones), fc1, fc4, mdk, su9, su10 * Third party packager support * A new build tag added to support third party packagers to replace the information in the Packager: tag in the rpm. Invoking --define contrib_packager Your Name [EMAIL PROTECTED] will substitute your packager identification. Users interested in building packages for platforms not normally published should examine the platforms/contrib-rpm directory in the source code. *** * Option to build client only * *** A build define to build the client rpm package only added. This turns off all database builds, gnome console and wxconsole. --define build_client_only 1 * Python support added * Support for compiling with python scripting support added. This is off by default but can be enabled with: --define build_python 1 Released binary packages are built with python support. *** * Database update * *** The 2.x release requires an update to the bacula database structure from version 9 to version 10. A pre-install routine has been added to check for databases older than 9. In that event the install will exit with an error message indicating that the database must be updated to version 9 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 9 database is detected a post-install routine will update the database after creating a backup file in the bacula working directory. ** * Platform Notes * ** The spec file currently supports building on the following platforms: # RedHat builds --define build_rh7 1 --define build_rh8 1 --define build_rh9 1 # Fedora Core build --define build_fc1 1 --define build_fc3 1 --define build_fc4 1 --define build_fc5 1 --define build_fc6 1 # Whitebox Enterprise build --define build_wb3 1 # RedHat Enterprise builds --define build_rhel3 1 --define build_rhel4 1 --define build_rhel5 1 # CentOS build --define build_centos3 1 --define build_centos4 1 --define build_centos5 1 # Scientific Linux build --define build_sl3 1 --define build_sl4 1 --define build_sl5 1 # SuSE build --define build_su9 1 --define build_su10 1 --define build_su102 1 # Mandrake 10.x build --define build_mdk 1 # Mandriva build --define build_mdv 1 ** * Database build options * ** Database support (must select one or build client only) MySQL support: --define build_mysql 1 # OR if using mysql 4.x define this # currently: Mandrake 10.x, SuSE 9.x 10.0, RHEL4, fc4 --define build_mysql4 1 # OR if using mysql 5.x define this # currently: SuSE 10.1, fc5 --define build_mysql5 1 PostgreSQL support: --define build_postgresql 1 Sqlite support: --define build_sqlite 1
[Bacula-users] Recent discussions re: binaries, donations, etc.
Hello All, For those on the lists who do not know me, I am the primary packaging manager for bacula linux binaries. I am the primary commit person on the rpm spec file as well as building *many* release files and managing contributions from other folks for platforms I don't build directly. I have also in the past produced Windows binaries and may do so again in the future. I'm not sure. I began my involvement with this project on 3/30/2003 with the initial incarnation of the rpm spec file. I have received feedback in the past from companies and distributions praising the multi-platform approach we have taken with that spec file. I think there are very few projects out there that out of the box will build to the number of platforms that we do. And I spend a lot of effort to keep that up to date and growing with the help of many contributors on rpm based platforms. Many other folks do the same for BSD, Debian etc. bacula has come a long way in that time due to the contributions of *many* people and still has some way to go in some regards vs. comparable commercial software. In some ways it excels that very same commercial software. This is the essence of open source software. It is a commons that we develop collaboratively, and knowledge and capability advances in the same way that science in general advances. So where does this leave us in the present discussion? I work my primary job as a Director for USAirways. As such I am involved in many projects that include software. My position/expertise is in fleet management so I am involved with a particular commercial software package that I will not name, but suffice to say that it is business critical and costs the company a *lot* of money, both in terms of license fees and maintenance and support fees. A recent proposal to our finance department to implement a reporting module was in the neighborhood of one quarter million dollars. You read that right and now ask yourself how useful is a database driven application where the reporting capability is such a priced option. My point is this. We all do this in an effort to provide a service and advance the general art. If we are to continue in the long run we need the support of those who utilize the efforts. If you are a private user we welcome you at no charge. If you are a commercial enterprise then please contemplate contributing a portion of what you save by accessing the commons. Otherwise the golden egg goose will not likely survive. As bacula moves into the enterprise mainstream there will be more and more requests for features and support. The way to do this consequent with the OSS model is that we need to generate an income stream to the project in some way, thus hire developers to build upon what is contributed. Kern and the other core developers can not do this alone. Neither can Linus do it with the kernel. IBM gets this. Others do not. Regards, Scott - This SF.net email is sponsored by DB2 Express Download DB2 Express C - the FREE version of DB2 express and take control of your XML. No limits. Just data. Click to get it now. http://sourceforge.net/powerbar/db2/ ___ Bacula-users mailing list Bacula-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/bacula-users
[Bacula-users] Possible RPM documentation change
Good Afternoon, As I sat here earlier watching the 39 MB SRPM (30 MB of which is the docs tarball) for 2.1.18 crawl it's way up to sourceforge I began to wonder if it is not time for a change. The documentation package has grown substantially since the change to latex and I'm only packaging the pdf manuals and the html manual. But the entire doc source tarball is still a source in the packages. So I'm thinking about changing that and making only the pdf manuals (user and developer) actual sources in the RPM package. - This SF.net email is sponsored by DB2 Express Download DB2 Express C - the FREE version of DB2 express and take control of your XML. No limits. Just data. Click to get it now. http://sourceforge.net/powerbar/db2/ ___ Bacula-users mailing list Bacula-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/bacula-users
Re: [Bacula-users] [Bacula-devel] Possible RPM documentation change
On Sun, 2007-06-17 at 12:32 -0400, Dan Langille wrote: On 17 Jun 2007 at 12:28, Scott Barninger wrote: But the entire doc source tarball is still a source in the packages. So I'm thinking about changing that and making only the pdf manuals (user and developer) actual sources in the RPM package. I see no reason for the source files to be in the packages for the documentation. My suggestion: split the docs into source and binary. To be a bit more explicit, the bacula-docs tarball we publish has actually been build before releasing it. I have always included that tarball as a source and then installed a few pieces. I'm suggesting to just install the pdf manuals and skip the html manual if that doesn't cause anyone grief. I think pdf is universal enough at this point. - This SF.net email is sponsored by DB2 Express Download DB2 Express C - the FREE version of DB2 express and take control of your XML. No limits. Just data. Click to get it now. http://sourceforge.net/powerbar/db2/ ___ Bacula-users mailing list Bacula-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/bacula-users
Re: [Bacula-users] [Bacula-devel] Possible RPM documentation change
On Sun, 2007-06-17 at 12:56 -0400, Dan Langille wrote: On 17 Jun 2007 at 12:42, Scott Barninger wrote: On Sun, 2007-06-17 at 12:32 -0400, Dan Langille wrote: On 17 Jun 2007 at 12:28, Scott Barninger wrote: But the entire doc source tarball is still a source in the packages. So I'm thinking about changing that and making only the pdf manuals (user and developer) actual sources in the RPM package. I see no reason for the source files to be in the packages for the documentation. My suggestion: split the docs into source and binary. To be a bit more explicit, the bacula-docs tarball we publish has actually been build before releasing it. I have always included that tarball as a source and then installed a few pieces. I'm suggesting to just install the pdf manuals and skip the html manual if that doesn't cause anyone grief. I think pdf is universal enough at this point. What about two tarballs? PDF. HTML. Well, yes, I suppose I could build my own but I was sort of looking to avoid that. - This SF.net email is sponsored by DB2 Express Download DB2 Express C - the FREE version of DB2 express and take control of your XML. No limits. Just data. Click to get it now. http://sourceforge.net/powerbar/db2/ ___ Bacula-users mailing list Bacula-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/bacula-users
Re: [Bacula-users] [Bacula-devel] Possible RPM documentation change
On Sun, 2007-06-17 at 12:56 -0400, Dan Langille wrote: On 17 Jun 2007 at 12:42, Scott Barninger wrote: On Sun, 2007-06-17 at 12:32 -0400, Dan Langille wrote: On 17 Jun 2007 at 12:28, Scott Barninger wrote: But the entire doc source tarball is still a source in the packages. So I'm thinking about changing that and making only the pdf manuals (user and developer) actual sources in the RPM package. I see no reason for the source files to be in the packages for the documentation. My suggestion: split the docs into source and binary. To be a bit more explicit, the bacula-docs tarball we publish has actually been build before releasing it. I have always included that tarball as a source and then installed a few pieces. I'm suggesting to just install the pdf manuals and skip the html manual if that doesn't cause anyone grief. I think pdf is universal enough at this point. What about two tarballs? PDF. HTML. I stripped the docs tarball leaving only the html manual and the pdf ones. That reduced the size of the SRPM to 11 MB but sourceforge is still not cooperating. I've tried 3 times today to get the 2.1.18 release up and I keep getting aborted uploads. Perhaps it will work better tomorrow. - This SF.net email is sponsored by DB2 Express Download DB2 Express C - the FREE version of DB2 express and take control of your XML. No limits. Just data. Click to get it now. http://sourceforge.net/powerbar/db2/ ___ Bacula-users mailing list Bacula-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/bacula-users
Re: [Bacula-users] [Bacula-devel] Possible RPM documentation change
On Mon, 2007-06-18 at 08:23 +0200, Kern Sibbald wrote: The told me to upload it to the shell area then to ftp it from there. I consider that a total waste of time for the docs, but I'll let you decide if you want to use it for the srpms. I've given you access to the shell area, but don't remember how to use it -- I logged in once. There is documentation on the site for how to get into it. I think you just ssh in, but you need to know the right address. The only thing I ask is that if you do upload files to the shell area, please delete them once you get them in the upload area, otherwise they start sending me email messages about the space usage which we are supposed to keep to a minimum. If you find that technique useful, please let me know how you did it, and also let me know if any of the other packagers need shell access. I will look at this this coming weekend as I don't have time at the moment. I tried just now to upload the 2.1.18 srpm by regular ftp and failed again after a partial upload. If you log in you will see it there in the upload area. So no 2.1.18 rpm for now, but for anyone interested it built without changes to the spec file from my previous beta release other than version information (I used my previous 2.1.10 docs file). - This SF.net email is sponsored by DB2 Express Download DB2 Express C - the FREE version of DB2 express and take control of your XML. No limits. Just data. Click to get it now. http://sourceforge.net/powerbar/db2/ ___ Bacula-users mailing list Bacula-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/bacula-users
Re: [Bacula-users] suggestion for the bacula.spec
Hello,
Thanks for the suggestion. Michael K. Johnson and I had this discussion
some years ago. His position, with which I agreed, was that it was bad
practice to prompt for information in rpm post-install scripts because
rpm was designed to run unattended. That is to say, tools like yum and
apt4rpm have a hard time answering prompts. So we settle for the
assumption that no password was in use and that seems to work for 99% of
users. Your suggestion does make the error output better from what I
see. Is there anyone out there with a postgresql installation who could
test the same or similar modification to the postgresql script? Sqlite
doesn't have password capability so far as I know.
On Thu, 2007-03-29 at 14:39 +0100, Jaime Ventura wrote:
Hello,
In the rpm based upgrade, I got the following:
...
Updating : bacula-mysql # [1/4]
Hmm, doesn't look like you have an existing database.
Granting privileges for MySQL user bacula...
ERROR 1045 (28000): Access denied for user 'root'@'localhost' (using
password: NO)
Error creating privileges.
Creating MySQL bacula database...
ERROR 1045 (28000): Access denied for user 'root'@'localhost' (using
password: NO)
Creation of bacula database failed.
Creating bacula tables...
ERROR 1045 (28000): Access denied for user 'root'@'localhost' (using
password: NO)
.
Thats ok because my mysql server is password protected.
But since the message wasn't so accurate to the problem, i took a look
at the spec file.
So Im sending you a suggestion.
As you can see it applies only on the mysql part of the script, because
I don't have sqlite or posgres to test it.
So, instead of:
...
%if %{mysql}
# test for an existing database
# note: this ASSUMES no password has been set for bacula database
DB_VER=`mysql 2/dev/null bacula -e 'select * from Version;'|tail -n 1`
# grant privileges and create tables if they do not exist
if [ -z $DB_VER ]; then
echo Hmm, doesn't look like you have an existing database.
...
you could:
...
# test for an existing database
# note: this ASSUMES no password has been set for bacula database
DB_VER=`mysql 21 bacula -e 'select * from Version;'|tail -n 1`
if expr $DB_VER : '.*ERROR.*' /dev/null; then
echo Couldn't access your database server.($DB_VER)
echo If you are installing bacula for the first time you will
need to run the bacula database creation scripts.
echo If you are upgrading you may need to run the bacula
database updating scripts.
# grant privileges and create tables if they do not exist
elif [ -z $DB_VER ]; then
echo Hmm, doesn't look like you have an existing database.
...
As you can see, I sugest to redirect stderror to std output the command,
and then search for the ERROR string to stat if there was an error.
Or you could ask for the database root password.
I didn't do any patch because the suggested code applies to mysql only
(may be you could do it for the other databases:P )
Thanks,
Jaime
-
Take Surveys. Earn Cash. Influence the Future of IT
Join SourceForge.net's Techsay panel and you'll get the chance to share your
opinions on IT business topics through brief surveys-and earn cash
http://www.techsay.com/default.php?page=join.phpp=sourceforgeCID=DEVDEV
___
Bacula-users mailing list
Bacula-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/bacula-users
Re: [Bacula-users] Fwd: Install-problems with OpenSUSE 10.2
I'm at a loss on that one. His command as shown, if that is truly what he typed, should work. It is the minimum necessary, no python support, no wxconsole, but should build. Perhaps a misplaced quote mark in reality vs what is shown in the email? It seems to think a define string is a file name. He of course doesn't need sqlite since we package our own. I also wonder why he is trying to rebuild rather than use the SuSE-10.2 binaries that are out there? On Mon, 2007-03-26 at 16:36 +0200, Kern Sibbald wrote: Any comments? -- Forwarded Message -- Subject: [Bacula-users] Install-problems with OpenSUSE 10.2 Date: Monday 26 March 2007 14:23 From: Ulrich Walter [EMAIL PROTECTED] To: bacula-users@lists.sourceforge.net Hello, At first, please be lenient toward me, I'm German and my English lessons in school are lying some years behind me. Now, my problem as named in the subject: My aim is to use a bacula-sytem to backup a Windows 2003 Server and some WinXP machines. I tried to install the bacula-2.0.3-1.src.rpm on a machine with OpenSuSE 10.2 as OS. The command on the console was: rpmbuild --rebuild \ --define build_su102 1 \ --define build_sqlite 1 \ bacula-2.0.3-1.src.rpm The result is: error: cannot open build_sqlite 1: No such file or directory The packages sqlite and sqlite2 form the distribution-dvd are installed. Please help me find the right way to install... Greetings from Duisburg, Germany Uli - Take Surveys. Earn Cash. Influence the Future of IT Join SourceForge.net's Techsay panel and you'll get the chance to share your opinions on IT business topics through brief surveys-and earn cash http://www.techsay.com/default.php?page=join.phpp=sourceforgeCID=DEVDEV ___ Bacula-users mailing list Bacula-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/bacula-users --- - Take Surveys. Earn Cash. Influence the Future of IT Join SourceForge.net's Techsay panel and you'll get the chance to share your opinions on IT business topics through brief surveys-and earn cash http://www.techsay.com/default.php?page=join.phpp=sourceforgeCID=DEVDEV ___ Bacula-users mailing list Bacula-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/bacula-users
Re: [Bacula-users] rpm error
No, he has installed the SuSE distro package which I have set to conflict with our official project packages for various previously discussed reasons. He should uninstall that and then install our packages. On Thu, 2007-03-08 at 13:57 +0100, Kern Sibbald wrote: Hello Scott, Is this problem related to the fact that he was upgrading two database versions? I.e. can a 2.0.x rpm do a double database upgrade? I wonder if he should first try updating to 1.38.11 then do the update to 2.0.x?? On Thursday 08 March 2007 00:12, [EMAIL PROTECTED] wrote: I've installed and tested bacula 1.36/MySql from the Suse 10.0 install media. I used this to run some basic tests and check the tape drive. I'm attempting to upgrade to 2.02 before I start final production configuration. I'm failing at the rpm command: omares-backup:/home/dthacker # rpm -U -v bacula-mysql-2.0.2-1.su100.i586.rpm warning: bacula-mysql-2.0.2-1.su100.i586.rpm: V3 DSA signature: NOKEY, key ID 10a792ad error: Failed dependencies: bacula conflicts with bacula-mysql-2.0.2-1 What am I missing? TIA Dave - Take Surveys. Earn Cash. Influence the Future of IT Join SourceForge.net's Techsay panel and you'll get the chance to share your opinions on IT business topics through brief surveys-and earn cash http://www.techsay.com/default.php?page=join.phpp=sourceforgeCID=DEVDEV ___ Bacula-users mailing list Bacula-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/bacula-users - Take Surveys. Earn Cash. Influence the Future of IT Join SourceForge.net's Techsay panel and you'll get the chance to share your opinions on IT business topics through brief surveys-and earn cash http://www.techsay.com/default.php?page=join.phpp=sourceforgeCID=DEVDEV ___ Bacula-users mailing list Bacula-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/bacula-users
Re: [Bacula-users] mac os x 10.4.8 and bacula-fd
Hello Darek, Thanks for writing back, but I have to tell you that there is little I think I can do with your dmg file?? as I do not have a Mac and know nothing about building or installing software on that platform. What I was meaning to say was that if you wished to volunteer your time to package for that platform we would welcome that. Otherwise I can pass this on to the users list and perhaps someone can make use of your work. On Fri, 2007-02-09 at 00:50 +0100, Darek Kramin wrote: Hello Scott, sorry for late reply,but I'm in the middle of house refurbishment. I did compile bacula client for mac os x 10.4.8 (inter core duo/universal binary). Apparently I'm new in developing for mac-before doing for Sun and Linux. However I can help as far as my knowledge exists. Hope bacula client 2.0.2 can be a solution for mac backup. In monday I'm leaving Poland for couple of weeks, but still will be availabel under gmail account. Inside dmg package you can find static linked client and console with configs and my compilation directives and of course marks of my system after uname -as command. is is standard mac book 13 '' with 1gb ram. regards, darek 2007/1/27, Scott Barninger [EMAIL PROTECTED]: Hello Darek, Thanks for writing. We are always interested in expanding the platform support for bacula. Please let us know if you may be interested in participating. We do not at the moment have a packager for Mac OS X. On Sat, 2007-01-27 at 21:41 +0100, Darek Kramin wrote: hello, please see link: http://www.statusq.org/archives/2005/12/10/853/ about setting client daemon under mac os. it doesn't need other x11 version to be installed. hope is better solution and not slowing down the system. i even didn't recognize 150mb backup over lan while working with torrents and web pages. regards darek - Take Surveys. Earn Cash. Influence the Future of IT Join SourceForge.net's Techsay panel and you'll get the chance to share your opinions on IT business topics through brief surveys-and earn cash http://www.techsay.com/default.php?page=join.phpp=sourceforgeCID=DEVDEV ___ Bacula-users mailing list Bacula-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/bacula-users
[Bacula-users] RedHat 9 rpm packages
Hello, I would like a bit of feedback. There are still a few apparent users of RedHat 9 based upon sourceforge download statistics. It would seem to me that the time has come to discontinue those packages (no panic, I am building 2.0.2 right now). Only the basic command line programs will still build, all of the gui stuff is locked out. Is anyone planning to continue this distribution into the reasonable future? Or should we plan to end support in some time frame? Scott - Using Tomcat but need to do more? Need to support web services, security? Get stuff done quickly with pre-integrated technology to make your job easier. Download IBM WebSphere Application Server v.1.0.1 based on Apache Geronimo http://sel.as-us.falkag.net/sel?cmd=lnkkid=120709bid=263057dat=121642 ___ Bacula-users mailing list Bacula-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/bacula-users
Re: [Bacula-users] [Bacula-devel] Bacula version 2.0.2 released to Source Forge
My rpms are out, Felix and Patti should follow soon. On Tue, 2007-01-30 at 23:09 +0100, Kern Sibbald wrote: Hello, I have just uploaded the source tar files and Win32 binaries for Bacula version 2.0.2 to the Bacula release area of Source Forge. Most of the rpms will be following this coming weekend. This is a bug fix update to version 2.0.1. Please note that to the best of my knowledge this release has regrettably not been built or tested on Solaris or FreeBSD, and will remain so until someone steps forward to do the testing. The same applies to the Win32 binaries. Best regards, Kern The changes in this release (since 2.0.1) include the following: 28Jan08 kes Fix maxruntime bug #621. 27Jan07 kes Get current main CVS .specs for RedHat, SuSE, Mandrake. 26Jan07 ebl Implement the include JobID in spool file name project. kes Reorder projects file in order determined by Jan 2007 vote. kes Fix open of SQLite3 db where user does not have write permission so that DIR does not crash. Fixes bug #761. 25Jan07 kes Change 'Device not configured to autolabel' from INFO to WARNING. kes Fix jobq.c to restart failed jobs when Reschedule Times = 0 which should restart an indefinite # of times. kes Fix configure --help to print --with-mysql[=DIR]. Same for other DIR specifications. 23Jan07 rn Fix msvc build problems. Fix bacula.dll exports for msvc build. Fix path quoting in SQLite scripts. Fix problems with SHGetFolderPath. 19Jan07 kes Create patches/2.0.1-restart.patch. Fixes bug #755. 18Jan07 kes Fix Job restart on error bug that promotes an Inc to a Full backup. This should fix bug #755. - Take Surveys. Earn Cash. Influence the Future of IT Join SourceForge.net's Techsay panel and you'll get the chance to share your opinions on IT business topics through brief surveys - and earn cash http://www.techsay.com/default.php?page=join.phpp=sourceforgeCID=DEVDEV ___ Bacula-devel mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/bacula-devel - Using Tomcat but need to do more? Need to support web services, security? Get stuff done quickly with pre-integrated technology to make your job easier. Download IBM WebSphere Application Server v.1.0.1 based on Apache Geronimo http://sel.as-us.falkag.net/sel?cmd=lnkkid=120709bid=263057dat=121642 ___ Bacula-users mailing list Bacula-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/bacula-users
Re: [Bacula-users] [Bacula-devel] Bacula 2.0.1 released to Source Forge
Hello, Source rpm package released also. Felix, note that you now have a build_fc6 tag. On Sat, 2007-01-13 at 17:25 +0100, Kern Sibbald wrote: Hello, I'm pleased to announce that you can now find Bacula version 2.0.1 on Source Forge. This afternoon, I released the following files: Package bacula: bacula-2.0.1.tar.gz bacula-2.0.1.tar.gz.sig bacula-docs-2.0.1.tar.gz bacula-docs-2.0.1.tar.gz.sig Package gui: bacula-gui-2.0.1.tar.gz bacula-gui-2.0.1.tar.gz.sig Package rescue (NOT UPDATED): bacula-rescue-2.0.0.tar.gz bacula-rescue-2.0.0.tar.gz.sig Package Win32: winbacula-2.0.1.exe winbacula-2.0.1.exe.sig This is a bug fix update to version 2.0.0, which contains the following fixes: Version 2.0.1 12Jan07 kes Fix Bacula-Documentation link on Win32 to point to index.html instead of bacula.html. Fixed bug #750. kes Return JobId in db_get_job_record() when JobId==0. This should fix bug #741. kes Do not release source pointers when restarting a failed job. 11Jan07 kes Add dynamic dll entry point for SHGetFolderPath to Win32 code. This *should* fix bug #747. kes Modify winbacula.nsi to substitute with g bin_dir_cmd. Should fix bug #742. 09Jan07 kes Modify USTORE constructor to set an empty store_source string, and don't copy the store_source string in a cancel. Hopefully this will fix Arno's seg fault, bug #744. kes Add back code to disable conio in configure. Fixes bug #743. kes Correct the Options scanner in the FD to correctly handle SHA1 option, which was eating the next option. Reported by Sebastien Guilbaud. kes Add code to indicate when the SD is spooling, spool wait, and despooling as requested by Alan Brown. As is always the case, for minor releases, all the components are compatible with version 2.0.0 and also following the compatibilities mentioned in the 2.0.0 release. Best regards, Kern - Take Surveys. Earn Cash. Influence the Future of IT Join SourceForge.net's Techsay panel and you'll get the chance to share your opinions on IT business topics through brief surveys - and earn cash http://www.techsay.com/default.php?page=join.phpp=sourceforgeCID=DEVDEV ___ Bacula-devel mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/bacula-devel - Take Surveys. Earn Cash. Influence the Future of IT Join SourceForge.net's Techsay panel and you'll get the chance to share your opinions on IT business topics through brief surveys - and earn cash http://www.techsay.com/default.php?page=join.phpp=sourceforgeCID=DEVDEV ___ Bacula-users mailing list Bacula-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/bacula-users
[Bacula-users] [Fwd: Re: [Bacula-devel] Bacula 2.0.1 released to Source Forge]
FYI all, I made an error on the new fc6 build tag, so anyone rebuilding should continue to use fc5. I'll fix it directly for the next release. Forwarded Message From: Felix Schwarz [EMAIL PROTECTED] To: Scott Barninger [EMAIL PROTECTED] Subject: Re: [Bacula-devel] Bacula 2.0.1 released to Source Forge Date: Sun, 14 Jan 2007 21:08:27 +0100 Hi Scott, Scott Barninger schrieb: Source rpm package released also. Felix, note that you now have a build_fc6 tag. Thanks for that. Unfortunately, the new tag is missing in the spec file in one place: error: You must specify a platform. Please examine the spec file. error: line 131: Unknown tag: exit 1 Therefore, I still built the new RPMs for fc6 with fc5 as a platform. fs - Take Surveys. Earn Cash. Influence the Future of IT Join SourceForge.net's Techsay panel and you'll get the chance to share your opinions on IT business topics through brief surveys - and earn cash http://www.techsay.com/default.php?page=join.phpp=sourceforgeCID=DEVDEV ___ Bacula-users mailing list Bacula-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/bacula-users
Re: [Bacula-users] incomplete fc6 support in 2.0.1 bacula.spec
Hello Charles,
The bug you reference has been corrected in the cvs copy. And yes, the
spec file is getting rather noisy. Why do I do all of that? We could
simplify the spec substantially by removing all the platform stuff and
just let rpm itself do the dependency requirements to the libs
automatically. That is the way many distros and commercial companies
handle it. It is certainly easier for a maintainer.
The reason I go to the effort is for the users who download the package.
If you don't take the time to research and require the specific package
names (which vary by distribution often) then the user just gets a very
unhelpful message stating that libSomeProgram.so.2 is required which
prompts a message to the lists asking where to get that. Same with
people who want to rebuild the source rpm and write because of compile
errors due to missing packages.
On Sun, 2007-01-21 at 18:34 -0500, Charles Galpin wrote:
Hi Scott (and anyone else involved in maintaining the src.rpm)
Just wanted to let you know that you need a couple of minor changes
to the bacula.spec file from bacula-2.0.1-1.src.rpm to support fc6
properly.
[EMAIL PROTECTED] SPECS]# !diff
diff bacula.spec bacula.spec.orig
129c129
%if ! %{rh7} ! %{rh8} ! %{rh9} ! %{fc1} ! %{fc3} ! %
{fc4} ! %{fc5} ! %{fc6} ! %{wb3} ! %{su9} ! %{su10}
! %{mdk}
---
%if ! %{rh7} ! %{rh8} ! %{rh9} ! %{fc1} ! %{fc3} ! %
{fc4} ! %{fc5} ! %{wb3} ! %{su9} ! %{su10} ! %{mdk}
1093c1093
%if %{rh8} || %{rh9} || %{wb3} || %{fc1} || %{fc3} || %{fc4} || %
{fc5} || %{fc6}|| %{mdk}
---
%if %{rh8} || %{rh9} || %{wb3} || %{fc1} || %{fc3} || %{fc4} || %
{fc5} || %{mdk}
This specfile is getting really ugly though. Are all these conditions
really necessary?
thanks
charles
-
Take Surveys. Earn Cash. Influence the Future of IT
Join SourceForge.net's Techsay panel and you'll get the chance to share your
opinions on IT business topics through brief surveys - and earn cash
http://www.techsay.com/default.php?page=join.phpp=sourceforgeCID=DEVDEV
___
Bacula-users mailing list
Bacula-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/bacula-users
Re: [Bacula-users] incomplete fc6 support in 2.0.1 bacula.spec
See src/platforms/contrib-rpm in the source package. On Sun, 2007-01-21 at 19:08 -0500, Charles Galpin wrote: Thanks Scott! Understood about making it easier on the users and I commend that. In that spirit, it's actually pretty hard to build anyway since it needs specific choices made up front about what platform and database. A very nice approach I have seen to this is to have a script that generates a spec file based on environment variables set. To see this in action, check out Simon Mudd's excellent postfix rpms. http://postfix.wl0.org/en/building-rpms/ I suspect this appraoch would also make the spec file simpler while making building them easier for the user at the same time. hth charles On Jan 21, 2007, at 6:57 PM, Scott Barninger wrote: The reason I go to the effort is for the users who download the package. If you don't take the time to research and require the specific package names (which vary by distribution often) then the user just gets a very unhelpful message stating that libSomeProgram.so.2 is required which prompts a message to the lists asking where to get that. Same with people who want to rebuild the source rpm and write because of compile errors due to missing packages. - Take Surveys. Earn Cash. Influence the Future of IT Join SourceForge.net's Techsay panel and you'll get the chance to share your opinions on IT business topics through brief surveys - and earn cash http://www.techsay.com/default.php?page=join.phpp=sourceforgeCID=DEVDEV ___ Bacula-users mailing list Bacula-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/bacula-users
Re: [Bacula-users] [Bacula-devel] Bacula 2.0.0 goodness, RPM SPEC building
I hope to publish the rpm packages this weekend. On Thu, 2007-01-04 at 20:23 +0100, Kern Sibbald wrote: On Thursday 04 January 2007 19:53, Dan Trainor wrote: Hi, all - Now, Kern, I noticed that you're noted as the RPM package maintainer for the 1.38 series - should the same be assumed about the 2.0 series, as well? Well, I may be listed as the maintainer, but Scott Barninger is the guy who does the work. I guess what I'm getting at is, I'm sure there are a few people who are plenty eager to find a nice SRPM for the 2.0 series, because we use RPMs a lot more frequently than we use tarballs and such. Are there any plans to package and distribute a SRPM or spec file within the next few days? I covered that in my release announcement -- it is up to the packager not me. Is any help needed for creating a 2.0 SPEC file for building RPMs with? If work has not already started, I can surely hack one up and give it to you guys - however, I'm not so sure if it would be up to Kern's expectations :) I believe that the .spec file that is in the source code is perfectly fine with the exception of updating the version numbers of everything, ... - Take Surveys. Earn Cash. Influence the Future of IT Join SourceForge.net's Techsay panel and you'll get the chance to share your opinions on IT business topics through brief surveys - and earn cash http://www.techsay.com/default.php?page=join.phpp=sourceforgeCID=DEVDEV ___ Bacula-devel mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/bacula-devel - Take Surveys. Earn Cash. Influence the Future of IT Join SourceForge.net's Techsay panel and you'll get the chance to share your opinions on IT business topics through brief surveys - and earn cash http://www.techsay.com/default.php?page=join.phpp=sourceforgeCID=DEVDEV ___ Bacula-users mailing list Bacula-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/bacula-users
Re: [Bacula-users] [Bacula-devel] Bacula 2.0.0 goodness, RPM SPEC building
I hope to publish the rpm packages this weekend. For the impatient, the most recent 1.39 SRPM should be essentially the same code, albeit packaged with 1.38 docs. Or, as Kern mentions, the spec file in the tarball should build as I have been testing and updating throughout the 1.39.x releases. On Thu, 2007-01-04 at 20:23 +0100, Kern Sibbald wrote: On Thursday 04 January 2007 19:53, Dan Trainor wrote: Hi, all - Now, Kern, I noticed that you're noted as the RPM package maintainer for the 1.38 series - should the same be assumed about the 2.0 series, as well? Well, I may be listed as the maintainer, but Scott Barninger is the guy who does the work. I guess what I'm getting at is, I'm sure there are a few people who are plenty eager to find a nice SRPM for the 2.0 series, because we use RPMs a lot more frequently than we use tarballs and such. Are there any plans to package and distribute a SRPM or spec file within the next few days? I covered that in my release announcement -- it is up to the packager not me. Is any help needed for creating a 2.0 SPEC file for building RPMs with? If work has not already started, I can surely hack one up and give it to you guys - however, I'm not so sure if it would be up to Kern's expectations :) I believe that the .spec file that is in the source code is perfectly fine with the exception of updating the version numbers of everything, ... - Take Surveys. Earn Cash. Influence the Future of IT Join SourceForge.net's Techsay panel and you'll get the chance to share your opinions on IT business topics through brief surveys - and earn cash http://www.techsay.com/default.php?page=join.phpp=sourceforgeCID=DEVDEV ___ Bacula-devel mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/bacula-devel - Take Surveys. Earn Cash. Influence the Future of IT Join SourceForge.net's Techsay panel and you'll get the chance to share your opinions on IT business topics through brief surveys - and earn cash http://www.techsay.com/default.php?page=join.phpp=sourceforgeCID=DEVDEV ___ Bacula-users mailing list Bacula-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/bacula-users
Re: [Bacula-users] [Bacula-devel] Bacula 2.0.0 goodness, RPM SPEC building
Thanks for the offer. Felix Schwarz is building EL4 64 bit packages. If you would be interested in building and contributing 32 bit please see the instructions in platforms/contrib-rpms directory. On Fri, 2007-01-05 at 13:33 -0700, Dan Trainor wrote: Hi, Scott - Thanks for the update - much appreciated. If you would like additional testing, please do let me know. I'd be happy to spend a short while over the weekend. Most of my testing will be done under RHEL4/CentOS4. Thanks -dant Scott Barninger wrote: I hope to publish the rpm packages this weekend. For the impatient, the most recent 1.39 SRPM should be essentially the same code, albeit packaged with 1.38 docs. Or, as Kern mentions, the spec file in the tarball should build as I have been testing and updating throughout the 1.39.x releases. On Thu, 2007-01-04 at 20:23 +0100, Kern Sibbald wrote: On Thursday 04 January 2007 19:53, Dan Trainor wrote: Hi, all - Now, Kern, I noticed that you're noted as the RPM package maintainer for the 1.38 series - should the same be assumed about the 2.0 series, as well? Well, I may be listed as the maintainer, but Scott Barninger is the guy who does the work. I guess what I'm getting at is, I'm sure there are a few people who are plenty eager to find a nice SRPM for the 2.0 series, because we use RPMs a lot more frequently than we use tarballs and such. Are there any plans to package and distribute a SRPM or spec file within the next few days? I covered that in my release announcement -- it is up to the packager not me. Is any help needed for creating a 2.0 SPEC file for building RPMs with? If work has not already started, I can surely hack one up and give it to you guys - however, I'm not so sure if it would be up to Kern's expectations :) I believe that the .spec file that is in the source code is perfectly fine with the exception of updating the version numbers of everything, ... - Take Surveys. Earn Cash. Influence the Future of IT Join SourceForge.net's Techsay panel and you'll get the chance to share your opinions on IT business topics through brief surveys - and earn cash http://www.techsay.com/default.php?page=join.phpp=sourceforgeCID=DEVDEV ___ Bacula-devel mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/bacula-devel - Take Surveys. Earn Cash. Influence the Future of IT Join SourceForge.net's Techsay panel and you'll get the chance to share your opinions on IT business topics through brief surveys - and earn cash http://www.techsay.com/default.php?page=join.phpp=sourceforgeCID=DEVDEV ___ Bacula-users mailing list Bacula-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/bacula-users
Re: [Bacula-users] SRPM for 2.0?
Hello, The source rpm for bacula-2.0.0 has been released to sourceforge. - Take Surveys. Earn Cash. Influence the Future of IT Join SourceForge.net's Techsay panel and you'll get the chance to share your opinions on IT business topics through brief surveys - and earn cash http://www.techsay.com/default.php?page=join.phpp=sourceforgeCID=DEVDEV ___ Bacula-users mailing list Bacula-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/bacula-users
[Bacula-users] bacula-2.0.0 rpm release
Hello, The source rpm package has been released as well as the binary packages which I currently support (see below). I expect that Felix and Patti will be releasing their platform packages sometime this weekend as well. If anyone is interested in publishing for platforms not mentioned at the bottom of this post, please examine the instructions in the directory platforms/contrib-rpm in the source tarball and contact me. It should be noted with this release that I am discontinuing publishing packages for Mandriva as Luca Berra has them available in Mandriva contrib. Bacula-2.0 RPM Release Notes 06 January 2007 D. Scott Barninger barninger at fairfieldcomputers dot com Release 2.0.0-1 This release incorporates a number of significant changes since 1.38. These release notes refer to the rpm packaging only. Please refer to the release notes and changelog in the tarball or on sourceforge for complete information on all changes. * * SQLite patches re-enabled * * Patches for the sqlite scripts have been updated and re-enabled for correct paths for rpm installation. *** * Gnome console dropped on some platforms * *** The gconsole package has been dropped on older gnome platforms (gtk+ 2.4). Changes in the gnome api and code produced by Glade no longer build. gconsole is now not built on the following platforms: rh7, rh8, rh9, rhel3 (and clones), fc1, mdk, su9 * Third party packager support * A new build tag added to support third party packagers to replace the information in the Packager: tag in the rpm. Invoking --define contrib_packager Your Name [EMAIL PROTECTED] will substitute your packager identification. Users interested in building packages for platforms not normally published should examine the platforms/contrib-rpm directory in the source code. *** * Option to build client only * *** A build define to build the client rpm package only added. This turns off all database builds, gnome console and wxconsole. --define build_client_only 1 * Python support added * Support for compiling with python scripting support added. This is off by default but can be enabled with: --define build_python 1 Released binary packages are built with python support. *** * Database update * *** The 2.0 release requires an update to the bacula database structure from version 9 to version 10. A pre-install routine has been added to check for databases older than 9. In that event the install will exit with an error message indicating that the database must be updated to version 9 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 9 database is detected a post-install routine will update the database after creating a backup file in the bacula working directory. ** * Platform Notes * ** The spec file currently supports building on the following platforms: # RedHat builds --define build_rh7 1 --define build_rh8 1 --define build_rh9 1 # Fedora Core build --define build_fc1 1 --define build_fc3 1 --define build_fc4 1 --define build_fc5 1 To build on Fedora 6 use build_fc5 currently. The next release should include updated dependencies for fc6. # Whitebox Enterprise build --define build_wb3 1 # RedHat Enterprise builds --define build_rhel3 1 --define build_rhel4 1 # CentOS build --define build_centos3 1 --define build_centos4 1 # SuSE build --define build_su9 1 --define build_su10 1 # Mandrake 10.x build --define build_mdk 1 # Mandriva build --define build_mdv 1 ** * Database build options * ** Database support (must select one or build client only) MySQL support: --define build_mysql 1 # OR if using mysql 4.x define this # currently: Mandrake 10.x, SuSE 9.x 10.0, RHEL4, fc4 --define build_mysql4 1 # OR if using mysql 5.x define this # currently: SuSE 10.1, fc5 --define build_mysql5 1 PostgreSQL support: --define build_postgresql 1 Sqlite support: --define build_sqlite 1 *** * Other build options * *** Supress build of Gnome Console: --define nobuild_gconsole 1 Enable X86-64 support --define build_x86_64 1 This build switch remains but should no longer be necessary. The configure script was adjusted in the 1.39 development series to correctly detect the location of 64 bit libraries. Enable wxconsole: --define build_wxconsole 1 Enable python support: --define build_python 1 Build the client package only: --define build_client_only 1 ** * Current binary package
Re: [Bacula-users] Advice requested from Mandriva users
On Mon, 2006-12-11 at 16:30 +0100, steen meyer wrote: Hi Scott, Are you using the free version of M2007? Yes. I have installed 2007 but not used it yet, I can try and see how mine behaves, but I think it is the pwoerpack version that I installed, but I can try the Free version also, if that is the one you have Steen Søndag 10 december 2006 19:08 skrev Scott Barninger: Hello, I'm looking for some assistance from anyone who regularly uses Mandriva-2007. I installed in on a partition on my build host last weekend in order to continue my rpm build support for that platform, but I must admit I'm less than impressed. Logging into a gnome session gets me a desktop with some icons but no panels or menus and I can't seem to click my way to adding a panel. Logging into a KDE session gets me a panel and a main menu, but when I ran rpmdrake and tried to apply updates to the system it just seems to be braindead. When I select 'all security updates' I get no packages checked. When I select all 'installed packages' I get a lot of packages checked. However, clicking apply in either case causes the program to insist that I must select some updates first. Have I missed something or is this distribution just broken? I have no intention of clicking through all the categories and checking the packages I need to update every time. I always try to build bacula packages against a fully updated system. Regards, Scott - Take Surveys. Earn Cash. Influence the Future of IT Join SourceForge.net's Techsay panel and you'll get the chance to share your opinions on IT business topics through brief surveys - and earn cash http://www.techsay.com/default.php?page=join.phpp=sourceforgeCID=DEVDEV ___ Bacula-users mailing list Bacula-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/bacula-users - Take Surveys. Earn Cash. Influence the Future of IT Join SourceForge.net's Techsay panel and you'll get the chance to share your opinions on IT business topics through brief surveys - and earn cash http://www.techsay.com/default.php?page=join.phpp=sourceforgeCID=DEVDEV ___ Bacula-users mailing list Bacula-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/bacula-users
Re: [Bacula-users] [Bacula-devel] Advice requested from Mandriva users
On Thu, 2006-12-14 at 07:32 +0100, Luca Berra wrote: On Wed, Dec 13, 2006 at 05:48:48PM -0500, Scott Barninger wrote: I certainly meant no offense. My only mission with bacula is contributing to the community. If you feel my Mandriva packages are redundant I'll be happy to not spend time on it, I have plenty of other I do believe that two sets of mandriva packages are redundant, i don't really know which one is better. No problem. I will leave the mandriva packaging to you, whether that be the spec file in bacula cvs or another, and concentrate my efforts on other platforms. It's truly becoming more than one person can manage on a part time basis, which is why I put out the call for assistance with the 1.39 branch. I have never used mandriva on a daily basis, only installed it for build purposes, so I suspect you are much better qualified in this respect. Cheers. things to occupy my time. Please accept my apologies if I offended you with these mails. Since you sent this to me only I'm only copying Kern. Feel free to publish my response to the lists if you wish. sorry, my response should have gone to the list. I am not offended, but i was not amused by the tone of your first mail, which sounded more like distro-bashing than a request for help. Let's move on to the technical points. On Wed, 2006-12-13 at 21:32 +0100, Luca Berra wrote: On Wed, Dec 13, 2006 at 07:20:29AM -0500, Scott Barninger wrote: On Tue, 2006-12-12 at 12:00 +0100, Luca Berra wrote: On Sun, Dec 10, 2006 at 01:08:57PM -0500, Scott Barninger wrote: Hello, I'm looking for some assistance from anyone who regularly uses Mandriva-2007. I installed in on a partition on my build host last weekend in order to continue my rpm build support for that platform, but is there any need for that, since mandriva is shipping with bacula rpms? Well, that depends upon what you want I suppose. The distribution packages, like SuSE packages, are pretty plain vanilla, were did you get this? Only from looking at the package contents and requires. The only linkages I saw were to sqlite. In the case of the official SuSE packages they only provide mysql. do not offer a choice in database, this is partially true actually multiple database are not built by default, but rpms can be rebuilt with support for mysql or postgres by passing --with ... flags to rpmbuild Agreed, but we attempt, from the project standpoint, to cater to the large base that does not do rpmbuild, doesn't wish to, but rather looks for pre-built choices. bacula can be built many ways. I've had many we were discussing about providing more db choices in the default rpm, i was hoping for modular db support from bacula, which IIRC Robert Nelson told me would come after the switch to cmake, but it is possible to rebuild the director 3 times and ship it in 3 different rpms. the only thing i am unsure about is the bscan program, i believe it should be part of the bacula-sd package, but it is writing directly to the database. Maybe i should also split it in 3 different packages. emails over the years from folks who just say could you publish this for me, I don't have the expertise, don't want to install devel packages etc. I have tried to produce as many choices as I can and currently am recruiting other platform builders to expand those choices within an accepted standard structural framework. That is the point of the recent publication of a build script with 1.39.x and the instructions in platforms/contrib-rpms/, to enhance the platform choices but standardize the actual build process across all those platforms. Not because I think my choices are in any way better than yours, but just to provide a standard basket to choose from. The biggest problem I see with the whole rpm process is the variation in sub-packaging choices, package names, and all that across various distributions. I invite you to join us in this process. I will have a look at the build script you mention, but i don't know how to merge those rpm back again since we took many different choices. do not run the dbupdate scripts on upgrade, we run dbupgrade scripts that allow to upgrade seamlessly from DB version 4 to latest, and we always did My mistake. I didn't look closely enough before replying to you. And the same for you comment below. My apologies. do not include the rescue files this is true, might package them separately if there is requests tough. and do not offer the security enhancements we have included like running as lesser user, setting random passwords on install etc. are you kidding? i inserted code to replace default passwords from the first rpm i produced for bacula, one or two years before you implemented it in your rpms. and yes, it runs with a lower privilege user even since bacula did support this. Regards, L
[Bacula-users] Advice requested from Mandriva users
Hello, I'm looking for some assistance from anyone who regularly uses Mandriva-2007. I installed in on a partition on my build host last weekend in order to continue my rpm build support for that platform, but I must admit I'm less than impressed. Logging into a gnome session gets me a desktop with some icons but no panels or menus and I can't seem to click my way to adding a panel. Logging into a KDE session gets me a panel and a main menu, but when I ran rpmdrake and tried to apply updates to the system it just seems to be braindead. When I select 'all security updates' I get no packages checked. When I select all 'installed packages' I get a lot of packages checked. However, clicking apply in either case causes the program to insist that I must select some updates first. Have I missed something or is this distribution just broken? I have no intention of clicking through all the categories and checking the packages I need to update every time. I always try to build bacula packages against a fully updated system. Regards, Scott - Take Surveys. Earn Cash. Influence the Future of IT Join SourceForge.net's Techsay panel and you'll get the chance to share your opinions on IT business topics through brief surveys - and earn cash http://www.techsay.com/default.php?page=join.phpp=sourceforgeCID=DEVDEV ___ Bacula-users mailing list Bacula-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/bacula-users
Re: [Bacula-users] bacula-mysql-1.38.11-3.fc5.i386.rpm mysql-5.0.18
On Mon, 2006-12-04 at 16:53 +0100, piero wrote: Scott Barninger ha scritto: On Mon, 2006-12-04 at 10:44 +0100, piero wrote: Scott Barninger ha scritto: On Thu, 2006-11-30 at 17:07 +0100, piero wrote: Scott Barninger ha scritto: Piero, Another thought - this package has been downloaded 491 times to date and this is the first I've seen this problem reported. This is an i386 package linked against 32-bit libs. Are you maybe running a 64-bit system? I am runninn fc5 on i386 32-bit. I don,t solve my problem, anyway thanks for your availability What is the result of: rpm -qa|grep mysql I have installed also mysql-server. The command rpm -qa | grep mysql is now mysql-5.0.18-2.1 mysql-server -5.0.18-2.1 I send you the file obtained whith the command : strace rpm -ivh bacula-mysql-1.38.11-3.fc5.i386.rpm rpmlog Thanks Piero Good grief. Try updating mysql. The latest update for FC5 is 5.0.27-1. G O A L Many and Many thanks Excuse me for my insistence Not at all. This is the first I ever heard of an API incompatibility on a minor-minor revision level. Kern - we should document this somehow, either Fedora or MySQL made an incompatible change between 5.0.18 and 5.0.27. The FC5 package will not work with 5.0.18, claiming missing dependency. by piero - Take Surveys. Earn Cash. Influence the Future of IT Join SourceForge.net's Techsay panel and you'll get the chance to share your opinions on IT business topics through brief surveys - and earn cash http://www.techsay.com/default.php?page=join.phpp=sourceforgeCID=DEVDEV ___ Bacula-users mailing list Bacula-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/bacula-users
Re: [Bacula-users] [Bacula-devel] bacula-mysql-1.38.11-3.fc5.i386.rpm mysql-5.0.18
On Tue, 2006-12-05 at 09:47 +0100, Kern Sibbald wrote: Well, any time you upgrade a database, whether or not it is MySQL, SQLite, or PostgreSQL, there is a good probability that Bacula needs to be recompiled. My experience is that this is rare for MySQL as long as the first two versions do not change. For PostgreSQL, the general rule is that one must always recompile, and worse, for PostgreSQL, you can easily corrupt your database if you don't back it up and reload it after the upgrade. If I am not mistaken, this is stated in the manual. Well, this is the first time I have seen an incompatible upgrade within a current distribution. I didn't look at the issue of rpm requires. It seems to me that to be safe, that the rpm should alway require exactly the same version it was built with. This may be a bit overkill, but it is the safest. Ugh, no. Way too much overhead. The best advice I have is that if you are running a production system with Bacula or any other program that uses an SQL engine, do not upgrade your SQL engine without upgrading all the other software that uses it. Concerning Fedora. I used that distribution. I dropped it because there were just too many problems. I don't regret for a second having dropped it because I have had *far* fewer problems. My personal problems were with FC4 and then worse ones with FC5. In the articles I've read since then FC6 is rated even worse. I feel sorry for any Fedora user unless he really enjoys being on the bloody edge. Scott, if you would like to build and release new rpms, OK, but I think we should be careful about letting the Fedora cowboys jerk us around. I don't know how to go about documenting this as this particular incident doesn't seem to be something for the manual, and all the other ways of providing documentation don't seem to reach many of the users. If you have specific suggestions, I'm listening. I would recommend that you send an email to the bacula-users and bacula-devel lists describing the problem. My proposed solutions would be:. the user reverts to the previous version of MySQL. You misunderstood, the released packages were built against a later version 5.0.24, updating to which fixed the problem. I expect this thread will serve to document it as well as any. Regards, Kern On Monday 04 December 2006 22:19, Scott Barninger wrote: On Mon, 2006-12-04 at 16:53 +0100, piero wrote: Scott Barninger ha scritto: On Mon, 2006-12-04 at 10:44 +0100, piero wrote: Scott Barninger ha scritto: On Thu, 2006-11-30 at 17:07 +0100, piero wrote: Scott Barninger ha scritto: Piero, Another thought - this package has been downloaded 491 times to date and this is the first I've seen this problem reported. This is an i386 package linked against 32-bit libs. Are you maybe running a 64-bit system? I am runninn fc5 on i386 32-bit. I don,t solve my problem, anyway thanks for your availability What is the result of: rpm -qa|grep mysql I have installed also mysql-server. The command rpm -qa | grep mysql is now mysql-5.0.18-2.1 mysql-server -5.0.18-2.1 I send you the file obtained whith the command : strace rpm -ivh bacula-mysql-1.38.11-3.fc5.i386.rpm rpmlog Thanks Piero Good grief. Try updating mysql. The latest update for FC5 is 5.0.27-1. G O A L Many and Many thanks Excuse me for my insistence Not at all. This is the first I ever heard of an API incompatibility on a minor-minor revision level. Kern - we should document this somehow, either Fedora or MySQL made an incompatible change between 5.0.18 and 5.0.27. The FC5 package will not work with 5.0.18, claiming missing dependency. by piero - Take Surveys. Earn Cash. Influence the Future of IT Join SourceForge.net's Techsay panel and you'll get the chance to share your opinions on IT business topics through brief surveys - and earn cash http://www.techsay.com/default.php?page=join.phpp=sourceforgeCID=DEVDEV ___ Bacula-devel mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/bacula-devel - Take Surveys. Earn Cash. Influence the Future of IT Join SourceForge.net's Techsay panel and you'll get the chance to share your opinions on IT business topics through brief surveys - and earn cash http://www.techsay.com/default.php?page=join.phpp=sourceforgeCID=DEVDEV ___ Bacula-users mailing list Bacula-users@lists.sourceforge.net https
Re: [Bacula-users] [Bacula-devel] (no subject)
I wasn't able to open the attachment, somehow came through corrupted. Here is a link: http://www.fsfeurope.org/projects/fla/FLA-1.0.en.pdf On Sat, 2006-11-04 at 13:46 +0100, Kern Sibbald wrote: Hello, 1 November 2006 This contents of this email is for discussion on the Bacula email list, but not yet a topic for publication. As you are probably aware, I am planning certain reorganizations of the Bacula project for a number of reasons. Two of the objectives that I have are to make the project less dependent on one person (me) and to ensure that the source code remains Free Software forever. These two objectives involve the creation of a Bacula entity (an Association or a Foundation), and the transfer of the copyright from myself to some entity. The purpose of this email is to give you, the Bacula users, advanced notice of what I think is the best path for the copyright transfer so that you can provide your feedback on it prior to my final decision. Currently, the timing is to send you this email as soon as possible then to make the final decision on the 15th of November with implementation before the end of the month. Several months ago, I met with Georg Greve, the President of the Free Software Foundation Europe (FSFE). I learned that he was in the process of creating the FSFE Freedom Task Force to work with projects that would like to enter into a fiduciary license agreement with the FSFE with the objective to offload the adminstrative (legal) needs of the project to the FSFE while keeping the project adminstration unchanged. The Freedom Task Force has been in operation since the beginning of October with Shane Coughlan heading it up. Probably the best explaination of their policy as it relates to Bacula is described in the FSFE Fiduciary Licensing Policy, which I have attached to this email in pdf format. A short summary of what I am proposing is: 1. Transfer the Bacula copyright to the FSFE. 2. There will be no change in the license, which is defined in the LICENSE file -- only the copyright holder will be changed. 3. FSFE will look after the legal matters of maintaining and, if necessary, defending the license. 4. Aside from the copyright assignments for important contributions, there will be no other changes to the project resulting from the copyright transfer. 5. The final transfer of the copyright will occur on or shortly after the 15th of November and will apply to the next released version. 6. The official announcement of the formation of the FSFE Freedom Task Force, and that Bacula will particpate in their Fiduciary Licensing will be made at the end of November. My belief is that this copyright transfer will be beneficial to the project in many respects: assure that the source remains Free Software, ensure that the source is not tied to any single person, off load most of the legal tasks, ... If any of you have concerns, comments, or questions, please do not hesitate to voice them now, either on the Bacula email lists or directly to me. I will take all comments and concerns into consideration and attempt to answer all the questions. Since I am on vacation and my Internet access is very limited, some or all my responses may be delayed until after my return on the 10th of November. Until the official FSFE announcement, I request that you keep this information (FSFE Freedom Task Force, Bacula participation) confidential to this list. Best regards, Kern - Using Tomcat but need to do more? Need to support web services, security? Get stuff done quickly with pre-integrated technology to make your job easier Download IBM WebSphere Application Server v.1.0.1 based on Apache Geronimo http://sel.as-us.falkag.net/sel?cmd=lnkkid=120709bid=263057dat=121642 ___ Bacula-devel mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/bacula-devel - Using Tomcat but need to do more? Need to support web services, security? Get stuff done quickly with pre-integrated technology to make your job easier Download IBM WebSphere Application Server v.1.0.1 based on Apache Geronimo http://sel.as-us.falkag.net/sel?cmd=lnkkid=120709bid=263057dat=121642 ___ Bacula-users mailing list Bacula-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/bacula-users
Re: [Bacula-users] [Bacula-devel] Bacula BETA 1.39.26 released to Source Forge
I've posted a source rpm for this for anyone wishing to do some test builds. Personally I built SuSE only with no issues although I did commit a change in the spec file from the tarball due to changes in the sqlite scripts. The docs are still a placeholder at 1.38.11. On Sat, 2006-10-14 at 15:36 +0200, Kern Sibbald wrote: Hello, This morning, I release the source tar file for Bacula BETA 1.39.26 to the Bacula release area of Source Forge. At the same time, I released the corresponding Win32 binary. This release is mainly a bug fix release to the prior version for both the main core code (Unix) and for the Win32 code. Although this code passes all my regression scripts and is running in production here, I have neither tested it on Solaris nor on FreeBSD due to time constraints (I'll be leaving on vacation Monday morning). Please note, since the released version numbers are unique even for beta releases, I have stopped appending the date to the release file, which simplifies its name just a bit. Best regards, Kern For your convenience, here are the ChangeLog items that have been added since version 1.39.24 was released: 2Oct06 kes Apply the three patches from Richard Mortimer. bacula-reposition.patch, bacula-tape-reopen.patch, and bacula-eod.patch. This corrects tape positioning on older devices, and also a problem with btape. kes Apply fix from bug report #696 where writing to a FIFO does not work due to a dumb typo. kes Unlock the tape door before the file descriptor is released. This should fix lots of somewhat subtle failures when using an autochanger. 11Oct06 kes Correct mtx-changer bug that I introduced in a recent commit, and pointed out by Robert Nelson -- thanks. rbn Fix Windows' daemons so that messages print to stdout if not running as a service. rbn Add daemon name to trace file name (eg bacula-dir.trace). rbn Fix environment variable expansion in directory names on Windows. rbn Fix autochanger support in fill command. rbn Update SQL scripts to match Unix versions. rbn Fix daemon usage displays. rbn Cleanup bacula-dir.conf template. rbn Install openssl.cnf so that the openssl.exe installed in the Bacula\bin directory can be used to generate keys and certificates for TLS and encryption. rbn Fix cleanup of spool files on Windows. rbn Remove /silent option from daemons on Windows. The new default is the same as the old /silent. To enable the message boxes that previously were suppressed by /silent you must add /debug instead. NOTE: As a result of this change, the first time you upgrade from a previous version of 1.39.x you will receive the message boxes when the remove of the old services succeeds. This is the same behaviour as when migrating from a version prior to 1.39.0. However, going forward, these message boxes will not appear on upgrades or new installs. rbn Add new /debug option. This option enables the message boxes that previously were suppressed by the /silent option. In addition the daemons running as services will open a console window if this option is used. rbn Fix bug with service not being removed on migrated installs. This should correct those cases where the file daemon install was failing when upgrading from versions prior to 1.39.x. 08Oct06 kes Turn on heap reporting in Dir with zero debug level. kes Send a message to the sys log when Bacula forces a SEG FAULT, and send the same message to stdout. 07Oct06 kes Begin work on new GUI console. kes Make configure look in non-standard MySQL library directory for Solaris. kes Make mtx-changer automatically configure the autochanger wait procedure for Solaris, FreeBSD, and Linux. Previously, only Linux was implemented. kes Correct drop_sqlite_tables.in script to not delete the database. kes When writing to a log file, close and reopen the file descriptor if there is an error writing the file. kes Modify the autochanger loaded?, load, and unload commands to print the full text of any mtx output if there is an error. Helps to ease diagnosis of autochanger problems. kes Correct a few Win32 errno returns in the VSS code so that hopefully a resonable Win32 error message will be printed. kes Convert a few strcat()... to bstrncat() in the Win32 code. 06Oct06 rbn Added Windows version of bsmtp. rbn Fixed path search for Windows so that Bacula\bin is automatically searched for programs and scripts. rbn Fixed bugs in mtx-changer.cmd and made template bacula-sd.conf Windows specific. - Using Tomcat but need to do more? Need to support web services, security? Get stuff done quickly with pre-integrated technology to make your job easier
[Bacula-users] rpm wizard script
Hello all, I read an article this week about using gnome's zenity utility to display gui dialogs and input information into shell scripts. I did some fooling around today and the result has been placed in cvs as platforms/contrib-rpm/rpm_wizard.sh. This handy little script will query your build parameters through a series of dialogs and then rebuild a bacula source rpm package. Regards, Scott - Take Surveys. Earn Cash. Influence the Future of IT Join SourceForge.net's Techsay panel and you'll get the chance to share your opinions on IT business topics through brief surveys -- and earn cash http://www.techsay.com/default.php?page=join.phpp=sourceforgeCID=DEVDEV ___ Bacula-users mailing list Bacula-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/bacula-users
[Bacula-users] contributed rpm packages
Hello, For those who have expressed and interest in contributing additional platform builds for bacula, I placed in cvs today a set of tools and instructions. They can be found in the directory platforms/contrib-rpm. Any 64-bit builders out there should note that I did not address that build switch because I expect it to be unnecessary with the next major release. To use the build script you would need to edit it and add --define build_x86_64 1 \ to each of the rpmbuild commands. Regards, Scott - Using Tomcat but need to do more? Need to support web services, security? Get stuff done quickly with pre-integrated technology to make your job easier Download IBM WebSphere Application Server v.1.0.1 based on Apache Geronimo http://sel.as-us.falkag.net/sel?cmd=lnkkid=120709bid=263057dat=121642 ___ Bacula-users mailing list Bacula-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/bacula-users
[Bacula-users] 1.38.11-3 FC5 rpms released to sourceforge
Hello, Rpm packages for the 1.38.11 release for FC5 have been provided by Felix and posted to sourceforge. Thanks Felix. - Using Tomcat but need to do more? Need to support web services, security? Get stuff done quickly with pre-integrated technology to make your job easier Download IBM WebSphere Application Server v.1.0.1 based on Apache Geronimo http://sel.as-us.falkag.net/sel?cmd=lnkkid=120709bid=263057dat=121642 ___ Bacula-users mailing list Bacula-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/bacula-users
[Bacula-users] bacula SuSE 10.1 installation repository
Hello All, For those running SuSE 10.1 I have created a repomd repository which you can add to your YaST installation sources to get the bacula rpm packages. After adding the installation source the latest package releases will be available for installation via YaST. Details can be found at http://linux01.gwdg.de/~sbarnin/ Regards, Scott - Using Tomcat but need to do more? Need to support web services, security? Get stuff done quickly with pre-integrated technology to make your job easier Download IBM WebSphere Application Server v.1.0.1 based on Apache Geronimo http://sel.as-us.falkag.net/sel?cmd=lnkkid=120709bid=263057dat=121642 ___ Bacula-users mailing list Bacula-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/bacula-users
Re: [Bacula-users] [Bacula-devel] Source Forge rejecting mail
On Tue, 2006-07-11 at 11:30 +0200, Kern Sibbald wrote: Hello, At least one user has reported that he is unable to send email to the list. Well, Source Forge recently put up a new version of Mailman, which is much more strict in what it lets through, probably in an effort to avoid spam. Your emails to any Bacula list will be dropped if they do not contain at least one of the following content types: multipart/mixed multipart/alternative text/plain I'm not an expert on this, but I suspect that those of you who sent HTML only will be silently dropped. In addition, any message attachment of the following types will be stripped from your email: exe bat cmd com pif scr vbs cpl Since we are beginning to see a bit of spam slip through, we are constantly tightening the rules to try to reduce it to a minimum ... Best regards, Kern They are also using SPF. I had to set up an @comcast.net address to send mail from my comcast cable connection. - Using Tomcat but need to do more? Need to support web services, security? Get stuff done quickly with pre-integrated technology to make your job easier Download IBM WebSphere Application Server v.1.0.1 based on Apache Geronimo http://sel.as-us.falkag.net/sel?cmd=lnkkid=120709bid=263057dat=121642 ___ Bacula-users mailing list Bacula-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/bacula-users
[Bacula-users] 1.38.11-3 rpm release
Hello All, Rpm packages have been released to sf including today's doc changes. Bacula-1.38 RPM Release Notes 01 July 2006 D. Scott Barninger barninger at fairfieldcomputers dot com Release 1.38.11-3 Patches included: bacula-1.38.9-gnome2console.patch 1.38.11-docs.patch 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 or on sourceforge for complete information on all changes. *** * WXWindows console added * *** A new package bacula-wxconsole has been added. Building this requires wxGTK =2.6 currently available on SuSE 10.0 and Fedora Core 4. * * Fix for daemon user/group problem * * Prior to the 1.38.8 release the pre-install scripts attempted to create the user bacula with primary group as both bacula and disk which failed. There was still a problem with these scripts in 1.38.8, noted in bug 605, on RedHat platforms which by default attempt to create a group with same name as the user (bacula) and failed because it had already been created. This has now been corrected with the addition of the -g parameter to the useradd commands and should work. A further syntax correction to the usermod commands was made and hopefully the post install scripts will now do everything correctly. ** * Build switch to turn off gnome console * ** If you do not wish to build gnome console --define nobuild_gconsole 1 when rebuilding the srpm. ** * Mtx change * ** Mtx is no longer included in the server package, but is packaged separately for systems without an mtx package. *** * Database update * *** The 1.38 release requires an update to the bacula database structure from version 8 to version 9. A pre-install routine has been added to check for databases older than 8. In that event the install will exit with an error message indicating that the database must be updated to version 8 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 8 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 cdrom rescue scripts are now included in the 3 server and client packages and the bacula-rescue package is obsoleted. You should uninstall bacula-rescue if installed before upgrading. ** * Platform Notes * ** Fedora Core 5 build target added. MySQL 5 build target added. RedHat 7.x gconsole package is eliminated with this release due to the elimination of support for gnome 1. The spec file currently supports building on the following platforms: # RedHat builds --define build_rh7 1 --define build_rh8 1 --define build_rh9 1 # Fedora Core build --define build_fc1 1 --define build_fc3 1 --define build_fc4 1 --define build_fc5 1 # Whitebox Enterprise build --define build_wb3 1 # RedHat Enterprise builds --define build_rhel3 1 --define build_rhel4 1 # CentOS build --define build_centos3 1 --define build_centos4 1 # SuSE build --define build_su9 1 --define build_su10 1 # Mandrake 10.x build --define build_mdk 1 # Mandriva build --define build_mdv 1 *** * Other build options * *** Database support (must select one) MySQL support: --define build_mysql 1 # OR if using mysql 4.x define this # currently: Mandrake 10.x, SuSE 9.x 10.0, RHEL4, fc4 --define build_mysql4 1 # OR if using mysql 5.x define this # currently: SuSE 10.1, fc5 --define build_mysql5 1 PostgreSQL support: --define build_postgresql 1 Sqlite support: --define build_sqlite 1 Supress build of Gnome Console: --define nobuild_gconsole 1 Enable X86-64 support --define build_x86_64 1 Enable wxconsole: --define build_wxconsole 1 Using Tomcat but need to do more? Need to support web services, security? Get stuff done quickly with pre-integrated technology to make your job easier Download IBM WebSphere Application Server v.1.0.1 based on Apache Geronimo http://sel.as-us.falkag.net/sel?cmd=lnkkid=120709bid=263057dat=121642 ___ Bacula-users mailing list Bacula-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/bacula-users
[Bacula-users] rpm python support
I've just released a modified spec file to bacula-beta to add python support. This release carries an updated spec file for the 1.38.11-3 srpm released to add python support. Currently there is not a lot of useful python functionality in 1.38 but it is expected to be present when 1.40 is released. I'm looking for some build testing on various platforms, particularly on x86_64 as there is a lib location hack I think will have to be implemented (it is currently commented out). Thanks in advance for your feedback. Using Tomcat but need to do more? Need to support web services, security? Get stuff done quickly with pre-integrated technology to make your job easier Download IBM WebSphere Application Server v.1.0.1 based on Apache Geronimo http://sel.as-us.falkag.net/sel?cmd=lnkkid=120709bid=263057dat=121642 ___ Bacula-users mailing list Bacula-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/bacula-users
[Bacula-users] bacula-1.38.10 rpm release
Rpm packages for 1.38.10 have been released to sourceforge. Bacula-gui-13.8 Release Notes 12 June 2006 D. Scott Barninger barninger at fairfieldcomputers dot com This release includes bacula-gui-bimagemgr only. There is no change to bacula-gui-web since 1.38.9. Configuration information has been separated out of bimagemgr.pl into a new file config.pm. This file will not be overwritten by the installer when upgrading in the future. If you are upgrading from earlier releases you will need to transfer your configuration information out of bimagemgr.pl into the new config.pm file. Support for SQLite databases has been added. Bacula-1.38 RPM Release Notes 12 June 2006 D. Scott Barninger barninger at fairfieldcomputers dot com Release 1.38.10-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 or on sourceforge for complete information on all changes. *** * WXWindows console added * *** A new package bacula-wxconsole has been added. Building this requires wxGTK =2.6 currently available on SuSE 10.0 and Fedora Core 4. * * Fix for daemon user/group problem * * Prior to the 1.38.8 release the pre-install scripts attempted to create the user bacula with primary group as both bacula and disk which failed. There was still a problem with these scripts in 1.38.8, noted in bug 605, on RedHat platforms which by default attempt to create a group with same name as the user (bacula) and failed because it had already been created. This has now been corrected with the addition of the -g parameter to the useradd commands and should work. A further syntax correction to the usermod commands was made and hopefully the post install scripts will now do everything correctly. ** * Build switch to turn off gnome console * ** If you do not wish to build gnome console --define nobuild_gconsole 1 when rebuilding the srpm. ** * Mtx change * ** Mtx is no longer included in the server package, but is packaged separately for systems without an mtx package. *** * Database update * *** The 1.38 release requires an update to the bacula database structure from version 8 to version 9. A pre-install routine has been added to check for databases older than 8. In that event the install will exit with an error message indicating that the database must be updated to version 8 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 8 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 cdrom rescue scripts are now included in the 3 server and client packages and the bacula-rescue package is obsoleted. You should uninstall bacula-rescue if installed before upgrading. ** * Platform Notes * ** Fedora Core 5 build target added. RedHat 7.x gconsole package is eliminated with this release due to the elimination of support for gnome 1. The spec file currently supports building on the following platforms: # RedHat builds --define build_rh7 1 --define build_rh8 1 --define build_rh9 1 # Fedora Core build --define build_fc1 1 --define build_fc3 1 --define build_fc4 1 --define build_fc5 1 # Whitebox Enterprise build --define build_wb3 1 # RedHat Enterprise builds --define build_rhel3 1 --define build_rhel4 1 # CentOS build --define build_centos3 1 --define build_centos4 1 # SuSE build --define build_su9 1 --define build_su10 1 # Mandrake 10.x build --define build_mdk 1 # Mandriva build --define build_mdv 1 *** * Other build options * *** Database support (must select one) MySQL support: --define build_mysql 1 # OR if using mysql 4.x define this # currently: Mandrake 10.x, SuSE 9.x 10.x, RHEL4, fc4 --define build_mysql4 1 PostgreSQL support: --define build_postgresql 1 Sqlite support: --define build_sqlite 1 Supress build of Gnome Console: --define nobuild_gconsole 1 Enable X86-64 support --define build_x86_64 1 Enable wxconsole: --define build_wxconsole 1 ___ Bacula-users mailing list Bacula-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/bacula-users
[Bacula-users] bacula-gui beta release
Hello All, I've released bacula-gui-CVS20060514 to sourceforge to hopefully get some testing on a couple new features in the bimagemgr utility. Anyone using an SQLite catalog and backing up to volume files is encouraged to try it out. All the usual beta caveats apply, don't use it in production, don't put your first born at risk etc. But do send bug reports. Thanks. Regards, Scott --- bimagemgr Release Notes Release 0.3 Configuration information has been separated out of bimagemgr.pl into a new file config.pm. This file will not be overwritten by the installer when upgrading in the future. If you are upgrading from earlier releases you will need to transfer your configuration information out of bimagemgr.pl into the new config.pm file. Support for SQLite databases has been added. --- Using Tomcat but need to do more? Need to support web services, security? Get stuff done quickly with pre-integrated technology to make your job easier Download IBM WebSphere Application Server v.1.0.1 based on Apache Geronimo http://sel.as-us.falkag.net/sel?cmd=lnkkid=120709bid=263057dat=121642 ___ Bacula-users mailing list Bacula-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/bacula-users
[Bacula-users] bacula-1.38.9 rpm packages released
Bacula-1.38 RPM Release Notes 06 May 2006 D. Scott Barninger barninger at fairfieldcomputers dot com The Gnome2 console currently will not build on older versions of Gtk2 ( 2.4) so you will see some missing gconsole packages. You _should_ be able to keep your gconsole package at 1.38.8 without problems if you upgrade since this release only incorporates minor bug fixes. If you are rebuilding the src rpm use the nobuild_gconsole switch. Release 1.38.9-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 or on sourceforge for complete information on all changes. *** * WXWindows console added * *** A new package bacula-wxconsole has been added. Building this requires wxGTK =2.6 currently available on SuSE 10.0 and Fedora Core 4. * * Fix for daemon user/group problem * * Prior to the 1.38.8 release the pre-install scripts attempted to create the user bacula with primary group as both bacula and disk which failed. There was still a problem with these scripts in 1.38.8, noted in bug 605, on RedHat platforms which by default attempt to create a group with same name as the user (bacula) and failed because it had already been created. This has (I think) now been corrected with the addition of the -g parameter to the useradd commands and should work. ** * Build switch to turn off gnome console * ** If you do not wish to build gnome console --define nobuild_gconsole 1 when rebuilding the srpm. ** * Mtx change * ** Mtx is no longer included in the server package, but is packaged separately for systems without an mtx package. *** * Database update * *** The 1.38 release requires an update to the bacula database structure from version 8 to version 9. A pre-install routine has been added to check for databases older than 8. In that event the install will exit with an error message indicating that the database must be updated to version 8 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 8 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 cdrom rescue scripts are now included in the 3 server and client packages and the bacula-rescue package is obsoleted. You should uninstall bacula-rescue if installed before upgrading. ** * Platform Notes * ** RedHat 7.x gconsole package is eliminated with this release due to the elimination of support for gnome 1. The spec file currently supports building on the following platforms: # RedHat builds --define build_rh7 1 --define build_rh8 1 --define build_rh9 1 # Fedora Core build --define build_fc1 1 --define build_fc3 1 --define build_fc4 1 # Whitebox Enterprise build --define build_wb3 1 # RedHat Enterprise builds --define build_rhel3 1 --define build_rhel4 1 # CentOS build --define build_centos3 1 --define build_centos4 1 # SuSE build --define build_su9 1 --define build_su10 1 # Mandrake 10.x build --define build_mdk 1 # Mandriva build --define build_mdv 1 *** * Other build options * *** Database support (must select one) MySQL support: --define build_mysql 1 # OR if using mysql 4.x define this # currently: Mandrake 10.x, SuSE 9.x 10.x, RHEL4, fc4 --define build_mysql4 1 PostgreSQL support: --define build_postgresql 1 Sqlite support: --define build_sqlite 1 Supress build of Gnome Console: --define nobuild_gconsole 1 Enable X86-64 support --define build_x86_64 1 Enable wxconsole: --define build_wxconsole 1 --- Using Tomcat but need to do more? Need to support web services, security? Get stuff done quickly with pre-integrated technology to make your job easier Download IBM WebSphere Application Server v.1.0.1 based on Apache Geronimo http://sel.as-us.falkag.net/sel?cmd=lnkkid=120709bid=263057dat=121642 ___ Bacula-users mailing list Bacula-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/bacula-users
[Bacula-users] bacula-1.38.8 rpm release
Bacula-1.38 RPM Release Notes 14 Apr 2006 D. Scott Barninger barninger at fairfieldcomputers dot com Release 1.38.8-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 or on sourceforge for complete information on all changes. * * Fix for daemon user/group problem * * Prior to the 1.38.8 release the pre-install scripts attempted to create the user bacula with primary group as both bacula and disk which failed. This has been corrected. ** * Build switch to turn off gnome console * ** If you do not wish to build gnome console --define nobuild_gconsole 1 when rebuilding the srpm. ** * Mtx change * ** Mtx is no longer included in the server package, but is packaged separately for systems without an mtx package. *** * Database update * *** The 1.38 release requires an update to the bacula database structure from version 8 to version 9. A pre-install routine has been added to check for databases older than 8. In that event the install will exit with an error message indicating that the database must be updated to version 8 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 8 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 cdrom rescue scripts are now included in the 3 server and client packages and the bacula-rescue package is obsoleted. You should uninstall bacula-rescue if installed before upgrading. ** * Platform Notes * ** RedHat 7.x gconsole package is eliminated with this release due to the elimination of support for gnome 1. The spec file currently supports building on the following platforms: # RedHat builds --define build_rh7 1 --define build_rh8 1 --define build_rh9 1 # Fedora Core build --define build_fc1 1 --define build_fc3 1 --define build_fc4 1 # Whitebox Enterprise build --define build_wb3 1 # RedHat Enterprise builds --define build_rhel3 1 --define build_rhel4 1 # CentOS build --define build_centos3 1 --define build_centos4 1 # SuSE build --define build_su9 1 --define build_su10 1 # Mandrake 10.x build --define build_mdk 1 # Mandriva build --define build_mdv 1 *** * Other build options * *** Database support (must select one) MySQL support: --define build_mysql 1 # OR if using mysql 4.x define this # currently: Mandrake 10.x, SuSE 9.x 10.x, RHEL4, fc4 --define build_mysql4 1 PostgreSQL support: --define build_postgresql 1 Sqlite support: --define build_sqlite 1 Supress build of Gnome Console: --define nobuild_gconsole 1 Enable X86-64 support --define build_x86_64 1 --- Using Tomcat but need to do more? Need to support web services, security? Get stuff done quickly with pre-integrated technology to make your job easier Download IBM WebSphere Application Server v.1.0.1 based on Apache Geronimo http://sel.as-us.falkag.net/sel?cmd=lnkkid=120709bid=263057dat=121642 ___ Bacula-users mailing list Bacula-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/bacula-users
[Bacula-users] 1.38.8-2 rpm release
I've released bacula-1.38.8-2.src.rpm and an SuSE 10 binary to sourceforge which adds a bacula-wxconsole package in the rpm-beta section. Note that you need wxGTK = 2.6 to build it, currently available from official sources on SuSE 10.0 and Fedora Core 4 AFAIK. To build it add the switch --define build_wxconsolw 1 I'll upload an FC4 binary later today or tomorrow. --- Using Tomcat but need to do more? Need to support web services, security? Get stuff done quickly with pre-integrated technology to make your job easier Download IBM WebSphere Application Server v.1.0.1 based on Apache Geronimo http://sel.as-us.falkag.net/sel?cmd=lnkkid=120709bid=263057dat=121642 ___ Bacula-users mailing list Bacula-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/bacula-users
[Bacula-users] Re: [Bacula-devel] Win32 FD compile
On Fri, 2006-03-03 at 19:33 -0500, Dan Langille wrote: AFAIK, cygwin is no longer used. Everything is native Windows now. If you want to build the Win32 binaries, you will need a Microsoft Visual C++ compiler (or Visual Studio). Does that help? I am getting ready to start building the win32 client for releases again, just waiting for VC++ to arrive. Looking at http://www.bacula.org/developers/Bacula_Porting_Notes.html I see: If you want to build the Win32 binaries, you will need the full Cygwin 1.5.5 release. Although all components build (console has some warnings), only the File daemon has been tested. Please note that if you attempt to build Bacula on any other version of Cygwin, particularly previous versions, you will be on your own. --- This SF.Net email is sponsored by xPML, a groundbreaking scripting language that extends applications into web and mobile media. Attend the live webcast and join the prime developer group breaking into this new coding territory! http://sel.as-us.falkag.net/sel?cmd=lnkkid=110944bid=241720dat=121642 ___ Bacula-users mailing list Bacula-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/bacula-users
[Bacula-users] Re: [Bacula-devel] Win32 FD compile
On Fri, 2006-03-03 at 19:33 -0500, Dan Langille wrote: AFAIK, cygwin is no longer used. Everything is native Windows now. If you want to build the Win32 binaries, you will need a Microsoft Visual C++ compiler (or Visual Studio). Does that help? See also README.win32 in src/win32 --- This SF.Net email is sponsored by xPML, a groundbreaking scripting language that extends applications into web and mobile media. Attend the live webcast and join the prime developer group breaking into this new coding territory! http://sel.as-us.falkag.net/sel?cmd=lnkkid=110944bid=241720dat=121642 ___ Bacula-users mailing list Bacula-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/bacula-users
[Bacula-users] Re: Bacula RPMs without gconsole (patch)
On Wed, 2006-02-22 at 13:10 +0200, Mindaugas wrote: Hello, Attached patch for bacula.spec file to be able to build without gconsole (build_gconsole define). Then server/client build requires much fewer gnome and other needed RPMs installed. Questions and notices: - I think BuildRequires: glibc-devel can be removed because anyway on both RHEL3 and RHEL4 gcc requires glibc-devel to be installed. Why to make .spec file too complicated? That is possible but without knowing the requires on all possible cases I prefer to explicitly state the requirements to build. - What for is BuildRequires: ORBit-devel for rh7? Since anyway later it is noted that now gconsole is only available for Gnome2? Kern can perhaps comment, but without double-checking I believe the file daemon may use CORBA technology and requires ORBit. If not it was probably an oversight to leave it in. - Current patch reverts default build behaviour to not build gconsole. To retain current behaviour maybe nobuild_gconsole define would be more reasonable. Yes, from a standpoint of building packages for distribution a nobuild default would be better. Mindaugas --- This SF.Net email is sponsored by xPML, a groundbreaking scripting language that extends applications into web and mobile media. Attend the live webcast and join the prime developer group breaking into this new coding territory! http://sel.as-us.falkag.net/sel?cmd=lnkkid=110944bid=241720dat=121642 ___ Bacula-users mailing list Bacula-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/bacula-users
[Bacula-users] 1.38.5 rpm release
Bacula-1.38 RPM Release Notes 21 Jan 2006 D. Scott Barninger barninger at fairfieldcomputers dot com Release 1.38.5-2 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=386633group_id=50727 * Known Issues * 1. The fc4 build currently uses fc3 dependancies. 2. Specific file permissions are applied in the packaging process - this needs to be removed. 3. Mandrake currently will not build. *** * Database update * *** The 1.38 release requires an update to the bacula database structure from version 8 to version 9. A pre-install routine has been added to check for databases older than 8. In that event the install will exit with an error message indicating that the database must be updated to version 8 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 8 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 cdrom rescue scripts are now included in the 3 server and client packages and the bacula-rescue package is obsoleted. You should uninstall bacula-rescue if installed before upgrading. ** * Platform Notes * ** RedHat 7.x gconsole package is eliminated with this release due to the elimination of support for gnome 1. The spec file currently supports building on the following platforms: # RedHat builds --define build_rh7 1 --define build_rh8 1 --define build_rh9 1 # Fedora Core build --define build_fc1 1 --define build_fc3 1 --define build_fc4 1 # Whitebox Enterprise build --define build_wb3 1 # RedHat Enterprise builds --define build_rhel3 1 --define build_rhel4 1 # CentOS build --define build_centos4 1 # SuSE build --define build_su9 1 # Mandrake build --define build_mdk 1 MySQL support: --define build_mysql 1 # OR if using mysql 4.x define this # currently: Mandrake 10.x, SuSE 9.x, RHEL4, fc4 --define build_mysql4 1 PostgreSQL support: --define build_postgresql 1 Sqlite support: --define build_sqlite 1 --- This SF.net email is sponsored by: Splunk Inc. Do you grep through log files for problems? Stop! Download the new AJAX search engine that makes searching your log files as easy as surfing the web. DOWNLOAD SPLUNK! http://sel.as-us.falkag.net/sel?cmd=lnkkid=103432bid=230486dat=121642 ___ Bacula-users mailing list Bacula-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/bacula-users
[Bacula-users] 1.38.0 rpm release to sourceforge
Bacula-1.38 RPM Release Notes 05 Nov 2005 D. Scott Barninger barninger at fairfieldcomputers dot com Release 1.38.0-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=367340 *** * Database update * *** The 1.38 release requires an update to the bacula database structure from version 8 to version 9. A pre-install routine has been added to check for databases older than 8. In that event the install will exit with an error message indicating that the database must be updated to version 8 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 8 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 cdrom rescue scripts are now included in the 3 server and client packages and the bacula-rescue package is obsoleted. You should uninstall bacula-rescue if installed before upgrading. ** * Platform Notes * ** RedHat 7.x will not build with this release due to the elimination of support for gnome 1. The spec file currently supports building on the following platforms: # RedHat builds --define build_rh8 1 --define build_rh9 1 # Fedora Core build --define build_fc1 1 --define build_fc3 1 # Whitebox Enterprise build --define build_wb3 1 # RedHat Enterprise builds --define build_rhel3 1 --define build_rhel4 1 # CentOS build --define build_centos4 1 # SuSE build --define build_su9 1 # Mandrake build --define build_mdk 1 MySQL support: --define build_mysql 1 # if using mysql 4.x define this and mysql above # currently: Mandrake 10.x, SuSE 9.x, RHEL4 --define build_mysql4 1 PostgreSQL support: --define build_postgresql 1 Sqlite support: --define build_sqlite 1 --- SF.Net email is sponsored by: Tame your development challenges with Apache's Geronimo App Server. Download it for free - -and be entered to win a 42 plasma tv or your very own Sony(tm)PSP. Click here to play: http://sourceforge.net/geronimo.php ___ Bacula-users mailing list Bacula-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/bacula-users
Re: [Bacula-users] Trouble building RPMS for 1.37.38
The spec file currently in cvs should build the server and client packages, what will be missing is the docs, rescue, gui etc. On Mon, 2005-09-19 at 11:41 +0200, Kern Sibbald wrote: On Monday 19 September 2005 09:43, Daniel Holtkamp wrote: Hi ! Kern Sibbald wrote: The spec files have not yet been updated from version 1.36.3, so until some work is done on them, they are not likely to work -- many things in the source have changed. Ouch, can anyone help quickly ? I was about to roll out the packages to our servers. Can anyone supply client-packages for bacula 1.37.38 ? I need RHEL2.1, RHEL3, RHEL4 and RH9. You might ask Scott Barninger who is our packager. As i said the packages compiled without major problems after some tweaking but you are sure they are broken right ? Had some test-systems run backups over the weekend and the director crashed twice already ... If you are experiencing crashes with the Director, please file a bug report. Given this situation, instead of asking Scott to rush creating the new .spec files, I think you would be much better off using the currently released version 1.36.3, which is already packaged for several of the distributions you want to use. Personally i have no idea about creating spec-files so i`m pretty lost out here ;) Best regards, --- SF.Net email is sponsored by: Tame your development challenges with Apache's Geronimo App Server. Download it for free - -and be entered to win a 42 plasma tv or your very own Sony(tm)PSP. Click here to play: http://sourceforge.net/geronimo.php ___ Bacula-users mailing list Bacula-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/bacula-users
[Bacula-users] Re: [Bacula-devel] Bacula RPM conflicts with sqlite (which is needed by rpm-4.4)
On Mon, 2005-07-11 at 16:34 +0200, Kern Sibbald wrote: On Monday 11 July 2005 16:25, Alexander Bergolth wrote: Hi! The current bacula-sqlite RPM has a conflicts-tag for sqlite: $ rpm -q --conflicts -p bacula-sqlite-1.36.3-1.fc3.i386.rpm bacula-client sqlite sqlite-tools However, the current rpm package from Axel Thimm's ATrpms (http://atrpms.net/dist/fc3/rpm-4.4.x/) requires sqlite which is packaged as a seperate RPM (http://atrpms.net/dist/fc3/sqlite/). rpm -q rpm rpm-4.4.1-21_45.rhfc3.at rpm -q --requires rpm | fgrep sqlite libsqlite3.so.0 rpm -q sqlite sqlite-3.1.2-2.99_1.rhfc3.at rpm -ql sqlite /usr/bin/sqlite3 /usr/lib/libsqlite3.so.0 /usr/lib/libsqlite3.so.0.8.6 /usr/share/doc/sqlite-3.1.2 /usr/share/doc/sqlite-3.1.2/README /usr/share/man/man1/sqlite3.1.gz Can the bacula-rpm be rebuilt to either use the existing sqlite-RPM or use it's own sqlite that doesn't conflict with the sqlite-package? (The current version's filenames shouldn't conflict anyway however the Conflicts-tag prevents from installing both packages. Bacula 1.36.x does not work with SQLite 3.x. Bacula 1.37.x does work with it, but I recommend against it because SQLite 3.x in my tests seems to be 4 to 10 times slower than SQLite 2.8.x SQLite 2.x and 3.x are designed to be installed on your system at the same time without conflicts -- providing it is done correctly of course. It is my intention for the next release to package the sqlite as a private library and remove the package conflict. --- This SF.Net email is sponsored by the 'Do More With Dual!' webinar happening July 14 at 8am PDT/11am EDT. We invite you to explore the latest in dual core and dual graphics technology at this free one hour event hosted by HP, AMD, and NVIDIA. To register visit http://www.hp.com/go/dualwebinar ___ Bacula-users mailing list Bacula-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/bacula-users
Re: Fwd: [Bacula-users] RPM rebuild for RHEL3 x86_64
Hello, The problem seems to me that you modified your release file to masquerade as RHEL, so the attempt to extract a Whitebox distribution release fails. Try: --define build_rhel3 1 You also need to tell it you are x86_64 with: --define build_x86_64 1 On Wed, 2005-06-08 at 14:37 +0200, Kern Sibbald wrote: -- Forwarded Message -- Subject: [Bacula-users] RPM rebuild for RHEL3 x86_64 Date: Wednesday 08 June 2005 13:49 From: Marcel Gsteiger [EMAIL PROTECTED] To: bacula-users@lists.sourceforge.net Hi all I recently did a rebuild of the RPMs from sources on Centos4 x86_64 for bacula-postgresql, this worked nice and produced functional RPMS for my platform. Meanwhile I tried the same on a WBEL3 x86_64 machine (Proliant ML370G4 SMP) upgraded to Centos3.4 . But I cannot make the rebuild work. Here is what happens: rpmbuild --rebuild --define build_wb3 1 --define build_postgresql 1 \ bacula-1.36.3-1.src.rpm Installiere bacula-1.36.3-1.src.rpm Warnung: user sbarn does not exist - using root Warnung: user sbarn does not exist - using root Warnung: user sbarn does not exist - using root Warnung: user sbarn does not exist - using root Warnung: user sbarn does not exist - using root Fehler: line 116: Empty tag: Distribution: My /etc/redhat-release and /etc/whitebox-release contains: Red Hat Enterprise Linux AS release 3 (Taroon) here: CentOS 3.4 (I did have to put that in to make my proliant support pack install properly) Any ideas? Regards --Marcel --- This SF.Net email is sponsored by: NEC IT Guy Games. How far can you shotput a projector? How fast can you ride your desk chair down the office luge track? If you want to score the big prize, get to know the little guy. Play to win an NEC 61 plasma display: http://www.necitguy.com/?r ___ Bacula-users mailing list Bacula-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/bacula-users --- --- This SF.Net email is sponsored by: NEC IT Guy Games. How far can you shotput a projector? How fast can you ride your desk chair down the office luge track? If you want to score the big prize, get to know the little guy. Play to win an NEC 61 plasma display: http://www.necitguy.com/?r=20 ___ Bacula-users mailing list Bacula-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/bacula-users
Re: [Bacula-users] bacula-1.36.2-1.src.rpm RHEL4
Hello,
Attached is the current spec file that was released with 1.36.2. The
snip you have below is older. I don't have access to RHEL4 so if you can
get it to build my next question would be to tell me the versions
shipped of certain packages. I realize it is probably closer to FC3, but
I think it will build working binaries with the build string I gave you
below. If you can get it to build and supply the version information I
can add an explicit target for RHEL4. If you have other ideas for the
Distribution tag please let me know.
Regards,
Scott
On Thu, 2005-03-24 at 19:19 -0500, Jeff McCune wrote:
D. Scott Barninger wrote:
Hello,
To build for RHEL4 and MySQL-4 do:
rpmbuild --rebuild \
--define build_rhel3 1 \
--define build_mysql 1 \
--define build_mysql4 1 \
bacula-1.36.2-1.src.rpm
Let me know if this works for you.
Sure doesn't... Also please note that RHEL4 is more akin to FC2/FC3
than it is to RHEL3.
[EMAIL PROTECTED] rhel-as-x86-4]# rpmbuild --rebuild \
--define build_rhel3 1 \
--define build_mysql 1 \
--define build_mysql4 1 \
bacula-1.36.2-1.src.rpm
Installing bacula-1.36.2-1.src.rpm
error: You must specify a platform. Please examine the spec file.
error: line 45: Unknown tag: exit 1
Note, there's no build_rhel3 in the spec file... There's wb3, which
contrary to the comment This should work for RHEL3 won't work because
it specifically greps for White in /etc/whitebox-release which will
never exist on a RHEL box.
On a side note, I'm really confused why there's such a heavy dependency
on the /etc/*release files. If you don't have the right files and the
right words in the files, builds fail completely.
Would you accept a patch to the spec file that populates _dist more
robustly?
Here's a snippet from the current spec file that shows why build_rhel3
won't work:
# platform defines - set one below or define the build_xxx on the
command line
# RedHat builds
%define rh7 0
%{?build_rh7:%define rh7 1}
%define rh8 0
%{?build_rh8:%define rh8 1}
%define rh9 0
%{?build_rh9:%define rh9 1}
# Fedora Core build
%define fc1 0
%{?build_fc1:%define fc1 1}
%define fc3 0
%{?build_fc3:%define fc3 1}
# Whitebox Enterprise build
# this should also work for RHEL
%define wb3 0
%{?build_wb3:%define wb3 1}
# SuSE build
# this is known to build on SuSE 8.2 and 9.0
%define su9 0
%{?build_su9:%define su9 1}
# Mandrake build
%define mdk 0
%{?build_mdk:%define mdk 1}
# test for a platform definition
%if ! %{rh7} ! %{rh8} ! %{rh9} ! %{fc1} ! %{fc3} ! %{wb3}
! %{su9} ! %{mdk}
%{error: You must specify a platform. Please examine the spec file.}
exit 1
%endif
Regards,
# Bacula RPM spec file
# Copyright (C) 2004 Kern Sibbald
# Platform Build Configuration
# basic defines for every build
%define depkgs ../depkgs
%define depkgs_version 29Oct04
%define tomsrtbt tomsrtbt-2.0.103
%define sqlite_bindir /usr/lib/sqlite
%define working_dir /var/bacula
%define daemon_user root
%define daemon_group bacula
%define group_file /etc/group
%define groupadd /usr/sbin/groupadd
# platform defines - set one below or define the build_xxx on the command line
# RedHat builds
%define rh7 0
%{?build_rh7:%define rh7 1}
%define rh8 0
%{?build_rh8:%define rh8 1}
%define rh9 0
%{?build_rh9:%define rh9 1}
# Fedora Core build
%define fc1 0
%{?build_fc1:%define fc1 1}
%define fc3 0
%{?build_fc3:%define fc3 1}
# Whitebox Enterprise build
%define wb3 0
%{?build_wb3:%define wb3 1}
# RedHat Enterprise build
%define rhel3 0
%{?build_rhel3:%define rhel3 1}
%{?build_rhel3:%define wb3 1}
# SuSE build
%define su9 0
%{?build_su9:%define su9 1}
# Mandrake build
%define mdk 0
%{?build_mdk:%define mdk 1}
# test for a platform definition
%if ! %{rh7} ! %{rh8} ! %{rh9} ! %{fc1} ! %{fc3} ! %{wb3} !
%{su9} ! %{mdk}
%{error: You must specify a platform. Please examine the spec file.}
exit 1
%endif
# database defines
# set for database support desired or define the build_xxx on the command line
%define mysql 0
%{?build_mysql:%define mysql 1}
# if using mysql 4.x define this and mysql above
# currently only Mandrake 10.1 uses this
%define mysql4 0
%{?build_mysql4:%define mysql4 1}
%define sqlite 0
%{?build_sqlite:%define sqlite 1}
%define postgresql 0
%{?build_postgresql:%define postgresql 1}
# test for a database definition
%if ! %{mysql} ! %{sqlite} ! %{postgresql}
%{error: You must specify database support. Please examine the spec file.}
exit 1
%endif
# check what distribution we are
%if %{rh7} || %{rh8} || %{rh9} || %{rhel3}
%define _dist %(grep Red /etc/redhat-release)
%endif
%if %{fc1} || %{fc3}
%define _dist %(grep Fedora /etc/redhat-release)
%endif
%if %{wb3} ! %{rhel3}
%define _dist %(grep White /etc/whitebox-release)
%endif
%if %{su9}
%define _dist %(grep SuSE /etc/SuSE-release)
%endif
%if %{mdk}
%define _dist %(grep Mandrake /etc/mandrake-release)
%endif
Summary: Bacula - The Network
