On 08/20/2010 01:53 PM, Thomas Arendsen Hein wrote:
2010-08-01 21:58:55 upgrade bacula-director-pgsql 2.4.4-1 5.0.2-1~bpo50+1
The history before that was that I used bacula-director-sqlite3
2.2.8-8 in the past and switched to postgresql without
importing/converting the old catalog when bacula 2.4.2-3.1 was the
current version in lenny/testing. dbconfig-common is still at
1.8.39:
OK, let me restate that and make sure I understand correctly.
1. You used to use bacula-director-sqlite3 version 2.2.8-8.
2. At some point you installed bacula-director-pgsql 2.4.2-3.1 instead.
3. You started with a freshly-installed new catalog when you installed
2.4.2-3.1, and made no effort to migrate the old catalog to it.
4. You made no changes to the database schema manually at any point.
5. You upgraded to 2.4.4-1 over time.
6. Then you had an error when upgrading from 2.4.4 to 5.0.2.
Is that correct?
-- John
--
To UNSUBSCRIBE, email to [email protected]
with a subject of "unsubscribe". Trouble? Contact [email protected]
