severity 569139 normal tags 569139 moreinfo unreproducible thanks On Wed, Feb 10, 2010 at 11:04:10AM +0100, Klaus Ethgen wrote: > I set the severity to important as the upgrade fails with existing > databases.
Hi Klaus, I have tested the upgrade path from 2.4.4-1 (the version in lenny) to 5.0.0-2 (the version now in sid). I have tested it from both the Sqlite v2 and the Sqlite v3 director, and while there was a small glitch in upstream's upgrade code relating to dropping a non-existing index, the upgrade process DID run, and I WAS asked if it should. So I am rather confused by the assertion that there is no upgrade code. Contrary to your message, there *is* code in bacula-director-sqlite3 to perform this upgrade, and it will ask you if you wish it to do so. If you answer affirmatively, then it will do so for you automatically. This is handled via the dbconfig-common infrastructure. It should be noted that upgrades from 3.x to 5.0 will not be really supported by the package, since 5.x will migrate to testing before squeeze is released. However, I see no reason why it should have failed. Your debconf settings below indicate that you assented to the upgrade (or that this was your default action, depending on your debconf settings). Therefore, I would like to see a copy of the terminal output that happens during your upgrade attempt, and to know what version of bacula-director-sqlite3 you upgraded from, as everything you've said suggests to me that the upgrade should have worked. > As you can see below I did try both but the new creation trows many > errors and I had to restore the database to convert it with the script > from the source. I'm not sure what information these comments pertain to -- can you clarify? > APT prefers stable > APT policy: (800, 'stable'), (700, 'oldstable'), (600, 'unstable'), (60, > 'experimental') > Architecture: i386 (i686) Given this rather complex apt policy, I would also like to know the exact commands you used to upgrade Bacula. -- John -- To UNSUBSCRIBE, email to [email protected] with a subject of "unsubscribe". Trouble? Contact [email protected]
