All that said, it maybe better 'fall mode' behavior, or at least present
us with a better error message. Especially since dbc_dbadmin and
dbc_dbname were set properly. The upgrade runs as dbc_dbuser as I
understand though. It's an entirely moot point though, but in theory it
could have run the u
This is how I created the script, by merging the
/usr/share/dbconfig-common/data/bacula-director-mysq/upgrade/mysql/3.0.0
and 5.0.0 scripts.
I'm afraid I can see where this is probably my fault. Under
/etc/dbconfig-common/bacula-director-mysql.conf
I do not have the dbc_dbuser and dbc_dbpass pro
On Thu, Apr 14, 2011 at 05:18:05PM +0200, Jan Hauke Rahm wrote:
> Actually, our debian package already handles such upgrades. It simply
> started off of a false premise, that is having db version 11 in lenny.
> I'm still thinking about this but, if I'm not mistaken, the lenny
> version just needs t
On Thu, Apr 14, 2011 at 05:00:12PM +0200, Luca Capello wrote:
> On Tue, 07 Dec 2010 22:32:49 +0100, Julien Savoie wrote:
> > The included script upgrades from database format version 11 to
> > version 12. Unfortunately Debian lenny has bacula 2.4.4, which is
> > version 10. We were able to get ar
found 606262 5.0.2-1
tags 606262 + upstream
tags 606262 + patch
thanks
Hi Julien!
On Tue, 07 Dec 2010 22:32:49 +0100, Julien Savoie wrote:
> Package: bacula-director-mysql
> Version: 5.0.2-2, 5.0.2-1
AFAIK you can give only one version as an argument, giving two (or more)
gives you an error. I
Package: bacula-director-mysql
Version: 5.0.2-2, 5.0.2-1
The included script upgrades from database format version 11 to version
12. Unfortunately Debian lenny has bacula 2.4.4, which is version 10.
We were able to get around this by downloading the source to bacula 3.0
and running the versi
6 matches
Mail list logo
