On Friday 09 March 2007 00:23, Scott Barninger wrote:
PS. No, the rpm packages can only do a single database version upgrade.
If an older version is detected it will abort and instruct the user to
upgrade the database with the scripts in the updatedb package.
OK, that explains things.
Dave, bottom line: either you need to stick with SuSE packages and upgrade
one version at a time manually upgrading the database, or you remove the SuSE
package (saving everything that is important) and install our package, then
upgrade one version at a time letting our rpms run the db upgrade script for
you.
Regards,
Kern
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, dthacker9 < at > co... 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.php&p=sourceforge&CID=DEVD
EV _______________________________________________
Bacula-users mailing list
Bacula-users < at > li...
https://lists.sourceforge.net/lists/listinfo/bacula-users
