[Date Prev][Date Next] [Thread Prev][Thread Next] [Date Index] [Thread Index]

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

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?
>   <http://www.bacula.org/en/dev-manual/main/main/Bacula_Copyright_Trademark_.html>
> 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.


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

Attachment: signature.asc
Description: Digital signature

Reply to: