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
tags 620963 + moreinfo
Hi Guillaume,
On Tue, Apr 05, 2011 at 02:45:31PM +0200, Guillaume Voyau wrote:
> backup catalog failed because of missing scripts that should be created
> during
> installation.
> occur (only ?) when using an existing mysql database.
> this files have not been created :
>
Processing commands for cont...@bugs.debian.org:
> tags 620963 + moreinfo
Bug #620963 [bacula] backup catalog scripts are not created when using an
existing mysql database
Added tag(s) moreinfo.
> Hi Guillaume,
Unknown command or malformed arguments to command.
> On Tue, Apr 05, 2011 at 02:45:31
Your message dated Wed, 20 Apr 2011 16:50:17 +0200
with message-id <20110420145017.ga16...@ca.home.jhr-online.de>
and subject line Re: Bug#612717: bacula-server: broken dependencies, cannot
install
has caused the Debian Bug report #612717,
regarding bacula-server: broken dependencies, cannot insta
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
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
6 matches
Mail list logo
