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.
On Thu, 2007-03-08 at 13:57 +0100, Kern Sibbald wrote:
> Hello Scott,
>
> Is this problem r
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
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
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'
Hi,
On 3/8/2007 12:12 AM, [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
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
