On 30/08/12 17:20, Kern Sibbald wrote:
> However, if you are updating Bacula and going from say version
> 1.38 to version 5.2.x, you may have several DB updates to make.
> These must be done one at a time, which can be slightly painful to
> know exactly which scripts need to be called. So to make packagers
> jobs a bit easier we supply a directory <bacula-src>/updatedb that
> has all the scripts necessary to upgrade from one DB version to the
> next (it may not have the very latest upgrade which is in
> src/cats). If you look in that directory and read the README file,
> you should be able to figure out what needs to be done. Also
> looking at the comments at the top of the upgrade scripts you will
> probably see what Bacula versions correspond to what DB versions.
Thanks for the explanation; I've familiar with the DB upgrade process
(having just fixed it for 12.04) hence why I'm looking at this bug as
well.
So long as you use the dbconfig-common option to configure the
database then the bacula database is upgraded from version 10 -> 11 ->
12 - so the packaging does take this into account.
- --
James Page
Ubuntu Core Developer
Debian Maintainer
<email address hidden>
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.11 (GNU/Linux)
Comment: Using GnuPG with Mozilla - http://www.enigmail.net/
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA256
Hi Kern
On 30/08/12 17:20, Kern Sibbald wrote: src>/updatedb that
> However, if you are updating Bacula and going from say version
> 1.38 to version 5.2.x, you may have several DB updates to make.
> These must be done one at a time, which can be slightly painful to
> know exactly which scripts need to be called. So to make packagers
> jobs a bit easier we supply a directory <bacula-
> has all the scripts necessary to upgrade from one DB version to the
> next (it may not have the very latest upgrade which is in
> src/cats). If you look in that directory and read the README file,
> you should be able to figure out what needs to be done. Also
> looking at the comments at the top of the upgrade scripts you will
> probably see what Bacula versions correspond to what DB versions.
Thanks for the explanation; I've familiar with the DB upgrade process
(having just fixed it for 12.04) hence why I'm looking at this bug as
well.
So long as you use the dbconfig-common option to configure the
database then the bacula database is upgraded from version 10 -> 11 ->
12 - so the packaging does take this into account.
- -- www.enigmail. net/
James Page
Ubuntu Core Developer
Debian Maintainer
<email address hidden>
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.11 (GNU/Linux)
Comment: Using GnuPG with Mozilla - http://
iQIcBAEBCAAGBQJ QP5fAAAoJEL/ srsug59jDH1MP/ R97LlI4C0t9n+ j4c454Z8xf mXXc7exaoLq2T33 6fhT2VjVj5qobGX 2ufbVOelchBLPQ/ NpqM6fEtr 5jaLnuN/ BRpLbfet+ lg2iDf/ 4mhxuXv7qIpcDMt 1XNYmm6AOa Vxh+hArf8Oh4SFL gcv7YdBwBYPm7QT uvO2bHqQTYKPI2d CGMxP qO2Z3JleFkaD2zD PWbEjynPmr70Xr+ xu7RAlIarI9Z7B5 hn5e 6fzRL/jD3qC0CYX CU5LcsdFH1v/ gDctf0byQYwwdic 1jLjiIU 4zYomVEp4Fa1oGg 7jYQimz33e8H5D1 jVQhPMqcbJHvSe1 nhoSN/B0h eZdN+i85yuGTsBE enRJ7Xli2pdCrcQ 32l6ZbUDYE9OEaB kkmWbv ZrQLuAHsZC3jHJw W8t5KvsiqKRIkEn n1Tbefse/ 9aZZh0FgXm /i18ilQbQquyYd8 AoDmB4RuNXHf6OG /StHgoIB6BGzXt3 afPG tyYexcKSdGVka/ 12dcTx/ S7tU7UKmvBWNCG0 gZa86I4eDgN8JvE jT9i9w yUTRiT/ 7U
GwFRCfapy+
U6KHG+mKPItzEsY
aaLG4ja3pYmMo+
gndqqYQYGFcGuHR
YDjUVU19v6GwOGV
iFk3RxVaG/
89m2s8FFkbZa+
i1KBZy5CpObWyk9
RXALjhFaOWNWTVQ
HKAMRB+
jOe9k5Gq21+
=qKaP
-----END PGP SIGNATURE-----