alpha5 packages don't move old database and config files

As a workaround, people can run the following command to remove the configuartion filea and Data.fs before installing the current version of schooltool.

$ apt-get remove --purge schooltool

Or, if schooltool has already been removed (but not purged):

$ dpkg --purge schooltool

As for automatically detecting old installs and moving stuff out the way. Should it just silently happen? Should there be some kind of UI question? Or perhaps we should just fail new installs with instructions to do the above (not sure how that will gel with synaptic)?

My vote would be for doing the move by default but notifying the user, if that is possible. We don't want people making the update finding SchoolTool broken because of the old file and having to dig up the solution to their problem. We also don't want people to accidentally permanently delete their data (if they had any) because they thoughtlessly do a purge.

Ok, I'm uploading 2007.0.alpha5-2 that have a fix for this.

Note that the fix is not perfect. In fact these actions from any installation of schooltool will get your database moved out the way:

* purge schooltool (but don't remove the database)
* re-install

(The alternative is to not move the database out the way on purged installations with databases. Which is the behaviour this bug tries to fix.)

Needs testing.

Brian, is this still an issue with our new set of packages?

Nope, it's not applicable anymore. The new packages use a Database file with a different name (but in the same directory).

So you can run 2 versions side by side. Attempting a data migration is simply the cp command.

P.S. let me know if there are any other bugs I need to comment on. I saw this one by chance in the firestorm of launchpad bug mail.