Bug#569139: Please provide upgrade script

2010-02-22 Thread sean finney
hi again, On Mon, Feb 22, 2010 at 10:13:59AM +0100, Klaus Ethgen wrote: > I'm not sure too. How is the case of a complete new installation > diverted from the update procedure? I think that should at least be > addressed by proper questions. Maybe that needs the second suggestion > with a new debc

Bug#569139: Please provide upgrade script

2010-02-22 Thread Klaus Ethgen
-BEGIN PGP SIGNED MESSAGE- Hash: SHA512 Hi, Am So den 21. Feb 2010 um 23:26 schrieb sean finney: > The question is definitely confusing, and i believe it's even been > reported before. I think asking the upgrade question instead of > the install question would make it less ambiguous. Fo

Bug#569139: Please provide upgrade script

2010-02-21 Thread sean finney
hi guys, On Fri, Feb 12, 2010 at 10:40:05AM +0100, Klaus Ethgen wrote: > Am Do den 11. Feb 2010 um 22:48 schrieb John Goerzen: > > On Thu, Feb 11, 2010 at 10:13:37PM +0100, Klaus Ethgen wrote: > > > And there is the point. I never ever get to this point where I could > > > choose the option to upd

Bug#569139: Please provide upgrade script

2010-02-12 Thread Klaus Ethgen
-BEGIN PGP SIGNED MESSAGE- Hash: SHA512 Hi, Am Do den 11. Feb 2010 um 22:48 schrieb John Goerzen: > On Thu, Feb 11, 2010 at 10:13:37PM +0100, Klaus Ethgen wrote: > > And there is the point. I never ever get to this point where I could > > choose the option to update. > That is because you

Bug#569139: Please provide upgrade script

2010-02-11 Thread John Goerzen
On Thu, Feb 11, 2010 at 10:13:37PM +0100, Klaus Ethgen wrote: > And there is the point. I never ever get to this point where I could > choose the option to update. > That is because you answered incorrectly to the first question. You should have said yes when asked if dbconfig-common should conf

Bug#569139: Please provide upgrade script

2010-02-11 Thread Klaus Ethgen
-BEGIN PGP SIGNED MESSAGE- Hash: SHA512 Hi, Am Do den 11. Feb 2010 um 21:12 schrieb John Goerzen: > Klaus Ethgen wrote: > > Well, I was updating from version 3.xxx to the new version. As the 2.4 > > version is pretty old I think there are many people out there using the > > 3.x version in

Bug#569139: Please provide upgrade script

2010-02-11 Thread John Goerzen
Klaus Ethgen wrote: > Well, I was updating from version 3.xxx to the new version. As the 2.4 > version is pretty old I think there are many people out there using the > 3.x version in production. > > Additional, the debconf message just gives the options to create the > database or to _not_ create

Bug#569139: Please provide upgrade script

2010-02-11 Thread Klaus Ethgen
-BEGIN PGP SIGNED MESSAGE- Hash: SHA512 Hi John, Am Mi den 10. Feb 2010 um 20:38 schrieb John Goerzen: > 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. [...] > I have tested the upgrade pa

Bug#569139: Please provide upgrade script

2010-02-10 Thread John Goerzen
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-

Bug#569139: Please provide upgrade script

2010-02-10 Thread Klaus Ethgen
-BEGIN PGP SIGNED MESSAGE- Hash: SHA512 Package: bacula-director-sqlite3 Version: 5.0.0-2 Severity: important I set the severity to important as the upgrade fails with existing databases. In the source distribution is a script to update tables from 3.x database (V11) to the new version (