So openSUSE 10.2 is no longer supported carlo_t, which does not mean a good Samaritan who knows the exact answer might not pop up here. However, we would not know any better about how to do this than the bacula web site where you found this file. I am thinking I would try the rpm files instead of trying a compile, perhaps the older the better, but I don’t really know:
Then, if you have not already figured it out, you can switch to openSUSE 11.2 and find that the bacula file can be installed using the 1-Click install for openSUSE 11.2 as shown above.
Anyway compiling the src.rpm give me a zero byte executables I can’t investigate further, so I opened a bug: Access Denied
Thanks for help and answers
carlo_t, it is my opinion that in almost every case, you would better off installing the application, if it exists, from the 1-click installation rather than trying to compile the application yourself for the very reason you state when trying to compile the source code yourself. You are not the only person that have had such issues. In any event, good luck with your endeavor to install bacula. We want you to success and please ask for help if you need any more.
So it is possible that your attempt to compile the application has left something that can not be over written by the new install. I might suggest you open YaST / Software / Software Management and search for bacula. When found. right click on it and select Delete and let the program be uninstalled. Then, open up a terminal session and input the following commands:
su -
password:
rm /usr/sbin/bacula-dir
Next, open YaST / Software / Software Management and search for bacula again and this time elect to reinstall it. I assume that the one click install left the repository for this application, but if you removed it, then you need to go back to the 1-click just as before and install that way. See if this makes any difference.
Same trouble on OpenSuse 11.3 It looks like bacula installation packages are completely damaged, all these files should be soft or hard links to their MySQL equivalents, but they are just zero sized, and if copied manually, they are erased on each package upgrade… It sucks…
Breaks backups completely.
As I see, the root cause of this issue is that ‘bacula-director-mysql’ and other RPMs contain zero-sized binaries packaged inside RPM file:
-rwxr-xr-x 1 root root 0 Feb 1 14:44 bacula-dir
-rwxr-xr-x 1 root root 964367 Feb 1 14:44 bacula-dir.mysql
-rwxr-xr-x 1 root root 0 Feb 1 14:44 dbcheck
-rwxr-xr-x 1 root root 436831 Feb 1 14:44 dbcheck.mysql
And following post-install script will not overwrite existing zero-sized files. However, if zero-sized files are not packaged into RPM, it will create correct symlinks.
Note to jdmcdaniel3: You got it completely backwards. The OP did install from RPM packages, and that is actually the cause of the trouble. The problem can be completely avoided by compiling from source.