John Goerzen wrote:
David L. Anselmi wrote:
On upgrading to bacula 3.0 I was told my catalog was empty and should new tables
be created. I said no. I had hoped that my old catalog would be upgraded
automatically.
You can fix that with something along the lines of
echo .dump | sqlite2 bacula.db.sqlite2 | sqlite3 bacula.db.sqlite
This is from memory; a better recipe is probably in the preinst for
bacula-sqlite3. I will try to look into why this happened next week.
Thanks for the quick response. Here's what's seemed to work (run as the
bacula user in /var/lib/bacula):
sqlite bacula.db.sqlite2 .dump \
| sed 's/ INTEGER UNSIGNED AUTOINCREMENT,/ INTEGER,/' \
| sqlite3 bacula.db
/usr/share/bacula-director/update_sqlite3_tables
Hope that helps anyone else with this problem. I'll try to look at the
bacula-director-sqlite3.postinst to see what went wrong.
Dave
--
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
