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

[Julien Savoie]

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 upgrade as dbc_dbadmin rather than dbc_dbuser. 
Anyways, this is a separate issue and my bug that the upgrade script
doesn't work was in error.

On 04/20/2011 07:43 PM, Julien Savoie wrote:
> 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
>>
>>   
>> 



-- 
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org

Bug#606262: [pkg-bacula-devel] 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
>
>   



-- 
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org

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

[Jan Hauke Rahm]

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

-- 
 .''`.   Jan Hauke Rahmwww.jhr-online.de
: :'  :  Debian Developer www.debian.org
`. `'`   Member of the Linux Foundationwww.linux.com
  `- Fellow of the Free Software Foundation Europe  www.fsfe.org


signature.asc
Description: Digital signature

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

[Jan Hauke Rahm]

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 around this by downloading the source
> > to bacula 3.0 and running the version 10 to 11 script manually
> > ourselves.
> 
> Thus we clearly need an upgrade path from lenny, even if we are a bit
> late given squeeze is out for two months now.

Absolutely, yes.

> > /usr/share/bacula-director/update_mysql_tables
> >> echo " "
> >> echo "This script will update a Bacula MySQL database from version
> >> 11 to 12"
> >> echo " which is needed to convert from Bacula Enterprise 2.6 to 4.0 or "
> >> echo " Standard version 3.0 to 5.0"
> >> echo " "
> > What is needed is a script that upgrades 10 to 12.  I'm including the
> > one I wrote.  The upgrade for the bacula-director-mysql should really
> > call this script or something similar.
> 
> Thank you very much for the script.
> 
> Given that this is an upstream bug (bacula-user@ mailing list cc:ed for
> comments), it would probably be a good thing to check with upstream if
> they have already provided a solution.  If this is not the case and
> there is interest for it outside Debian, I would be more than happy to
> push your script to upstream.
> 
> For the latter to happen, however, your script should share the same
> Bacula upstream license, do you agree with that?
> 
>   
> 
> 
> Or, if not pushed upstream and included in Debian-only, the license
> should be the same as the one José and John chose for their packaging
> work.  Since I could not find any note about it, José, John, could you
> enlighten us, please?

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.

But I still need to check that. I'm still working on a version for sid.

Hauke

-- 
 .''`.   Jan Hauke Rahmwww.jhr-online.de
: :'  :  Debian Developer www.debian.org
`. `'`   Member of the Linux Foundationwww.linux.com
  `- Fellow of the Free Software Foundation Europe  www.fsfe.org


signature.asc
Description: Digital signature