[pkg-bacula-devel] Bug#606262: Bug#606262: bacula-director-mysql lenny to squeeze database upgrade fail

[Julien Savoie]

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 properly populated.  This is
because we setup bacula's database access without first going through
the dpkg-reconfigure bacula-director-mysql.

I apologize, and I would like to close the ticket.  This was an issue on
our end.

On 04/20/2011 07:34 AM, Jan Hauke Rahm wrote:
> 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 to run the upgrade script for 10->11 additionally to
>> the already set script for 11->12. And if that's so, it's basicall
>> uncommenting a line in debian/rules.
>>     
> That's nonsense. bacula-director-* ship sql upgrade files for 3.0.0 and
> 5.0.0 (which combined are the script Julien provided). Either
> dbconfig-common didn't catch up on both or something entirely different
> went wrong.
>
> Hauke
>
>